Why naming events after screens fails after two releases
Screen labels age poorly. Action-based names survive redesigns and keep cohorts comparable.
Teams often stamp events with the screen title they see in Figma. Two releases later the screen is gone, the event remains, and onboarding cohorts quietly mix old and new meaning.
Action-based names—trial_started, plan_selected, receipt_viewed—describe what happened, not where it appeared. Properties carry layout context when you still need it.
secure-route writes taxonomies this way so analysts can compare months without footnotes about which UI lived when.