Name events for intent, not for widgets
A button label will change. The user intent behind the tap usually will not.
Teams treat event names like disposable UI labels. A designer renames a screen, an engineer ships a new component, and suddenly two names describe the same moment. Reports become archaeology.
Prefer verbs that describe intent. Submit_order outlasts tap_green_button. Keep platform out of the event name; put it in a property so web and app stay comparable.
Document allowed properties the same day you create the name. An event without a property contract becomes a free-form dump nobody trusts six months later.
In Product Event Blueprint work we spend the first day on inventory alone—because until synonyms are visible, every later fix guesses at the wrong root.