Stop naming events after screens alone
When every event is screen_viewed with a route property, funnels become fragile. Routes rename, tabs move, and deep links appear. The chart still lights up — but the meaning drifts.
Prefer verbs tied to user intent: plan_selected, checkout_started, invite_sent. Keep screen context as a property, not the noun. Your inventory stays readable when the UI rearranges.
During an instrumentation audit we often find duplicate fires because two screens share a component that both emit the same screen-named event. Intent names make those collisions obvious before they inflate conversion.