Name steps by user intent
The best funnels read like a user story: lands on pricing, starts signup, creates workspace, installs snippet, sees first recording. Each step describes progress from the user's point of view. Internal labels like account-created-v2 or dashboard-route-loaded are useful for code, but they hide intent from product review.
When a funnel is named in user language, everyone can spot the gap faster. If many users create a workspace but do not install the snippet, the next question is obvious.
Validate every step with recordings
Before treating a funnel as truth, watch sessions around each transition. Make sure the event fires when users complete the intended action, not when a component renders or an API call retries. A funnel built on noisy events creates false urgency and hides the real leak.
Recordings are the fastest way to catch event definitions that look correct in a dashboard but fail in context.
Keep one activation funnel sacred
Small teams should maintain one core activation funnel and review it weekly. Resist the urge to create a dozen overlapping funnels. A focused funnel creates a shared operating rhythm: what changed, where did conversion move, and which sessions explain the movement?