feat(analytics): Plausible analytics phase 1 (visitors, imports/exports, persona)

Open
#796 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@DerekRoberts is already working on this.

Since Oct 24, 2026.

  • #799 by @DerekRoberts — open

Assessment

This issue has not been assessed yet.

Description

enhancement

Priority: high. Ships together with the privacy note issue (linked below).

Goal

Count usage without collecting personal information. The app has no persistent storage and redeploys often, so everything goes to Plausible. Nothing is stored in the app.

Scope

  • Add Plausible: cookieless, no raw IPs stored. Plausible counts daily unique visitors with its own rotating salted hash, so we don't need any extra code for that.
  • Custom events:
    • Import with property result: success|failure
    • Export with property result: success|failure
    • Persona Selected (mode/persona) with property persona: <name>
  • Events carry only the event name and simple enumerated properties. Never content, file names, question/answer text, or anything the user typed.

Done when

  • Plausible script/API added, configured by env (e.g. domain); if unset, nothing is sent
  • Unique visitors show in Plausible with no cookies set and no IPs logged by the app
  • Import/export success and failure events fire and appear in Plausible
  • Persona/mode selection event fires with the persona name only
  • Tests confirm event payloads contain no content, file names or user input
  • Analytics failure never breaks or slows a user action
  • One PR, CI green, no warnings/errors in test output

Related: #340 (operational telemetry, separate scope; keep payload rules consistent).

Dominant language
Python
Stars
2
Forks
1
Avg merge
4h 16m
Merged PRs (30d)
38

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MinionTech/vexilon

All issues in MinionTech/vexilon

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.