Analytics Event Tracking

Move product analytics from ad-hoc track("Clicked Button") calls to a versioned, linted tracking plan that engineers implement the same way every time, without sacrificing user privacy, consent compliance, or the trust of the people who read the dashboards.

Start every run

1. Read references/taxonomy-rules.md before naming or renaming any event, property or trait.
2. Read references/implementation-playbook.md before writing tracking code, choosing client versus server, or wiring consent.
3. Read references/operations.md before running the linters, exporting events, or changing project settings.
4. Inspect current state: the tracking plan file (default analytics/tracking-plan.json), the last lint and QA output, the analytics project's live event list for the past 7 days, and the consent configuration. The live event list is the truth; the plan is the intent.
5. Confirm authorization. Editing the plan and adding tracking code in a branch needs none. Deleting events, renaming live events, changing consent categories, or touching the production project's settings needs an explicit request from the plan owner.

Non-negotiable rules

• Event names are object_action_past in snake_case, at most 40 characters: checkout_completed, not Checkout Completed, completeCheckout, or