Mobile App Churn Rate: How to Calculate and Reduce It
Churn rate is retention's mirror image, but most teams measure it as one number when it's really two different problems: users who never found value, and users who found it and left anyway.
What churn rate means
Churn rate is the percentage of users from a cohort who were active at the start of a period and did not return by the end of it. It's the direct inverse of retention rate - if day-30 retention is 30%, day-30 churn is 70%.
See the churn rate glossary entry for the short-form definition and formula.
Churn rate formula
Churn rate = 1 − (users retained at end of period ÷ users active at start of period)
Example: 1 − (300 ÷ 1,000) = 70% churn rate over 30 days
Teams often prefer tracking churn over retention for the same data because framing it as a rate to reduce - with a target ceiling and an alert threshold - is easier to act on than a rate to grow.
The number hides two different populations
A single churn rate blends two groups that churn for opposite reasons:
| Group | What happened | What fixes it |
|---|---|---|
| Onboarding churn | Never reached your activation event | Fix the onboarding funnel |
| Established-user churn | Activated, then stopped returning | Fix ongoing product value or re-engagement |
! Note
A blended churn number can stay flat while both underlying problems get worse - a rising onboarding churn rate and a falling established-user churn rate can cancel out in the aggregate. Split the cohort before you diagnose it.
Split your churned cohort by whether they ever reached your activation event. See user activation rate for how to define that event if you haven't already.
Why the split changes what you fix first
If most of your churn is onboarding churn, the fix is upstream: reduce drop-off in the funnel from signup to first value. See how to track onboarding drop-off for the instrumentation and how to reduce it for the process.
If most of your churn is established-user churn, the onboarding funnel isn't the problem - users are already getting through it. The fix is either the core product loop (does it deliver recurring value?) or a re-engagement trigger (does it remind users to come back at the right moment?).
Calculate churn separately for activated and non-activated users before deciding which team owns the fix.
How to calculate it correctly
- Define the period. Day-7 and day-30 are the most common windows; pick one and hold it constant so cohorts are comparable.
- Define "active." Usually a session or a specific event within the window - not just install.
- Take a cohort by start date, not a rolling snapshot of all current users. See retention cohort for why date cohorts avoid the mixing problem that makes DAU-based churn misleading.
- Split the cohort into activated and non-activated at the start of the window.
- Calculate churn separately for each group using the formula above.
✓ Tip
Report churn and retention side by side. They're mathematically redundant (churn = 1 − retention), but a stakeholder audience often reacts to a "70% churned" framing differently than "30% retained" - use whichever makes the trend legible to the people acting on it.
Is your churn rate normal?
There's no universal benchmark that applies across categories, price points, and usage frequencies - a daily habit app and a quarterly-use utility have structurally different churn curves. What's useful instead of a benchmark: your own release-over-release trend, split by activation status, on a fixed cohort window. See how to benchmark mobile app retention for the same method applied to the retention side of this number.
Measuring it with OnRamp
With OnRamp, you build a funnel from signup to your activation event, then compare retention (and its inverse, churn) between users who completed the funnel and users who didn't - as two separate cohort curves instead of one blended number. That split is usually enough to tell you in minutes whether the priority is an onboarding fix or a core-product fix.
Split churn by activation status
See which users are actually driving your churn rate
OnRamp splits retention and churn by funnel completion automatically, so you know whether to fix onboarding or the core product - without exporting to a spreadsheet.
Start 7-day trial →