The MENA founder’s guide to App Store Connect: subscription analytics deep dive
App Store Connect’s subscription dashboard is the most under-read piece of growth infrastructure most MENA founders have access to. RevenueCat gets the credit for “the subscription dashboard” in most stacks. But App Store Connect has data RevenueCat does not — it is what Apple itself sees, and it surfaces signals about your subscription business that no third-party tool can fully reconstruct.
The catch is that the dashboard is dense, the metric names overlap in confusing ways, and a few of them are quietly different from what their labels suggest. Founders who do not understand what each number actually measures will make pricing, retention, and acquisition decisions on the wrong signal.
Here is what each of the core subscription metrics actually means, what to use it for, where the MENA-specific signals live, and which Apple reporting bugs to know about.
The four “subscriber” metrics that are not the same thing
App Store Connect surfaces four metrics that all sound like “how many people are paying me”:
- Active Subscribers
- Subscribers
- Paid Subscribers
- Recoverable Cancellations
They are different metrics. Here is what each one is.
Active Subscribers
The count of users who, at the time the report was generated, have an active subscription entitlement — paying or in a free trial or in an introductory offer or in a grace period. This is the number you want when answering “how many people have access to my paid features right now?” It includes everyone with a valid entitlement, regardless of whether they have actually paid yet.
It is also the number that most overstates your real paying base, because it bakes in free-trial users who have not yet converted and grace-period users whose payment has actually failed.
Subscribers
The count of users with an active paid subscription, excluding free trials. This is closer to what most founders mean when they say “my subscriber count.” But it still includes users in grace periods after a failed renewal — Apple keeps them as Subscribers for up to 60 days while attempting retries.
The difference between Active Subscribers and Subscribers tells you the size of your free-trial pipeline. If your Active Subscribers number is 12% higher than your Subscribers number, you have a meaningful trial-conversion opportunity that month — and a meaningful churn risk if the trials fail to convert.
Paid Subscribers
The count of users who have made at least one paid renewal — they paid for at least one period beyond any introductory or trial offer. This is the metric closest to “people who actually transacted money with me for the product.” It is the right number to use for retention math, because retention questions are about people who paid, not people who started a trial.
Active Subscribers > Subscribers > Paid Subscribers in any given week. The gaps between them tell you about your trial-to-paid funnel, your grace-period exposure, and your renewal health.
Recoverable Cancellations
Users who cancelled or whose subscriptions lapsed but whose receipts Apple can still recover if they re-subscribe within a window. This metric is small and confusing — most founders ignore it. But it tells you how much “shadow MRR” is sitting in users who haven’t fully left.
In MENA specifically, Recoverable Cancellations spikes during Ramadan because users cancel transactionally during the month (deferring decisions) and many of them re-subscribe after Eid. The Recoverable Cancellations number in early Ramadan is the leading indicator of your post-Eid re-subscription cohort.
The metric most founders get wrong: Proceeds
App Store Connect reports two related but different things in the financial views:
- Proceeds — what Apple paid you after their cut.
- Customer Price — what the user paid before Apple’s cut.
Most founders read Proceeds in the dashboard and treat it as “revenue.” It is not revenue in the way an accounting team or an investor uses the word. It is net to your bank account, after Apple’s 15% or 30% take and after Apple’s currency conversion and any local taxes Apple collects on your behalf.
If you are comparing ROAS or LTV across networks, you need to be consistent: Proceeds vs ad spend gives you net-revenue ROAS, while Customer Price vs ad spend gives you a gross figure that is more comparable to how ad networks measure their attributable revenue. Most ad networks default to gross. We see teams routinely under-report their effective ROAS by 15-30% because they use Proceeds where their AppsFlyer dashboard is using Customer Price.
The MENA-specific signals in this dashboard
Apple’s dashboard is the same UI worldwide, but the patterns in the data are not. A few signals are MENA-specific:
Cross-country pricing arbitrage
If you serve KSA, UAE, and Egypt with the same tier price, the App Store Connect Customer Price by Country view will show you that your effective USD-equivalent price varies widely. Apple converts Customer Price to your home currency in the dashboard using their internal FX rate, which is updated quarterly — so during a quarter where the EGP weakens against USD (a routine occurrence), your “Egypt Customer Price” line silently falls while your ad spend in EGP rises. The dashboard does not flag this as a problem; you have to spot it yourself.
The fix is to publish per-country pricing tiers (Apple supports up to 800 price points per app per country) and update them when local currency moves more than ~5% against USD.
iOS share signal
App Store Connect’s Sources view shows you which acquisition channels are driving installs. In KSA and UAE, the share of installs coming from “App Store Search” routinely exceeds 50% — far higher than the global average. If your KSA App Store Search share is below 40%, your ASO is the problem, not your paid spend.
In Egypt and the Levant, the same metric is lower (often 25-35%) because organic discovery happens more through social and WhatsApp shares. The same install volume requires different strategies by country.
The “Notifications” sub-view that nobody reads
App Store Connect’s Notifications view records every server-to-server notification Apple sends you about subscription state changes — renewals, cancellations, billing retries, refunds, price-consent prompts. If your backend is missing notifications (the most common cause of subscription state drift), this is where you spot it.
In MENA, the most common gap we see is the DID_FAIL_TO_RENEW and GRACE_PERIOD_EXPIRED notifications being dropped during regional CDN issues — STC and Vodafone Egypt egress paths have variable success rates for notification delivery, and Apple does not retry forever. Apps that don’t have a daily reconciliation job comparing their internal subscription state to App Store Connect’s Subscribers count will silently drift.
Reporting bugs worth knowing about
Apple’s dashboard has known issues. The ones MENA founders are most likely to hit:
The 4-day delay on Subscriber metrics
Active Subscribers, Subscribers, and Paid Subscribers all run on a roughly 4-day delay. Apple aggregates the data overnight after the day closes, and the count for “today” is not stable until about 4 days later. If you are looking at this morning’s number and making a decision on it, you are looking at a guess. Wait for the figure to settle before changing strategy.
Promotional offers not counted as renewals
If you give a promotional offer (a one-time discount, a win-back offer, etc.), the resulting subscription period is not counted as a “Paid Subscriber renewal” in the dashboard — even though the user paid real money for it, just at a discounted rate. This causes Paid Subscribers to silently undercount your real paying base by 5-15% in any month where you ran a promo, distorting your retention calculations.
Currency conversion timing
The dashboard’s revenue charts in your home currency convert at end-of-period FX rates, not at the rate when the transaction cleared. In high-FX-volatility markets (Egypt and Turkey both qualify), this introduces non-trivial noise into your month-over-month revenue comparison.
The “Customer Reviews” lag
Apple’s Customer Reviews data in App Store Connect lags the public-facing store by up to 48 hours. If you see a negative review storm on the public store, you may not be able to triage it from Connect for 1–2 days. Watch the public store directly for breaking issues.
How to actually use this dashboard week to week
A pragmatic weekly workflow for a MENA subscription app:
- Monday morning: check Active vs Subscribers vs Paid Subscribers for the country breakdowns that matter to you. The gap between Subscribers and Paid Subscribers tells you about renewal health; the gap between Active and Subscribers tells you about your trial pipeline.
- Mid-week: scan the Notifications view for any spike in
DID_FAIL_TO_RENEW. A 20%+ increase week-over-week in a single country is your involuntary-churn signal — usually a payment-rail issue you can fix with a retry policy update. - End of week: reconcile against RevenueCat. Discrepancies of more than 2% between Apple’s Paid Subscribers and RevenueCat’s “active entitlement” count mean either a notification gap or a stale state, and you need to investigate before the gap compounds.
Madar AI runs this reconciliation automatically — it connects to App Store Connect, RevenueCat, and your MMP, then flags drift, undercounted promotional revenue, and currency-conversion noise without you having to remember which Apple metric to compare against which.
If you want to see this reconciliation on your real data, the live demo sets it up in about ten minutes.