iOS subscription analytics: what third-party tools show that App Store Connect can't

App Store Connect's built-in analytics leave critical subscription data gaps. This guide explains what RevenueCat, Amplitude, and Mixpanel add — and how to choose the right stack for your stage.

App Store Connect has expanded its analytics surface considerably since 2022, but a persistent frustration among subscription app developers remains: the data visible in Apple's dashboard and the data actually needed to improve a subscription business don't fully overlap. This guide maps the gap and explains what third-party analytics tools provide — and when the investment is justified.

What App Store Connect analytics covers — and where it stops

Apple's built-in analytics give you several genuinely useful views. The Sales and Trends reports surface downloads, in-app purchase revenue, and proceeds broken down by territory and product. The App Analytics tab shows impressions, product page views, and install conversion rates. Subscription-specific reports let you track active subscribers, new paid starts, renewals, voluntary churn, and billing-retry outcomes across cohorts.

For a developer who has just launched a subscription app, this is a reasonable starting point. The data is free, no additional SDK integration is required beyond StoreKit itself, and the financial reporting is authoritative — Apple's numbers are the source of truth for proceeds and tax-eligible events.

The gaps become apparent when you move from monitoring to improving:

• No event-level data. App Store Connect reports aggregates. You cannot inspect the journey of an individual user from install to trial to paid to cancelled.
• No custom segmentation. You cannot filter subscription metrics by attributes your app collects — whether a user completed onboarding, which feature they used first, or what acquisition campaign brought them in.
• No in-app behavioral data. Apple does not know what users do inside your app. Paywall exposure, feature engagement, session depth, and in-app actions are invisible to App Store Connect.
• Significant reporting delays. Sales and Trends data for in-app purchases can lag 24–48 hours. Subscription cohort reports update even less frequently. You cannot monitor a live paywall test in real time.
• Limited attribution. Apple Search Ads attribution is surfaced, but organic versus other paid channels, referral sources, and cross-channel journeys are not visible.

None of this is a criticism of Apple's tooling on its own terms. App Store Connect is designed to report on App Store activity, not to serve as a full-stack product analytics platform. The mismatch only emerges when developers expect it to answer questions it was never built to answer.

RevenueCat: subscription intelligence as the primary data layer

RevenueCat is the most widely adopted third-party subscription analytics platform among iOS developers, and its dominance is partly explained by its positioning. Rather than competing with App Store Connect, it extends it: the RevenueCat SDK wraps StoreKit (and Google Play Billing on Android), normalizes subscription events across platforms, and exposes a clean API and dashboard on top.

The core value proposition is that RevenueCat maintains the complete lifecycle of every subscriber an app has ever had: when they started a trial, when they converted, when they churned, what offer they redeemed, and whether they reactivated. That event log, queryable and exportable, enables the subscription metrics that App Store Connect approximates but does not fully deliver.

RevenueCat's Charts feature provides MRR, active subscribers, trial conversion rates, churn rates, and LTV cohorts — all filterable by country, product, store, and date range. RevenueCat's own published research has documented cases where LTV differences between acquisition cohorts vary by 2× or more across channels, a gap that would be impossible to identify from App Store Connect's aggregate views alone.

RevenueCat's free tier covers apps generating up to $2,500 in monthly tracked revenue, which is meaningful for early-stage developers. Pricing scales after that threshold. For cross-platform apps, the unified dashboard across iOS, Android, and web is a material operational advantage — App Store Connect and Google Play Console do not speak to each other.

Compared to competing platforms like Adapty and Purchasely (covered in the SDK comparison guide), RevenueCat's analytics depth and third-party integration ecosystem — Amplitude, Mixpanel, Braze, Airship, Slack, and others — are primary differentiators. The integration layer matters because RevenueCat alone is not a behavioral analytics tool. It knows that a user subscribed; it does not know why they did.

Behavioral analytics: Amplitude and Mixpanel paired with subscription events

Behavioral analytics platforms track event streams — arbitrary actions a user takes inside an app, sent to the platform in real time via an SDK. Amplitude and Mixpanel are the two most common choices in the iOS subscription developer community, though PostHog (open-source, self-hostable) has gained ground among cost-conscious developers in recent years.

