Event names that survive the next release
If renaming an event requires a week of archaeology, the dictionary—not the dashboard—is the problem.
- instrumentation
- naming
Application analytics collapses when every squad invents its own verb for the same action. Prefer a short vocabulary: object, action, and context—written once and reused.
Ban marketing adjectives inside event names. “AwesomeCheckoutComplete” ages poorly; “checkout_completed” with properties for plan and surface stays readable after three rebrands.
Store the dictionary where engineering already looks—repository docs or a shared sheet with owners—not only in a slide from last quarter’s offsite.
In telemetry audits we often find twenty near-duplicates of the same click. Collapsing them is usually worth more than adding a new chart.