Why event names fail after three releases
Most teams start with clear event labels. Then a rebrand, a new funnel, and two contractors later, nobody trusts the catalogue.
Field notes
Notes from taxonomy planning rooms
Short articles on naming failures, required properties, workshop practice, and when to retire events — rooted in application analytics work.
Properties worth requiring on every event
Not every field belongs on every event. A small required set keeps analysis coherent without bloating payloads.
Running a taxonomy workshop with product and engineering
A good workshop ends with named events and open questions, not a slide deck nobody opens again.
When to retire an analytics event
Keeping every historical event “just in case” makes new analysis harder. Retirement needs a rule, not a hunch.
Mapping user journeys to candidate events
Journey maps become useful for analytics when each step is tied to an observable action and a business question.