Signals that survive UI renames
Name the operational intent, not the button label—or the next redesign breaks every ops report.
Teams often treat event names as disposable labels. A designer renames a screen, an engineer ships a new component, and suddenly checkout_fail and tap_error both exist for the same moment. Ops 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 during cloud incidents. Write allowed properties on the same day you create the signal.
In Visibility Audit engagements we spend the first day on inventory alone, because until synonyms are visible every later fix guesses at the wrong root.