Event Naming That Survives Growth
A naming scheme that looks tidy at ten events often collapses at two hundred. Here is a durable pattern for product teams.
Most tracking plans begin with a spreadsheet and good intentions. The trouble starts when marketing invents campaign events, engineering ships feature flags under temporary names, and nobody owns the glossary.
A durable scheme separates object, action, and context. Prefer `checkout_payment_submitted` over vague labels like `click_btn3`. Keep property keys stable even when UI copy changes.
Version the plan. When an event must change meaning, retire it and introduce a successor rather than silently rewriting history. Downstream reports stay honest, and new hires can learn the system without tribal knowledge.
Finally, treat naming reviews as part of the pull request checklist. Five minutes of scrutiny at merge time prevents months of cleanup later.