Event names that survive product changes
Naming rules that keep historical reports readable when screens, buttons, and service boundaries shift.
UI-tied names such as "blue_button_tap_v3" age poorly. When the button moves or the colour changes, historical series become hard to interpret.
Prefer names that describe the business action and the object: "subscription_renewal_started", "invoice_exported". Properties can carry screen or component detail without poisoning the event name.
For distributed services, include the emitting service as a property, not as part of the verb. That keeps the same activity comparable when ownership moves between teams.
Document deprecations with a sunset date. Silent renames are the usual reason year-over-year charts look broken after a redesign.