A taxonomy
that notices drift.
The taxonomy-detector maps incoming payloads to 32 canonical events, versions the contract in event_taxonomy_versions, and records changes in event_taxonomy_drifts when implementation behavior moves.
Built from the product surface, not brochure claims.
What the team actually gets.
Canonical names
view_item, add_to_cart, checkout_started, purchase_placed, lead_submitted, and 27 more events stay stable.
Versioned contracts
Every merchant has an event taxonomy history instead of tribal knowledge in a launch doc.
Drift detection
Field moves, missing identifiers, value changes, and event absences are captured as drift records.
Destination mapping
Each canonical event maps into platform-specific names and payload requirements.
How it compares to ordinary tracking work.
- Canonical event count
- 32
- Taxonomy versioning
- event_taxonomy_versions
- Drift records
- event_taxonomy_drifts
- Destination mapping
- per platform
- Missing event detection
- coverage_gaps
- Canonical event count
- implementation-specific
- Taxonomy versioning
- docs
- Drift records
- manual QA
- Destination mapping
- tag templates
- Missing event detection
- manual
- Canonical event count
- platform-specific
- Taxonomy versioning
- none
- Drift records
- symptoms
- Destination mapping
- connectors
- Missing event detection
- partial
Real merchant-shaped cases and measurable signals.
The references an operator can inspect.
Where this matters in production.
A theme release renamed customer_email to user.email.
event_taxonomy_drifts recorded the field move before identity_gaps became a paid-media issue.
Launch QA needed to verify every required commerce event.
The 32-event taxonomy became the acceptance checklist for implementation.
Search UI shipped without firing search events.
coverage_gaps detected the missing canonical event after traffic continued but events disappeared.