Measure Onboarding Completion in Amplitude
Model the essential onboarding steps as observable outcomes and define completion as readiness for core value. Required and optional branches should not be mixed into one funnel that penalizes legitimate alternative paths.
Before you start: Have validated events, known entry criteria and an agreed completion definition. Include product and engineering in checking the sequence.
Worked example: A workspace owner creates a workspace, configures a project and invites a teammate. Importing sample data is optional and should not make the owner appear to fail onboarding.
Step-by-step guide
Define completion
Write what the user must be able to accomplish at the end. Separate account setup from the first meaningful value outcome.
Map essential steps
Choose events for confirmed state changes. Mark optional branches and alternative routes instead of forcing every event into one sequence.
Validate journeys
Check a successful user, a retry and an alternative path. Confirm the funnel counts the intended cases.
Set the window
Allow realistic completion time and compare cohorts with equal maturity. Record any incomplete observation.
Inspect the largest meaningful loss
Review both absolute users and conversion between steps. Distinguish a required bottleneck from a low-volume optional action.
Choose a focused follow-up
Investigate one transition with segments or user evidence. Keep the original funnel definition for comparison after a change.
Common mistakes
Optional step required
A legitimate route becomes a false drop-off.
Click versus state change
A button attempt may fail.
Recent cohort judged early
Users need an equal chance to complete.
Tips
Keep optional branches outside the core completion funnel.
Test a known successful journey after event changes.
Pair percentages with entrant counts.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.