Event Naming That Survives Roadmaps

Application analytics fails quietly when event names encode temporary UI labels or sprint-specific feature codes. Six months later, nobody remembers what `btn_orange_v3_click` meant, and dashboards become archaeology.

Prefer object–action pairs that describe user intent rather than interface chrome: `project.created`, `invite.accepted`, `billing.plan_changed`. Keep properties for context—source surface, plan tier, locale—instead of baking that context into the event name.

Document the dictionary where engineers already work. A markdown file in the repo, reviewed in pull requests, beats a forgotten spreadsheet. When a name must change, version the property rather than inventing a parallel event that forever forks your history.

Teams operating across Korean and international markets should also standardise locale and timezone properties early. Otherwise retention charts disagree depending on which office built the query.