## Why

We need clear, consistent measurement of what users click on the website and where they go, so we can evaluate acquisition and conversion performance and iterate quickly.

## What Changes

- Standardize click tracking across the entire site so every clickable item emits a custom event with a unique, consistent set of data properties.
- Align event naming and properties with Umami custom event tracking conventions (see Umami "Track events" documentation).
- Ensure tracking works without breaking navigation/UX, and remains safe when analytics is disabled or misconfigured.

## Capabilities

### New Capabilities

- `interaction-tracking-taxonomy`: Define a site-wide event taxonomy for clickable items (required properties, naming conventions, uniqueness rules, and allowed values) and document how new links/buttons must be instrumented.

### Modified Capabilities

- `analytics-umami`: Expand custom event support beyond the current CTA/outbound tracking to cover all clickable items and their unique data properties.
- `conversion-ctas`: Ensure all CTAs conform to the taxonomy (unique identifiers/properties per placement) and remain measurable in Umami with consistent segmentation.

## Impact

- Frontend code: add/standardize data attributes (or equivalent wiring) for all clickable elements (nav links, content cards, CTAs, external links) and update the central tracking hook.
- Analytics: define and maintain an event/property contract; dashboards/filters in Umami will depend on stable names.
- QA: verify in staging that events are emitted as expected and that disabling analytics does not cause client errors.