The Biggest Analytics Expansion Since Launch
On March 24, 2026, Apple released what it describes as the largest update to wiki:app-store-connect Analytics since the platform's inception. The expansion brings more than 100 new metrics into the Analytics dashboard, fundamentally changing what developers can measure beyond top-line installs.
The new capabilities center on three areas:
- Monetization and subscription tracking โ In-App Purchase performance, offer effectiveness, subscription retention curves, and churn analysis now live directly inside Analytics. Previously, assembling a complete monetization view required stitching together data from multiple tools. This consolidation eliminates that friction.
- Cohort analysis โ Developers can now segment users by download date, traffic source, region, or offer start date, then track how those cohorts perform over time. For example, comparing how long it takes users from a new market to convert versus users from an established region becomes a native workflow.
- 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 industry data from similar apps in their category.
Privacy Boundaries and Data Thresholds
Before drawing conclusions from the new metrics, understanding what the data includes โ and excludes โ matters.
Engagement metrics (active devices, session data) only reflect users who have opted in to share diagnostics and usage information. Your engagement figures represent a subset of your actual user base, not the full install count.
Certain acquisition sources require minimum volume thresholds before appearing in Analytics. If a particular referrer or campaign link does not show up, it may be below the privacy threshold rather than absent. These protections apply throughout Analytics, including the new subscription and cohort views.
Peer group benchmarks use differential privacy to ensure individual app performance within a comparison group remains protected. Benchmark values also draw only from users who have agreed to share app analytics.
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 things โ being deliberate about which metric drives a given decision prevents misinterpretation.
Apple Ads Insights Replaces Custom Report Builder
Alongside the Analytics expansion, Apple introduced Insights โ a new reporting workspace inside Apple Ads designed to replace the legacy Custom Report Builder. Insights provides flexible exploration across campaign groups, campaigns, ad placements, keywords, and other account dimensions.
The workspace includes three main components:
- Insights landing page โ A high-level performance snapshot for selected campaign groups, defaulting to the last seven days. You can adjust the date range and add or remove campaign groups to expand the view.
- Report builder โ Predefined reports pre-populated with common metrics and dimensions, split into Performance reports (covering account structure like Campaigns, Keywords, Search Terms, Ad Placements) and Advanced reports (aggregate views including Impression Share data).
- Visualization options โ Editable metrics, dimensions, and filters to drill into performance at the required level of detail.
Report Management and Sharing Mechanics
Reports in Insights fall into three categories on the landing page: reports you created, reports shared with you, and reports migrated from Custom Report Builder.
Ownership determines editing permissions. If you created a report, you can edit and save changes. If someone else owns it, any changes you make will not persist unless you save a new version using "Save as." Reports are shared to campaign groups, not to individual people โ anyone with access to the campaign group automatically gains access to the report. Deleting a report removes access for everyone it was shared with through that group.
Reports can be exported as XLSX files from the Actions column, useful for offline analysis or distribution outside Apple Ads.
- Impression Share, Search Popularity, and Rank measures require pairing with specific dimensions (Day, App, App ID, Country or Region, or Search Term) to display meaningfully
- Predefined Impression Share reports support up to 12 weeks of data
- Some predefined report settings (such as timezone on certain Impression Share reports) are fixed by report type
What This Enables for Practitioners
The combined updates to App Store Connect Analytics and Apple Ads Insights clarify the boundary between paid acquisition measurement and store-side outcome measurement.
Apple Ads Insights focuses on campaign performance: which placements, keywords, and segments drive installs at what efficiency. It helps identify where performance is shifting by campaign group, placement, keyword, or region.
App Store Connect Analytics now covers what happens on the App Store itself and after acquisition: how users find your app, whether they download it, how different cohorts perform over time, and how monetization develops. The expanded metrics let teams understand not just whether users arrived, but which groups convert, retain, and monetize.
For teams operating across both paid and organic channels, these platforms provide complementary lenses. Insights helps optimize acquisition spend. Analytics helps validate whether acquisition choices translate into downstream business outcomes โ within the privacy constraints Apple enforces.
The expansion also reduces the need to maintain custom data pipelines for basic questions. Subscription performance, cohort retention, and category benchmarking now live natively in App Store Connect rather than requiring export-and-stitch workflows through third-party tools or internal BI systems.
Xcode 26 SDK Requirement Takes Effect April 28
Starting April 28, 2026, every app submitted to App Store Connect must be built with Xcode 26 or later, using the iOS 26, iPadOS 26, tvOS 26, visionOS 26, or watchOS 26 SDK. This is a hard gate โ apps that do not meet the requirement will be rejected at submission.
One side effect: by default, apps built with the iOS 26 SDK adopt the new Liquid Glass visual style on native UI components unless developers explicitly opt out. Teams that have not yet updated their wiki:screenshot sets should do so before the deadline to ensure visual consistency between the live app and store listing assets.