Subscription cancellation reasons come down to five survey answers: too little usage (37%), cost (35%), a better app (10%), technical problems (7%) and other. Billing errors add cancellations the subscriber never chose. Usage and cost are the two biggest, and both are preventable.
Why subscribers cancel: the five reasons
The shares below are Google Play cancellation survey answers, reported in RevenueCat's State of Subscription Apps 2025 write-up. They are averages across many apps and will differ for yours.
| Reason | Share of cancellations | What it signals | First fix |
|---|
| Insufficient usage | 37.02% | The subscriber never built a habit, often an activation problem | Show value earlier in onboarding |
| Cost concerns | 34.64% | Price, perceived value or affordability, three different problems | Split by discount and trial cohorts, add a cheaper tier |
| Other | 11.68% | A reason the survey did not name | Ask cancelling users a short open question |
| Found a better app | 9.54% | A competitor won on value or features | Make the unique value clearer in the paywall and first run |
| Technical issues | 7.12% | Crashes, bugs or failed purchases | Watch cancellations by app version |
Survey answers cover subscribers who turned off renewal. Cancellations the store forced through a failed charge sit outside this table and are covered under billing errors below.
See your own cancellation reasons in ActivationPal
Survey averages tell you what is common. Your own events tell you what is happening in your app. ActivationPal stores RevenueCat webhook events as rc_cancellation (with cancel_reason), rc_billing_issue and rc_expiration, next to your onboarding and paywall events.
The stats snapshot counts cancellations per cancel reason, plus billing issues and expirations. A refund is counted as its own reason, separate from voluntary cancels. The same numbers are available through the agent API and MCP, so you can ask for them from a coding agent as well as read them on the dashboard.
Setup is one webhook per store app: follow the RevenueCat webhook docs.
Cancel reason codes in RevenueCat
The cancel_reason on each rc_cancellation event is RevenueCat's own code. These are the ones that matter when you group cancellations in your own data, as listed in RevenueCat's event types:
- UNSUBSCRIBE: the subscriber turned off renewal. This is the group the survey reasons above apply to.
- BILLING_ERROR: a CANCELLATION event where the store could not charge the subscriber. It is not a choice, so it counts as involuntary churn.
- CUSTOMER_SUPPORT: a refund. Keep it apart from voluntary cancels.
- Price increase: PRICE_INCREASE_CONSENT_REQUIRED and PRICE_INCREASE_CONSENT_APPROVED are separate events, sent for App Store and Google Play. Subscribers who were asked to consent and did not are the ones to watch around a price change.
Two details prevent miscounts. CANCELLATION covers both cancels and refunds. BILLING_ISSUE is a failed charge attempt and does not mean the subscription has expired yet. The full list is in the RevenueCat webhook events guide.
Not enough usage
RevenueCat frames low usage as an activation problem as much as a retention problem: the subscriber never got to the point where the app was useful.
Find out whether people leave early or late in their first weeks, and which milestones they passed before they did. Start at the beginning of the journey, with onboarding, then move to habit-building. The guide to mobile app onboarding covers the first-run flow and where to measure drop-off.
Cost concerns
"It's too expensive" covers three different things: the subscriber found a cheaper price elsewhere, does not think the app is worth the price, or can no longer afford it. Each needs a different fix, so separate them before changing a price.
- Check discount and trial cohorts. RevenueCat describes one analysis where customers who signed up at 50% off had a £50 lower LTV and a far higher churn rate than full-price customers.
- Separate the preventable from the unpreventable. A lifestyle change is not a pricing problem. "Not worth the price" is.
- Offer a downgrade. A cheaper tier can keep a subscriber who does not use every feature. Duolingo added Max as a higher tier instead of raising the price for everyone, so users chose the level that suited them.
For the plan side of this question, see annual vs monthly subscription.
Billing errors
Billing errors are the second-largest group in the store expiration data, which covers 99.5 million entries. On Google Play they account for 28.2% of expirations, against 15.1% on the App Store.
A billing error is not a decision. The subscriber did not choose to leave, which makes it involuntary churn. The split is explained in voluntary vs involuntary churn.
The fix sits in retry and grace handling plus a prompt asking the subscriber to update their payment method. To see whether it works, count rc_billing_issue events per period and compare them with the BILLING_ERROR cancellations that follow.
Found a better app and technical issues
Subscribers who leave for a better app are telling you the value was not clear or not unique. Say what only your app does on the paywall and in the first session.
Technical issues are 7.12% overall but weigh more in some regions: 13.36% in Middle East & Africa. Check cancellations by app version after each release. A spike on one version points to a bug, not to the product.
Cancellation reasons by region
The same survey breaks down by region, and the mix changes:
- India & Southeast Asia has the highest share of usage cancellations, at 40.79%.
- Western Europe has the highest share of cost-related cancellations, at 38.48%.
- Middle East & Africa has the highest share of technical issues, at 13.36%.
By category, RevenueCat reports gaming with the highest share of price-related cancellations and travel with a low one. If you have no data of your own yet, these patterns suggest which reason to check first for your audience.