iOS subscription metrics beyond MRR and churn: the signals most developers ignore

MRR and churn are necessary but not sufficient. This guide covers eight operational metrics—trial start rate, post-intro renewal rate, billing retry recovery, and more—that surface problems before they reach your revenue line.

MRR and churn are the headline numbers for any subscription business. Every analytics dashboard, every App Store Connect summary, every quarterly review starts there. But if those are the only two numbers on your subscription dashboard, you are navigating by a compass that only shows north and south. The metrics that explain why MRR grows or shrinks—and predict where it is headed—live one layer below, in operational signals that most iOS developers never instrument.

This post walks through eight metrics that deserve their own charts, where to pull each one, and what to do when a number looks wrong.

Why headline metrics lag the real signal

MRR is a lagging indicator. By the time a churn spike registers in your monthly revenue figure, the subscribers who drove it made their cancellation decision two to four weeks earlier. If your paywall copy broke in a localization update, or your renewal flow started failing on a new OS version, you will see it in MRR only after the damage has compounded across a full billing cycle. Watching MRR in isolation is useful for trend confirmation—it is not useful for rapid diagnosis.

Aggregate churn rate has the same problem, and adds a second: it hides composition. A monthly churn rate of 7% looks identical whether new subscribers are churning in month one while long-term subscribers renew reliably, or whether long-term subscribers are quietly leaving after a price change. The shape of churn by cohort tells a completely different story than the aggregate rate, and that shape is where the actionable signal lives.

Trial metrics: the funnel before the funnel

For any subscription app with a free or discounted trial, a substantial portion of the subscriber lifecycle occurs before the first billable event. Two metrics that belong on every subscription dashboard:

Trial start rate is the share of users who see your paywall and choose to begin a trial. This metric lives in App Store Connect Analytics under Subscription Events (look for "Subscription Trial Started"). Research from the ASO community—including analysis published by Phiture on their Mobile Growth Stack—suggests that trial start rates vary widely by paywall design, by category, and by traffic quality. The number itself matters less than its movement over time; a declining trial start rate after an app update is an early signal that a paywall or onboarding change is not resonating.

Trial-to-paid conversion rate measures how many started trials convert at the end of the trial window. RevenueCat's benchmark reports have historically shown that conversion rates distribute broadly across the App Store, with significant category-level variation. Apps in high-intent categories—task management, language learning, personal finance—tend to convert at higher rates than general entertainment. The important cut is not the average but the conversion rate segmented by trial length, by locale, and by acquisition channel; each of those dimensions reveals a different lever.

Neither metric is included in your aggregate churn rate. A trial that expires without converting is not a churn event in Apple's reporting—it is a trial that did not convert. If you are not tracking trial start rate and trial-to-paid conversion separately, you are missing the widest part of your funnel. The App Store Connect Analytics subscription funnel guide covers where to find these events in the dashboard.

Introductory offer utilization and post-intro renewal

If you have enabled introductory offers—a free trial, a discounted first month, or a pay-upfront offer at a reduced price—you need two additional metrics.

Introductory offer utilization rate = (new subscribers who used an intro offer) ÷ (all new subscribers in the period). A high utilization rate is not inherently good or bad; it changes what your LTV model needs to assume. RevenueCat analysis has indicated that subscribers acquired through discounted introductory offers show somewhat different early-period renewal behavior than subscribers who paid full price from the start—a pattern consistent with price-sensitivity selection effects. If your introductory offer is disproportionately attracting bargain hunters rather than engaged users, downstream LTV will not match your acquisition math.

Post-intro renewal rate = (subscribers who renew at full price after the intro period) ÷ (subscribers who completed the intro period). This is not the same as your overall renewal rate, and it is far more diagnostic. A low post-intro renewal rate—subscribers converting into a trial or discount, then not staying at full price—points to an onboarding and activation problem more than a pricing problem. The app is not delivering enough demonstrated value during the intro window to justify the full subscription cost.

Upgrade rate and resubscription rate

Two metrics that reveal the ongoing health of your subscriber relationship beyond initial acquisition:

Monthly-to-annual upgrade rate = (monthly subscribers who switch to annual in a period) ÷ (active monthly subscribers at the start of the period). Annual subscribers churn at dramatically lower rates than monthly subscribers—RevenueCat's published industry data has consistently shown annual plans retain subscribers at a substantial multiple of the monthly retention rate, with the gap most pronounced in the first six months. Converting even a small percentage of your monthly base to annual each quarter is one of the highest-leverage levers available without changing your underlying product. This metric tells you whether your upgrade prompts, annual plan positioning, and promotional offers are working.

