Events that outlive UI renames

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

Prefer verbs that describe intent. Keep platform out of the event name—put it in a property so web and app stay comparable. Write allowed properties on the same day you create the event.

In Measurement Blueprint engagements we spend the first day on inventory alone, because until synonyms are visible every later fix guesses at the wrong root.