iOS subscription analytics: MRR, churn rate, and LTV explained for indie developers

Learn how to track the three metrics that actually predict subscription health on iOS — MRR, churn rate, and customer lifetime value — using App Store Connect and third-party tools, and how reading them together changes your pricing and retention decisions.

Most iOS developers track downloads. Some track revenue. Fewer track the metrics that actually predict whether their subscription business is healthy or quietly deteriorating. Monthly Recurring Revenue (MRR), churn rate, and Customer Lifetime Value (LTV) are the three numbers that matter most — and reading them together changes how you price, how you design trials, and how you decide where to grow next.

This post walks through each metric, explains how to find it inside App Store Connect and third-party tooling, and shows how the three interact in ways that single-number dashboards routinely obscure.

The three core subscription health metrics

Before anything else, it helps to agree on definitions. Subscription analytics tools vary in how they calculate these numbers, and comparing an App Store Connect figure to a RevenueCat figure without understanding the methodological difference is one of the most common sources of confusion indie developers report.

Benchmarks are directional only, drawn from publicly available RevenueCat and Sensor Tower commentary. Your category, price point, and target audience shift these figures significantly.

Where to find your numbers: App Store Connect vs third-party tools

Apple provides a baseline analytics view inside App Store Connect under Analytics → Subscriptions. The dashboard shows active subscriptions, new subscriptions, cancellations, and a rough day-30 and day-60 retention curve. For a first look at subscription health, it is genuinely useful. Its limitations, however, are meaningful.

Revenue figures in App Store Connect represent gross proceeds before Apple's commission is deducted. Your actual net figures live in the Financial Reports section — a separate CSV export that carries a 30-day lag. The two numbers are easy to confuse in conversation and in forecasting spreadsheets. Additionally, Apple does not expose a direct LTV figure, a subscription-level cohort breakdown, or trial-to-paid conversion rates by introductory offer type in the analytics UI.

For deeper analysis, most serious subscription developers reach for a third-party SDK. RevenueCat's dashboard surfaces MRR, active trials, conversion rates, and cohort retention curves in real time, normalised to USD regardless of the storefront. Sensor Tower and AppFollow add competitive benchmarking context — useful for determining whether your churn rate reflects an app-specific problem or a category-wide pattern in your vertical.

Churn rate: the metric that compounds quietly

Churn is where subscription businesses erode slowly without noticing. The mathematics work against you exponentially over time, and the effect is large enough to overwhelm strong acquisition numbers if it goes unmanaged.

Consider a simple scenario: you charge $4.99 per month and acquire 1,000 subscribers in January. At 5% monthly churn, you retain roughly 540 of them after 12 months. At 8% monthly churn, you retain around 370. That difference — 170 subscribers — is paying you $849 per month less, every month, before you have acquired a single new user in the subsequent year.

Voluntary churn (users actively cancelling) and involuntary churn (failed card charges) behave differently and require different responses. Apple's billing retry and grace period system handles a portion of involuntary churn automatically — subscribers who hit a failed renewal enter a short grace period during which the app remains accessible while Apple retries the charge. If you cut off access immediately on a renewal failure before understanding this system, you risk turning a recoverable payment issue into a permanent cancellation. The post on iOS grace periods and billing retry mechanics covers this in detail.

Voluntary churn, on the other hand, is almost always a signal about perceived value relative to price. RevenueCat's published analysis has consistently highlighted that churn spikes at the first renewal — subscribers who forgot they signed up, or who re-evaluate value after a trial ends and a real charge appears. This is why the first 30 days of a paid subscription are disproportionately important: the onboarding experience during this window often determines whether a subscriber stays for six months or disappears at month one.

Trial conversion rate: the multiplier on everything else

If you offer a free trial — and for most subscription categories, research from Phiture and RevenueCat suggests you should — your trial-to-paid conversion rate is arguably the single most leveraged metric in your entire funnel. A one-percentage-point improvement in conversion translates directly to a proportional lift in MRR with no additional acquisition spend.

