iOS subscription pricing audit checklist: quarterly health checks for subscription app developers

A practical 10-point checklist of pricing, localization, and analytics health checks every iOS subscription developer should run each quarter to catch revenue leakage before it compounds.

Running an iOS subscription business without a regular pricing audit is like steering by looking in the rearview mirror. Apple's territories shift, exchange rates move, introductory offer eligibility resets, and the competitive landscape changes — often faster than quarterly release cycles. A structured health check, run every three months, catches revenue leakage before it compounds.

This checklist organises ten high-impact checks into four work areas. Each item maps to a specific tool or report inside App Store Connect, so you can move through the list without guesswork. Think of it as the maintenance schedule your subscription stack deserves.

Why quarterly is the right cadence

Many developers review pricing reactively — after a currency shock, after a churn spike, or after a competitor pivots. Reactive reviews are costly: RevenueCat has noted in published data that developers who respond to pricing problems after they appear in revenue charts are already weeks behind the underlying cause, because App Store Connect reporting can lag real-world transactions by 24–72 hours, and cohort-level signals may take several billing cycles to surface clearly.

A quarterly cadence aligns with Apple's own operational rhythm. Apple typically adjusts automatically-managed prices in response to exchange rate movements on a roughly quarterly basis, and promotional offer eligibility windows often run 30–90 days. Quarterly reviews also coincide naturally with fiscal quarters, making it easier to incorporate findings into budgeting and road-map discussions.

For a deeper look at how to structure the review calendar, see our post on App Store pricing review cadence. For the metrics concepts referenced throughout this checklist, our subscription analytics explainer covers MRR, churn rate, and LTV in detail.

Pricing tier and localization checks

The first work area covers what customers actually see when they land on your paywall: the price, the currency, and the framing. These are the checks with the most direct impact on conversion and the easiest to let slip between releases.

Check 1: Verify territory coverage against your active installs

Pull your active install geography from App Store Connect Analytics (or your analytics SDK). Cross-reference it against your territory pricing configuration. Any territory with more than one percent of installs but no explicit local price is a candidate for localisation — and a potential source of revenue uplift. Markets in Southeast Asia, Latin America, and the MENA region are particularly prone to being left on default USD tiers that effectively price out local users.

Check 2: Review automatically-managed price adjustments

Navigate to App Store Connect → your app → In-App Purchases → your subscription → Pricing. Apple flags territories where it has auto-adjusted prices due to exchange rate movements. Review each flagged territory and decide whether to accept Apple's suggestion or override with a manual local price. Auto-adjustments maintain purchasing-power parity with your base currency, but they do not account for local competitive positioning or deliberate PPP corrections you may have applied. In markets with high exchange rate volatility — Turkey and Argentina being persistent examples — auto-adjusted prices can drift significantly from the price point that converted well six months ago.

Check 3: Audit price points for psychological alignment by currency

Not all .99-style price endings translate well across markets. In territories where prices are conventionally quoted in whole numbers (Japan, South Korea) or where the local equivalent of a charm price differs from the Western convention, a tier that lands on an awkward denomination can suppress conversion. The table below illustrates the most common misalignments developers encounter in high-volume markets:

Check 4: Confirm subscription metadata is localised in your top markets

Subscription display names and promotional text surface on the system subscription management sheet — the screen users see immediately before subscribing and when they manage their subscription from device Settings. Research from Phiture suggests that localised subscription metadata in the user's native language correlates with higher conversion at the purchase confirmation step. Run through your top-ten markets and verify that at least the display name and promotional text fields are translated, not just the app description. A useful shortcut: filter App Store Connect Analytics by territory and sort by subscription starts; the markets near the top of that list with untranslated metadata are your highest-value localisation targets.

Subscription funnel and metrics health checks

The second work area diagnoses how your pricing is performing in practice. These checks require pulling data from App Store Connect Analytics, your subscription SDK, or both — and comparing against external benchmarks to distinguish normal variation from genuine problems.

Check 5: Benchmark trial-to-paid conversion by territory

Pull the conversion rate from free trial start to paid subscription, segmented by territory. Large gaps between high-income and low-income markets are expected — but significant gaps between markets of similar purchasing power (Australia vs Canada, or Germany vs France) often indicate a localisation mismatch worth investigating. RevenueCat's published benchmark reports segment conversion rates by app category; use those as directional targets, recognising that app-specific product factors always dominate. If your conversion in a specific market has dropped since the last auto-price adjustment, that correlation is worth following up before attributing the change to a product issue.

