Event Names That Survive Product Rewrites

Product teams rewrite screens often. Analytics taxonomies that encode layout details break the moment a button moves. Prefer names that describe the user intent and business outcome, not the pixel path.

A durable pattern uses object_action_context: for example checkout_submit_payment or profile_update_email. Keep properties for UI details such as surface, experiment_id, and platform.

Before a redesign ships, run a rename impact review. List events that reference deprecated screens, decide which to alias, and freeze a two-sprint dual-write window so historical funnels stay comparable.

Document ownership next to each event. When the design system changes, the owner—not a shared Slack channel—decides whether the semantic meaning still holds.