Industry commentary suggests that trial conversion rates vary widely by category: productivity and utility apps often see 30–50% conversion from 7-day trials, while entertainment or social apps tend toward the lower end of that range. These are directional figures, not universal truths. Your paywall design, trial length, and the clarity of your value proposition during the trial period all move the number. The posts on trial length trade-offs and introductory offer types go deeper on the specific levers.

The conclusion is obvious but easy to underweight: improving conversion from 20% to 40% doubles your MRR from the same acquisition volume. For an indie developer with limited marketing budget, optimising the trial-to-paid handoff — paywall copy, feature gating, onboarding depth — often returns more than doubling paid acquisition spend.

Lifetime value and what it tells you about pricing

LTV is where the previous metrics converge into actionable pricing decisions. Using the simplified formula — average monthly revenue per subscriber divided by monthly churn rate — you can calculate the expected total revenue from a subscriber over their lifetime with your app.

At $4.99/month with 5% monthly churn: LTV ≈ $4.99 ÷ 0.05 = $99.80. At 3% monthly churn with the same price: LTV ≈ $166. Halving your churn — genuinely hard to do — nearly doubles lifetime value. Raising your price from $4.99 to $6.99 while holding churn constant yields a roughly 40% LTV improvement that is often easier to achieve than a structural retention improvement.

This is one of the strongest quantitative arguments for periodic price increases on established subscription apps. If your churn rate is stable, a modest price increase that retains most existing subscribers lifts LTV without requiring any improvement in retention mechanics or acquisition efficiency. The Apple grandfathering rules govern how you can apply increases to existing subscribers — new subscriber pricing can be raised immediately, while existing subscribers require a separate notification flow. The post on Apple subscription price grandfathering covers the precise rules.

Cohort analysis: why aggregate numbers mislead

Total subscriber counts and aggregate MRR feel like the most concrete metrics, but they can mask a deeply unhealthy underlying dynamic. A subscription business can grow its total active subscriber count while its cohort retention is getting worse — if acquisition is outpacing churn in absolute terms, the headline number looks fine. The deterioration only becomes visible when acquisition slows, and by then the churn problem is entrenched.

Cohort analysis fixes this by grouping subscribers by the month they first paid and tracking what fraction remain active at each subsequent month. A healthy subscription app shows cohort curves that flatten: churn is highest at month 1, drops sharply at months 2–3, and settles at a lower steady-state loss rate thereafter. An unhealthy app shows curves that keep declining steeply through month 6 without finding a floor.

RevenueCat's dashboard exposes cohort retention curves directly, which is one of the clearest arguments for integrating the SDK early — before you have the subscriber volume to make the data statistically meaningful. App Store Connect does not surface cohort data in this form. If you are operating without a third-party analytics layer, you can approximate cohort behaviour by exporting monthly Financial Reports CSVs and comparing subscriber counts period-over-period, but the signal is noisy and requires manual work to interpret.

A minimum viable metrics practice for indie developers

Tracking every possible subscription metric is counterproductive for a small team. A minimum viable practice that surfaces the right signals without generating paralysis looks like this:

• MRR — from a single source, reviewed monthly. Flag month-over-month declines of more than 3% as requiring a cause investigation before the next development cycle.
• Monthly churn rate — tracked at the cohort level, not just as a rolling aggregate. Pay particular attention to month-1 renewal rates; industry data from RevenueCat consistently identifies the first renewal as the highest-risk churn point.
• Trial-to-paid conversion rate — per introductory offer type if you run more than one. A 5-percentage-point drop in conversion rate across two consecutive months is a meaningful signal, not noise.
• LTV segmented by storefront — at minimum, separate your top three revenue storefronts. Aggregated global LTV is directionally interesting but rarely actionable.

Review these four data points on a fixed monthly schedule. Most iOS subscription problems are visible in these metrics four to eight weeks before they show up as a meaningful decline in total revenue — which is usually enough lead time to diagnose and respond, if you are looking.

Sources and further reading

• RevenueCat blog — subscription benchmarks, cohort data, and industry analysis
• Apple Developer — Viewing subscription metrics in App Store Connect
• Phiture Mobile Growth Stack — retention and subscription growth frameworks
• AppFollow blog — App Store analytics and subscription tracking guides
• Sensor Tower blog — subscription market trends and category benchmarks