The Scope of the Analytics Overhaul
On March 24, 2026, Apple rolled out what it describes as "the biggest update since launch" for the Analytics platform in App Store Connect. The expansion fundamentally changes what developers can measure after a user downloads their app.
The update adds more than 100 new metrics, new cohort analysis tools, peer group benchmarks for monetization performance, and two new subscription reports accessible via API. For the first time, developers can track In-App Purchase performance, offer effectiveness, subscription retention curves, and churn analysis directly within wiki:app-store-connect — data that previously required stitching together multiple tools or exporting to third-party analytics platforms.
Where Analytics previously focused on acquisition metrics (impressions, downloads, conversion rates), it now provides a full view of what happens after install: how different user groups perform over time, how monetization develops across cohorts, and how an app's business metrics compare to category benchmarks.
What the New Metrics Cover
The expansion spans three major areas:
Monetization and subscription data. New reports now track In-App Purchase performance at the individual offer level, showing which subscription tiers convert, which promotional offers drive upgrades, and where churn occurs in the subscription lifecycle. Retention curves visualize how long users maintain active subscriptions, segmented by plan type, pricing, and offer source.
Cohort analysis capabilities. Developers can now segment users by download date, traffic source, geographic region, or offer start date, then track how those groups perform over time. This enables direct comparison between user cohorts — for example, measuring whether users acquired during a holiday campaign monetize differently than organic summer downloads, or whether a Q1 regional launch in Japan performs better than a Q4 launch in the US.
Peer group benchmarks. Two new monetization-specific benchmarks — download-to-paid conversion and proceeds per download — let developers compare their app's performance against anonymized data from similar apps in the same category. The benchmarks use differential privacy to protect individual app performance while providing meaningful competitive context.
Additionally, developers can now apply up to seven filters simultaneously to any metric, allowing drill-downs into highly specific segments without running separate queries. This supports more granular analysis of edge cases and outliers that drive disproportionate value.
Subscription Data Now Available via API
Two new subscription reports can be exported programmatically through the Analytics Reports API. This marks a significant shift for teams that rely on internal business intelligence systems or need to combine App Store data with other revenue sources.
Previously, getting complete subscription performance data required manual exports or integration with third-party platforms. The new API access allows developers to automate data pipelines, schedule regular exports, and integrate subscription metrics into dashboards alongside web revenue, advertising performance, and operational costs.
For apps with multiple revenue streams — subscriptions, one-time purchases, advertising — this consolidation removes a major friction point in financial reporting.
Privacy Thresholds Shape What You Can See
The expanded metrics come with privacy constraints that affect what appears in Analytics and how the data should be interpreted.
Engagement metrics reflect opted-in users only. Active device counts and session data include only users who agreed to share diagnostics and usage information with the developer. This means engagement figures represent a subset of the installed base, not the full user population.
Acquisition sources require minimum data volumes. Certain traffic sources — app referrers, web referrers, campaign links — will not appear in Analytics until they cross a minimum activity threshold. If a specific source does not show up in reporting, it may be below the threshold rather than absent entirely. These privacy protections apply across Analytics, including the new subscription and cohort views.
Peer group benchmarks use differential privacy. Benchmark values are calculated using differential privacy techniques designed to prevent reverse-engineering of individual app performance within a peer group. This adds noise to the data in a controlled way that preserves useful comparative insights while protecting confidentiality. Benchmarks also include only data from users who agreed to share app analytics.
Before making decisions based on a new metric — especially cohort comparisons or benchmarks — confirm what the metric includes, what it excludes, and whether privacy thresholds could be limiting visibility.
How the Expansion Changes Post-Acquisition Measurement
The practical impact of this update centers on what teams can now measure without third-party tools.
Acquisition metrics clarification. Total Downloads combines First-Time Downloads and Redownloads. wiki:conversion-rate is calculated as total downloads divided by unique impressions. Both are meaningful, but they measure different behaviors. Being explicit about which metric drives a given decision matters more now that both appear alongside monetization data.
Cohort-based decision-making. The ability to segment users by shared attributes and track performance over time enables new workflows: identifying which traffic sources produce the highest lifetime value, comparing retention across regional launches, or isolating the impact of specific promotional offers on long-term subscription behavior. This shifts optimization focus from install volume to user quality and long-term value.
Internal benchmarking. For the first time, developers can assess whether their monetization performance is competitive without relying on external data providers. If download-to-paid conversion sits below the peer group median, that signals a product, pricing, or messaging issue worth investigating. If proceeds per download exceed the benchmark, that validates current strategy and suggests room to scale.
The combination of richer post-install metrics, cohort tools, and competitive context reduces dependence on external analytics platforms for core business questions. Not every team will eliminate third-party tools entirely — mobile measurement partners still provide attribution, fraud detection, and cross-platform unification that Analytics does not cover — but the gap has narrowed significantly.
Apple Ads Insights Adds Flexible Reporting Across Campaign Dimensions
Parallel to the Analytics expansion, Apple updated the reporting interface inside Apple Ads with a new Insights workspace. This is a separate change from the App Store Connect Analytics overhaul, but the two updates together give marketers a more complete picture of acquisition and post-acquisition performance.
Insights provides flexible data exploration across campaign groups, campaigns, ad placements, wiki:keyword-ranking performance, and geographic regions. It replaces the previous Custom Report Builder with a more visual interface that supports predefined Performance and Advanced reports, customizable metrics and dimensions, and downloadable exports.
Key differences from the old reporting:
- Predefined report templates cover common views (Campaign Groups, Keywords, Search Terms, Ad Placements, Country/Region) pre-populated with standard metrics, reducing the time to answer routine performance questions.
- Impression Share and Rank reports provide competitive context on search term performance, showing share of impressions relative to other advertisers and how popular a given search term is in specific countries.
- Reports shared to campaign groups automatically grant access to everyone with permissions on that campaign group, simplifying team collaboration without manual sharing steps.
- Up to 24-month date ranges support long-term trend analysis without stitching together multiple exports.
Implications for Measurement Stack Architecture
The combined effect of these updates — expanded Analytics in App Store Connect and flexible reporting in Apple Ads Insights — changes the calculation for teams evaluating their measurement infrastructure.
For apps with simple monetization models (single purchase, basic subscription), the new Analytics capabilities may eliminate the need for third-party dashboards entirely. If the primary questions are "how many users downloaded," "how many converted to paid," and "how does that compare to my category," App Store Connect now provides direct answers.
For apps with complex multi-platform businesses, the update reduces but does not eliminate the role of external tools. Attribution providers still offer cross-platform view-through tracking, fraud detection, and Android-iOS unified reporting that Apple's tools do not cover. But the volume of questions requiring external tools has shrunk.
For teams optimizing both paid and organic channels, the workflow now centers on two Apple-native dashboards rather than a fragmented stack. Insights handles paid campaign performance. Analytics handles organic acquisition, engagement, and monetization. Integration points exist (campaign-tagged cohorts appear in Analytics), but the systems remain conceptually separate.
The shift we are seeing is not a wholesale replacement of third-party analytics, but a significant expansion of what can be measured natively. Teams that previously maintained five-tool measurement stacks may find that three suffice. Teams that relied on custom data pipelines to unify Apple-side metrics may find that the native tools now answer their core questions directly.
What to Do Next
If you have not reviewed the new Analytics capabilities yet, the immediate next steps are straightforward:
- Audit what you currently export to third-party tools. Identify which reports and metrics now exist natively in App Store Connect. For subscription apps especially, the new retention and churn reports may duplicate what you are paying for elsewhere.
- Set up cohort views for recent launches or campaigns. If you expanded to a new region, ran a major promotional campaign, or launched a new subscription tier in the past quarter, create a cohort and track its performance over the next 90 days. Use that data to validate whether the initiative met expectations before scaling further.
- Compare your monetization metrics to peer benchmarks. If download-to-paid conversion or proceeds per download fall below category medians, that is a signal to investigate conversion rate optimization cro opportunities — whether pricing, onboarding, or product-market fit.
- Review privacy thresholds on acquisition sources. If a traffic source you expect to see is missing from Analytics, check whether it has crossed the minimum data threshold. If not, consider whether the source is worth continued investment.
- Explore the API for subscription data export. If you maintain internal BI dashboards, integrating the new subscription reports via API can eliminate manual export workflows and keep financial reporting current.