On their own, behavioral platforms know nothing about subscriptions. They observe that a user tapped a button, reached a screen, or viewed the paywall — but not whether that user is a paying subscriber, a trial user, or a free-tier user, unless the app explicitly sends that context to them.

The integration with RevenueCat changes this calculus. RevenueCat can forward subscription lifecycle events — INITIAL_PURCHASE, RENEWAL, CANCELLATION, TRIAL_STARTED, TRIAL_CONVERTED — to Amplitude or Mixpanel as user properties and events. Once that data lands in Amplitude or Mixpanel, queries like these become possible:

• Build a funnel from "paywall viewed" → "trial started" → "trial converted" → "renewed at 30 days" and find where users drop
• Compare trial conversion rates for users who completed the onboarding flow versus those who skipped it
• Identify which in-app features are used most heavily by long-term subscribers (signals for paywall copy and feature positioning)
• Segment churn by acquisition channel and correlate with 90-day LTV

This level of analysis underpins what growth teams call product-led retention — using behavioral signals to intervene before a user cancels, not after. Research from Phiture and others in the mobile growth community suggests that in-app engagement depth in the first seven days is one of the strongest predictors of 90-day retention, a finding consistent with RevenueCat's own cohort data. The behavioral analytics stack makes that signal measurable and actionable. For more on shaping the first-week experience, see the subscription onboarding guide.

Comparing the data layers

Choosing your analytics stack by stage

The right stack depends less on what you want to know and more on what decisions you can actually act on at your current scale. Adding tooling before you have the traffic or team to use it creates instrumentation overhead without analytical payoff.

Pre-launch and early traction (under $2,500 MTR): App Store Connect plus RevenueCat's free tier is the right default. RevenueCat delivers the subscription event log and financial dashboard that App Store Connect lacks, and the free tier limit is generous enough that most early-stage apps will not hit it for months. Behavioral analytics at this stage is usually premature — user volumes are too low for statistically meaningful funnel or cohort analysis.

Growing ($2,500–$50,000 MTR): RevenueCat remains the subscription data layer, now on a paid plan. At this stage, the most common analytical gap is understanding trial conversion variance — why does the trial-to-paid rate shift week over week? Before adding Amplitude or Mixpanel, determine whether RevenueCat's own segmentation by country, product, and offer can explain the variance. If it cannot, behavioral data is likely the next investment. PostHog's self-hosted option is worth evaluating here as a cost-effective entry point.

Scaling ($50,000+ MTR): A two-layer stack — RevenueCat for subscription analytics plus Amplitude or Mixpanel for behavioral analytics — is standard at this stage. The incremental revenue recoverable from better churn prediction and paywall optimization typically exceeds the platform costs. For larger teams, a data warehouse export (RevenueCat supports BigQuery and Redshift destinations) becomes relevant for ad-hoc SQL analysis and joining with other business data. For the cohort math that supports those analyses, see the LTV cohort model guide.

Pricing and localization decisions also benefit from the combined stack. App Store Connect can report that subscribers in Japan have a higher churn rate than those in the US, but it cannot indicate whether Japanese users see a localized paywall or whether translation quality correlates with conversion. Behavioral analytics closes that loop. For territory-level pricing context, see the territory pricing reference and the broader data in subscription ARPU by geography.

The practical conclusion is that App Store Connect, RevenueCat, and a behavioral analytics platform are not competing tools — they occupy distinct analytical roles that compound when combined. App Store Connect provides authoritative financial data and App Store-side funnel metrics. RevenueCat provides the subscription event layer and the cross-platform normalized view of subscriber health. Behavioral analytics provides the in-app signal layer that explains the behavioral antecedents of financial outcomes. Each layer is necessary; none is individually sufficient for a mature subscription business.

Sources and further reading

• RevenueCat: State of Subscription Apps report
• Apple Developer: App Store Connect Analytics overview
• RevenueCat: Amplitude integration documentation
• Phiture: Mobile Growth Stack resources
• Mixpanel: Getting Started guide
• Amplitude: Product analytics for subscription apps