Churn rate is the percentage of users who stopped returning to your app or game within a given period. It's the flip side of retention — and one of the clearest signals that something in your product or onboarding isn't working.
What Is Churn Rate?
Churn rate shows how fast you're losing users. If 1,000 people installed your game last month and 650 never came back, your monthly churn is 65%.
That number affects everything: audience size, UA payback period, and revenue. High churn means you're running faster just to stay in place — spending on acquisition while the bucket leaks.
For F2P mobile games, losing 60–70% of users in the first week is common. For subscription apps, monthly churn above 10% is a warning sign. The goal isn't to eliminate churn — it's to understand when and why it happens, so you can fix the right thing.
What is churn rate and how to measure it →
How to Calculate Churn Rate
Formula:
| Churn Rate = (Users at start of period − Users at end of period) / Users at start of period × 100% |
|---|
Example: You started July with 10,000 active users. By July 31, 7,200 were still active. Churn = 28%.
How you define "inactive" matters. Common thresholds:
- Subscription apps — user cancelled their subscription
- F2P games and other apps — user hasn't opened the app in 7, 14, or 30 days (pick one and stick with it)
There's no universal rule. What matters is that you apply the same definition consistently across cohorts so comparisons are valid.
Why Churn Rate Matters
Audience size. If your D7 churn is 80% and you're acquiring 5,000 users a week, you're starting every new week with 1,000 survivors from the previous one. Growth stalls fast.
Revenue. Paying users who churn take their LTV with them. A stable base of retained payers is worth far more than a constant stream of one-time buyers.
UA efficiency. If your CPI is $2.50 and churned users generate $0.40 before leaving, you'll never hit payback. Tracking churn by acquisition channel shows which sources bring users who actually stay.
What Is a Good Churn Rate for Mobile Games and Apps?
Industry averages give you a starting point.
For mobile games:
| Period | Casual / Hyper-casual | Mid-core | Hard-core / RPG |
|---|---|---|---|
| Day 1 churn | 60–70% | 50–60% | 40–55% |
| Day 7 churn | 80–85% | 70–80% | 60–75% |
| Day 30 churn | 90–95% | 85–90% | 75–85% |
For mobile apps:
| App type | Healthy monthly churn | Warning sign |
|---|---|---|
| Subscription app | < 5% | > 10% |
| Utility / productivity | < 8% | > 15% |
| Social / community | < 6% | > 12% |
These are industry averages based on aggregated market data. Your numbers will vary depending on genre, region, platform, and monetization model.
If your Day 1 churn is 75% in casual — that's worth investigating. If it's 45% in a strategy game, you're doing something right. Numbers only make sense in context.
How to Track Churn Rate
Track churn separately for different user groups — the numbers tell different stories:
Paying vs. non-paying users. Paying users churning is a monetization emergency. Non-paying users churning in the first few days might just be normal early drop-off.
By install cohort. Compare D7 churn of users who installed before vs. after a major update. That's how you catch regressions fast. devtodev's cohort reports show this split without manual SQL.
By acquisition channel. Users from different sources often have very different churn profiles. A channel with low CPI but 90% D7 churn isn't cheap — it's expensive.
How to Reduce Churn Rate in Mobile Apps and Games
The fix depends on where users are leaving. Diagnose first, act second.
D1 churn is high → onboarding problem. Most users who leave on Day 1 didn't understand the product or hit friction immediately. Analyze your tutorial funnel step by step. Look at where session depth drops — that's your bottleneck. Fix it before spending more on UA.
D7 churn is high → engagement loop problem. Users liked the first session but didn't find a reason to return. Push notifications help here — but only if the message is relevant. A generic "Come back!" won't move D7. A contextual trigger tied to where the user left off can. For apps, this is where onboarding email sequences matter most.
D30 churn is high → monetization or value delivery problem. For games: long-term users often churn when aggressive monetization disrupts gameplay. Review your paywall timing and offer frequency for users past Day 14. Check ARPPU dynamics — if it's dropping among 30-day users, they're spending less before leaving. For subscription apps: D30 churn usually means the product didn't deliver enough value to justify renewal. Look at feature adoption — are users actually using what they're paying for?
Segmented re-engagement. Churned users aren't one group. A paying user who went quiet after Day 20 responds to a different message than a never-payer who left on Day 3. devtodev's churn prediction flags at-risk users before they leave — so you can act while there's still time.
Learn more about identifying and re-engaging churned users →
Takeaways
- Churn rate measures the percentage of users who stopped using your app or game in a given period — and directly affects revenue, audience size, and UA ROI.
- Define "churned" consistently: subscription cancellation, or X days of inactivity. Apply the same threshold across all cohorts.
- Benchmarks vary by type: for F2P games, 60–70% first-week churn is common; for subscription apps, monthly churn above 10% is a warning sign.
- D1, D7, and D30 churn point to different root causes — onboarding, engagement loop, and monetization respectively.
- Segment churned users by payment status and acquisition channel before acting — different groups need different responses.
- Diagnosis first: funnel analysis and session data before push campaigns.
Track D1, D7, and D30 churn across cohorts without writing a single SQL query. Explore devtodev →