# Event Tracking

## Objective

Know what people actually do in your app.

A consistent event tracking layer, wired to the actions that matter.

## Before You Begin

This feature is being added to an application that already exists and already
works. Do not scaffold a new project, and do not assume a blank slate.

Inspect the codebase first and establish:

- The existing application structure and where code of this kind already lives.
- The framework and version in use.
- The existing design system — colours, spacing, typography, and component conventions.
- Existing UI components you can reuse instead of writing new ones.
- The existing database structure, if this feature needs to persist anything.
- The existing authentication and authorization system, if this feature is user-scoped.
- Dependencies already installed, so you don't add a library that duplicates one.
- The existing test setup and conventions.

Only start writing code once you understand the above. If the application
already implements part of this feature, extend it rather than replacing it.

## Implementation Instructions

1. Define a naming convention before you write a single event. 'object_action' (user_signed_up, project_created) stays sane at scale; ad-hoc names do not.
2. Track the handful of events that map to your funnel. Tracking everything produces noise nobody reads.
3. Wrap the analytics vendor behind one internal function so you can swap or add providers without touching call sites.
4. Track server-side where correctness matters — ad blockers eat client-side events.

## UI and UX Requirements

Match the application's existing design system exactly. Reuse its components,
spacing, and typography. This feature should look like it was always there.

## Responsive Requirements

Works on mobile, tablet, and desktop. Touch targets are large enough to hit on a
phone, and nothing overflows horizontally at 320px.

## Accessibility Requirements

- Fully keyboard navigable.
- Correct semantic elements and ARIA roles.
- Visible focus states.
- Meets WCAG AA contrast.
- Dynamic changes are announced to screen readers.
- Respects prefers-reduced-motion.

## Edge Cases

- Never send PII (emails, names, raw addresses) into analytics payloads without an explicit decision — it's a compliance problem.
- Respect Do Not Track and any consent the user gave or withheld.
- A failing analytics call must never break the user's action.
- Don't double-count: a client event plus a server event for the same action inflates everything.
- Bots and internal staff traffic should be excluded.

## Testing

Exercise the feature end to end in the running application. Cover every edge case
above, then run the existing test suite and confirm nothing regressed.

## Acceptance Criteria

- [ ] Events follow one documented naming convention.
- [ ] The vendor sits behind a single internal wrapper.
- [ ] Revenue- and funnel-critical events are tracked server-side.
- [ ] No PII is sent without an explicit decision.
- [ ] Consent and Do Not Track are respected.
- [ ] A failed analytics call never breaks the app.
- [ ] The feature matches the existing design system.
- [ ] No existing functionality is broken.

## Adaptation Rules

- Match the existing design system. Do not introduce a new colour palette,
  spacing scale, or component library.
- Reuse existing components and utilities wherever they fit.
- Follow the naming, file layout, and code style already present.
- Do not upgrade, replace, or remove existing dependencies to make this
  feature fit. Adapt the feature to the app, not the app to the feature.
- Do not break existing functionality. If a change is genuinely required in
  existing code, make the smallest one that works and say so.
- If something in these instructions conflicts with how the application is
  built, follow the application and explain the deviation.

## Final Verification

Before you report the work as done:

1. Re-read the acceptance criteria above and check each one against what you
   actually built.
2. Run the application and exercise the feature end to end.
3. Run the existing test suite and confirm you have broken nothing.
4. Check the feature on mobile, tablet, and desktop widths.
5. Check keyboard navigation and focus handling.
6. Summarize what changed: files added, files modified, and anything you
   deliberately did differently because of how this application is built.

If any acceptance criterion is unmet, fix it before reporting completion.