·8 min read

7 Onboarding Funnel Metrics Every Mobile Product Team Should Track

Most teams track two onboarding numbers: signups and DAU. Here are the seven that actually tell you whether your onboarding is working - and what to fix when it isn't.

1. Per-step drop-off rate

The percentage of users who entered a step but didn't complete it. See the full drop-off rate definition for the formula and worked examples. This is the primary diagnostic metric - you need it for every step, not just for the funnel as a whole.

Per-step drop-off rate

Drop-off rate = 1 − (users who completed step N ÷ users who entered step N)

1 − (380 ÷ 720) = 47% drop-off at step 3

What's actionable: The step with the highest volume of drops (users lost × rate), not necessarily the highest rate. A 15% rate on 800 users outranks a 40% rate on 80 users.

Decision rule: Compare the step against its own prior cohorts. Prioritise a material increase in lost users or drop-off after checking traffic mix, release version, and instrumentation.


2. Funnel completion rate

The percentage of users who complete your full onboarding flow - from entry event to final step.

Funnel completion rate

Completion rate = users who completed final step ÷ users who entered first step × 100

180 completed ÷ 1,000 entered = 18% completion rate

What's actionable: Compare week over week. A falling completion rate after a deploy is a regression signal. Improvement after a specific fix validates the change.

Decision rule: Compare the same funnel definition over time. Step count, entry intent, and acquisition source make generic completion targets unreliable.


3. Activation rate

The percentage of new users who reach the event that predicts long-term retention (your "aha moment"). Different from completion rate - the activation event may be after onboarding, or may be one specific step.

Activation rate

Activation rate = users who reached activation event ÷ new users × 100

340 reached 'first_project_created' ÷ 1,000 signups = 34%

What's actionable: If activation rate is lower than completion rate, users are finishing onboarding without experiencing value - move the value delivery earlier.

Decision rule: Use a stable internal cohort baseline and document the activation-event definition before comparing releases.


4. Time to activate

The median time from signup to reaching the activation event. This matters because users who experience value faster retain better.

What's actionable: Investigate a meaningful increase in time-to-activate relative to comparable cohorts. Segment by platform, version, and acquisition source before attributing the change to onboarding.

Decision rule: Set an internal target that matches the product's value-delivery cycle, then monitor its trend using the same event and time-window definition.


5. Retention split (completers vs. drop-offs)

The difference in day-30 retention between users who completed onboarding and users who abandoned it. This is the clearest measure of how much your onboarding matters.

CohortDay 7 retentionDay 30 retention
Completed onboarding38%22%
Did not complete onboarding9%3%

What's actionable: A large gap (3× or more difference) means increasing your onboarding completion rate is your highest-return retention investment.


6. Platform split (iOS vs. Android)

The difference in per-step drop-off rate between iOS and Android users. Treat a platform gap as a prompt to inspect implementation, traffic mix, and device-specific behaviour rather than assuming a single cause.

What's actionable: A 20%+ gap at the same step between iOS and Android is a signal to look for platform-specific bugs: broken layouts, permission dialogs that behave differently, or deep links that don't work on one platform.

! Note

Teams often attribute iOS vs. Android differences to "user quality" or "channel mix." In practice, most platform gaps are caused by code and UX differences that are fixable - not audience differences.


7. Step attempt count

For steps with forms or integrations, how many times users attempt the step before either completing or abandoning. A high attempt count before abandonment signals confusion or technical failure - not a willingness problem.

What's actionable: If median attempt count at a step is 3+ and drop-off is high, instrument error events to see what's failing. The problem is usually a confusing error message, an API that returns silent errors, or a validation rule that rejects valid input.


Which to look at first

If you're starting with no funnel data at all, add per-step instrumentation and build the funnel first. Everything else follows from having step-level data.

Once you have the funnel running:

  1. Fix the highest-volume drop-off step (metric 1)
  2. Track whether that moves funnel completion rate (metric 2)
  3. Confirm the activation rate improves (metric 3)
  4. Validate with retention split data (metric 5)

One sprint per step. One metric per intervention.


All 7 metrics in one dashboard

Step funnel, retention split, platform breakdown - no SQL

OnRamp tracks all seven of these metrics automatically once you call OnRamp.step() at each milestone. Three lines of code, live in minutes.

Start free trial →