More Than 30 Unique Tracking Events Will Cause You Problems
Visit LinkBased on product audits, this post explains how exceeding 30 core events leads to confusion, duplicative metrics, and inflated tooling costs. Timo recommends modeling a small set of core entities and using properties to capture UI-specifics. Includes governance tips.
More in Event Taxonomy
How Data Governance Can Help Collect Good Event Data
João Lousada outlines how a data governance strategy prevents analytics drift. He emphasizes the role of casing rules, ownership tags, and source-of-truth documentation in keeping instrumentation aligned with product changes. Great for teams scaling analytics without chaos.
The UX of Event Architecture — An Amplitude Reintegration Story
In this Amplitude reintegration story, Moss Pauly shows how reducing events to a <30 schema improved usability for analysts. Events were refactored to prioritize clarity and team ownership, with event routing and validation set up before hitting Amplitude.
What's Sexy? Naming Conventions for Analytics Events
Paul Koullick argues that naming events well is a UX challenge. He lays out conventions for naming (verb-noun, title case, property bias), and introduces a workflow where every new event is reviewed for clarity and governance. Great for scaling teams.