12 August 2026 · 5 minute read
An event taxonomy your team can keep clean
A useful naming system is less about clever labels and more about ownership, review, and a small set of durable rules.
Analytics debt often begins when each feature team names events in isolation. Start with an object–action convention, define required properties once, and keep platform-specific detail out of the event name.
Make the practice repeatable
Assign one owner for the tracking dictionary and make analytics review part of feature acceptance. A short monthly cleanup prevents dashboards from becoming a museum of abandoned events.
Finally, test events against real product questions. If an event cannot support a decision, it probably should not be collected.