May 11, 2026
Naming events that survive refactors
A practical schema for application events so analytics stay readable when features move.
Feature names change. Screen routes move. If your analytics events mirror UI labels, every redesign becomes a data migration.
Prefer object + action names that describe the user outcome: account_created, invite_sent, checkout_completed. Keep UI labels in properties when you need them for debugging.
Version your schema in the same repo as your product. When an event changes meaning, add a new name rather than silently reshaping the old one.
A short glossary shared by eng and product prevents the classic trap: three events that all mean “signed up” with different property sets.