Naming events that survive releases

Application analytics fails quietly when event names drift. One sprint uses signup_complete; the next ships userRegistered. Dashboards break, funnels vanish, and trust erodes.

Start with a three-part pattern: object, action, and optional context—for example checkout_submit_payment. Keep casing consistent. Prefer past-tense actions only when the event fires after success is confirmed.

Document aliases when you must rename. Deprecate old keys with a sunset date rather than deleting them overnight. Product and engineering should review the schema together before every major release.

When names survive releases, historical comparisons stay honest—and that is the foundation of every useful retention or funnel study.