Inventory and intent
We collect existing event exports, product walkthroughs, and the business questions your reports must answer. Gaps and duplicates are listed before anyone debates names.
Method
How we plan an event taxonomy
A repeatable sequence used across our application analytics engagements. It keeps workshops focused on journeys, names, and owners rather than tool settings.
Journey to candidates
In workshop one we map a defined user journey and place candidate events on observable actions. Each candidate must answer a written question.
Names, properties, owners
Workshop two locks naming conventions, required properties, and an owner for each event family. Provisional labels are marked rather than forced.
Written pack and cadence
You receive the catalogue, convention notes, and a suggested review cadence. One revision cycle absorbs stakeholder feedback before the pack is final.
What you bring
- Export of current event definitions where they exist
- A product owner and an engineer who will implement tracking
- Clarity on one primary journey for the first engagement
What we leave behind
- Named events with trigger definitions
- Property schemas and required fields
- Ownership map and retirement guidance