Value Metric
Drop-Off Rate
Drop-Off Rate is the percentage of users who abandon a flow before completing it.
What is Drop-Off Rate?
Drop-Off Rate measures the share of users who leave a funnel or flow — signup, onboarding, checkout — before reaching the end. Measured step by step, it pinpoints exactly where a process leaks users, making it one of the most actionable diagnostics in product analytics.
Every flow has some drop-off; the goal is to find the steps where it is abnormally high and understand why, then remove the friction causing it.
How to calculate it
Drop-Off Rate = Users Who Left at a Step ÷ Users Who Entered That Step × 100
- Users Who Left
- Users who abandoned at the step without continuing
- Users Who Entered
- Users who reached that step
Worked example
If 400 of 1,000 users who reach the payment step leave without completing it, that step’s drop-off is 400 ÷ 1,000 × 100 = 40%.
What good looks like
- Relative, step-by-stepFind the spikes
There is no absolute target; the value is comparative. Map drop-off at each step and focus on the steps that leak the most.
Why it matters
Drop-off turns a vague sense that "users aren’t converting" into a precise map of where and how badly a flow leaks. Because it isolates individual steps, it tells you exactly where a fix will have the most impact — often recovering conversions far more cheaply than adding traffic.
How to improve Drop-Off Rate
Attack the biggest leak first
Rank steps by drop-off, then reduce friction at the worst one — fewer fields, clearer copy, faster load — and A/B test the change.
Understand the "why" behind the drop
Pair the quantitative drop-off with usability sessions or interviews to learn what confuses or blocks users at that step.
Frequently asked questions
How is drop-off rate different from bounce rate?
Bounce rate measures visitors who leave after viewing a single page without interacting. Drop-off rate measures users who abandon within a multi-step flow. Drop-off is more actionable for funnels because it localizes exactly which step loses users.
How do you reduce drop-off at a specific step?
First confirm the step is a genuine outlier, then reduce its friction: remove unnecessary fields, clarify what to do next, speed up load times, and reassure users about risk (cost, privacy). Validate each change with an A/B test.