· Yuri Han
Naming Events So Redesigns Do Not Break History
Prefer intent over layout. A taxonomy that encodes button labels will fail the moment the UI moves.
Product screens change often. Event names that encode layout details—screen titles, button copy, component IDs—break as soon as design ships a rewrite. Prefer names that describe user intent and business outcome.
A durable pattern uses object_action_context: checkout_submit_payment or profile_update_email. Keep UI details in properties such as surface, experiment_id, and platform.
Before a redesign, run a rename impact review. List events tied to deprecated screens, decide which to alias, and freeze a short dual-write window so historical funnels stay comparable.
Assign an owner next to each event. When the design system changes, that person decides whether the semantic meaning still holds—not a shared channel that forgets.