Naming events that survive the next release

Teams often treat event names as disposable labels. A designer renames a screen, an engineer ships a new component, and suddenly “checkout_start” and “begin_checkout” both exist for the same moment. Reports that once looked clean become archaeological digs.

Prefer verbs that describe the user’s intent, not the UI widget. “Submit_order” outlasts “tap_green_button.” Keep platform prefixes out of the event name; put platform in a property so web and app stay comparable.

Write the allowed properties next to the name on the same day you create it. An event without documented properties becomes a free-form dump that no one trusts six months later.

In Event Taxonomy Audits we spend the first day only on inventory—because until synonyms are visible, every later fix guesses at the wrong root.