29 lines
1.4 KiB
Markdown
29 lines
1.4 KiB
Markdown
## MODIFIED Requirements
|
||
|
||
### Requirement: Custom event tracking
|
||
When Umami is enabled, the site MUST support custom event emission for:
|
||
- `cta_click`
|
||
- `outbound_click`
|
||
- a general click interaction event for all instrumented clickable items (per the site tracking taxonomy)
|
||
|
||
Each emitted event MUST include enough properties to segment reports by platform and placement when applicable.
|
||
|
||
All tracked clickable items MUST emit events with a unique, consistent set of data elements as defined by the site tracking taxonomy, including at minimum `target_id` and `placement`.
|
||
|
||
The site MUST instrument tracked clickables using Umami’s supported Track Events data-attribute method:
|
||
- `data-umami-event="<event-name>"`
|
||
- optional event data using `data-umami-event-*`
|
||
|
||
#### Scenario: Emit outbound click event
|
||
- **WHEN** a user clicks a non-CTA outbound link from the homepage
|
||
- **THEN** the system emits an `outbound_click` event with a property identifying the destination domain
|
||
|
||
#### Scenario: Emit general click event for any clickable
|
||
- **WHEN** a user clicks an instrumented navigation link
|
||
- **THEN** the system emits a click interaction event with `target_id` and `placement`
|
||
|
||
#### Scenario: Uninstrumented clicks do not break the page
|
||
- **WHEN** a user clicks an element with no tracking metadata
|
||
- **THEN** the system does not throw and navigation/interaction proceeds normally
|
||
|