Naming events without chaos
A practical convention for event names that product and engineering can both live with—before your warehouse becomes a glossary of synonyms.
Most application analytics problems start as naming problems. One team logs `signup_complete`, another logs `userRegistered`, and a third logs `account_created` for the same moment. Months later, retention reports disagree because nobody agrees which event is canonical.
A durable convention is less about clever prefixes and more about ownership. Pick a verb-object pattern, write it down, and appoint one person who can reject new events that break the pattern. Rejecting early is cheaper than remapping warehouses later.
For Korean product teams shipping bilingual apps, decide whether event names stay English-only in code while dashboards localize labels. Mixing languages inside event strings creates filters that break the moment a new PM joins.
Start with twenty events that cover activation. Expand only when a question cannot be answered with those twenty. A short tracking plan that is followed beats a comprehensive plan that nobody updates.