Check 6: Review voluntary churn against category benchmarks

Voluntary churn — cancellations the user initiates — is the clearest direct pricing signal available. If voluntary churn in a specific market is running two to three percentage points above your overall average, and that market has seen an auto-price adjustment recently, the two events may be connected. Industry research cited by SensorTower and AppFollow consistently finds that price increases above ten percent are associated with measurable short-term churn spikes, particularly in mid-income markets. Compare your numbers against category benchmarks from sources like our 2026 churn benchmark post to distinguish a pricing problem from a product retention problem before deciding on a response.

Check 7: Calculate revenue-per-install by territory

Divide subscription revenue by active installs for each territory. This metric normalises for market size and surfaces markets where you have meaningful traction but are undermonetising relative to your global average. A territory with high install share but below-average revenue-per-install is a localisation opportunity — not necessarily a price increase, but potentially a paywall copy update, a better introductory offer, or a new price tier test. In App Store Connect Analytics, the "Proceeds per paying user" metric (under Subscriptions) gives you a closely related signal without requiring manual calculation.

Offer mechanics and conversion checks

Introductory offers and promotional offers are Apple's primary levers for subscription acquisition and win-back. They also come with eligibility rules that are straightforward to misconfigure and hard to diagnose without a deliberate audit process.

Check 8: Audit introductory offer territory coverage and eligibility rules

Open each active subscription product in App Store Connect and verify that introductory offers are enabled for every territory where you have active users. A common oversight: an introductory offer is configured for the primary market but never toggled on for added territories — meaning new users in those markets never see the free trial that anchors conversion. Apple's offer eligibility rules also affect lapsed subscribers: a user who cancels and re-subscribes after a defined gap may or may not be eligible for a new introductory offer depending on your subscription group structure. Review the Apple developer documentation on introductory offer eligibility to confirm your group architecture produces the behaviour you intend. For related mechanics around price changes and existing subscribers, see our post on Apple's grandfathering rules.

Check 9: Review and prune your active promotional offer inventory

Promotional offers — win-back and retention discounts — require manual creation in App Store Connect and do not expire automatically. They persist until you remove them. Run through your promotional offer inventory and remove any that correspond to campaigns that have ended. Stale promotional offers create two compounding problems: they can be surfaced unexpectedly by third-party tools or in-app messaging platforms, and they clutter your offer reporting, making it harder to measure the incremental impact of campaigns that are still active. Best practice is to name promotional offers with a campaign identifier and end date in the internal notes field, so auditing is a read-through rather than a reconstruction exercise.

Automation and reporting infrastructure checks

The final work area is administrative, but its effects compound silently. Broken webhooks and stale API tokens degrade your ability to act on everything surfaced by checks 1–9 — and they rarely announce themselves with an obvious error.

Check 10: Validate App Store Server Notifications delivery

Apple delivers subscription lifecycle events — renewals, cancellations, billing failures, refunds — via App Store Server Notifications (version 2). Open your App Store Connect notification configuration and confirm the endpoint URL is responding with a 200 status. Then cross-reference a sample of recent events against your subscription SDK or internal database: if your records are missing renewal events that App Store Connect shows as succeeded, your endpoint is dropping events or your handler has a silent bug.

Billing failure notifications (the DID_FAIL_TO_RENEW notification type) deserve special attention. If they are not reaching your system reliably, you cannot trigger grace period prompts or win-back flows — and involuntary churn accumulates without any signal until it appears in monthly revenue numbers. Setting up a dead-letter queue or a simple alerting rule on your notification endpoint's error rate is a worthwhile infrastructure investment that pays off at each future audit: if the error rate spikes between quarterly checks, you will know immediately rather than discovering the problem three months later.

Once you have worked through the full checklist, document the findings and the actions taken — even a simple spreadsheet row per check per quarter builds a historical record that makes future audits faster and helps you correlate pricing changes with revenue outcomes over time. The goal is not a perfect pricing configuration (that does not exist) but a consistently improving one.

Sources and further reading

• Apple Developer: Implementing introductory offers in your app
• Apple Developer: App Store Server Notifications reference
• RevenueCat: Subscription benchmark report (conversion and churn data by category)
• Phiture: App subscription metrics and benchmarks overview
• Apple App Store Connect Help: Set a subscription price
• World Bank: International Comparison Program (PPP data)