Resubscription (win-back) rate = (expired subscribers who resubscribe) ÷ (subscribers whose subscription expired in a given cohort month). Research from Phiture and others in the subscription retention space suggests that a meaningful fraction of churned subscribers will return within 90 days if engaged with targeted messaging or an appropriate offer. iOS promotional offers are explicitly designed for this use case—they are available only to subscribers who have previously paid and have not previously used the specific offer type. Segmenting your resubscription rate by time-to-resubscribe (within 30 days, 31–90 days, 91+ days) shows how quickly your win-back funnel operates and where it breaks down.

Renewal success rate and involuntary churn decomposition

Your aggregate churn rate combines two fundamentally different phenomena that require different interventions:

• Voluntary churn: the subscriber explicitly cancelled. This is a product and value delivery problem.
• Involuntary churn: payment failed, the grace period elapsed, and the subscription lapsed. This is a payment recovery problem—and it is substantially more fixable.

Renewal success rate = (successful renewals) ÷ (renewal attempts in the period). This is not equivalent to 1 − churn rate. A subscription that fails on the first attempt but succeeds during Apple's billing retry window is a recovered renewal, not lost revenue. Apple's billing retry can run for up to 60 days after a failed renewal, and the grace period gives subscribers continued access for up to 16 days during that window. A renewal that eventually recovers costs you nothing in subscriber lifetime—only a cash flow timing difference.

Tracking billing retry recovery rate—(renewals that initially failed but eventually succeeded) ÷ (all renewals that initially failed)—tells you how effectively Apple's infrastructure is recovering revenue on your behalf, and whether targeted in-app or push messaging during the retry window would lift that rate further.

You can decompose voluntary versus involuntary churn using App Store Server Notifications v2. The EXPIRED notification carries an expiration reason field: VOLUNTARY_CANCELLATION versus BILLING_ERROR separates the two populations clearly. See the iOS involuntary churn guide for a full breakdown of how to build a recovery flow around these events.

Subscriber lifetime and LTV by cohort

LTV is not a single number—it is a distribution. A subscriber who churns after two months and one who churns after 36 months are both counted as "churned" but their revenue contribution differs by an order of magnitude. Tracking median subscriber lifetime alongside the mean matters because subscriber lifetimes are right-skewed: a small population of long-term subscribers contributes disproportionately to total revenue, and the mean overstates what a typical subscriber is worth.

More importantly, LTV varies substantially by acquisition channel, by introductory offer type, and by geography. For subscription apps operating across markets with different purchasing-power levels—a topic the iOS subscription churn in low-PPP markets post covers in depth—a single blended LTV figure conflates subscribers paying $9.99/month in the US with those paying ₹149/month in India. Separate LTV models for each major cohort dimension are the foundation of sound pricing and acquisition channel decisions.

App Store Connect's Subscriber Retention report provides survival curves by subscription type and cohort start date. The survival curve shows what fraction of a cohort is still active at each period since subscription start—this is the empirical basis for any LTV estimate. The cohort retention analysis guide covers how to read and act on that report.

Building a monitoring cadence

The practical challenge is not knowing which metrics matter—it is building a review rhythm that surfaces anomalies before they compound into an MRR decline. A workable cadence for a subscription app with meaningful scale:

• Daily: renewal success rate and billing retry recovery rate, via App Store Server Notifications or your subscription SDK dashboard. Involuntary churn spikes often appear within 24 hours of a new app version shipping, when StoreKit calls begin failing on updated devices.
• Weekly: trial start rate, trial-to-paid conversion, post-intro renewal rate, and upgrade rate. These move more slowly but trend-break within a week of a significant paywall or onboarding change.
• Monthly: resubscription rate, subscriber lifetime by cohort, LTV by acquisition source. These require a full billing cycle or more to stabilize before the numbers are meaningful for decision-making.

App Store Connect's Reports API can automate the daily pull if you have built a reporting pipeline. Your subscription management SDK—RevenueCat, Adapty, or Purchasely—will surface most weekly metrics natively in its dashboard. The goal is not a dashboard with fifteen charts; it is a monitoring setup where the first anomaly in any of these metrics reaches you before it reaches your MRR.

Sources and further reading

• Apple Developer: App Store Server Notifications documentation
• RevenueCat blog: subscription benchmarks and growth research
• Phiture Mobile Growth Stack: ASO and subscription retention analysis
• Apple: View subscription analytics in App Store Connect
• Apple Developer: StoreKit subscriptions overview