App Store Connect Analytics: The Metrics That Actually Matter

Quick answer: App Store Connect Analytics tracks your acquisition funnel (impressions, product page views, downloads), where downloads come from, and what users do afterward (sessions, retention, proceeds). Start with four numbers: conversion rate by source type, product page views, day 1 and day 7 retention, and the peer group benchmarks. Together they tell you whether to fix your store listing or your app.

Open App Store Connect, choose your app and go to Analytics. Apple has expanded this area significantly, adding more metrics, cohort views and support for up to seven filters at once, so menus may not match older screenshots you find online.

Three things to know before you read any chart:

• Thresholds. App Store metrics appear once an app has at least five first-time downloads, and usage metrics need at least five active devices. Smaller sources are grouped or hidden until they pass Apple's minimums.
• Opt-in data. Sessions, active devices, crashes, deletions and retention only count people who agreed to share diagnostics and usage data with developers. Treat them as trends, not totals.
• Exports. For your own dashboards, the Analytics Reports API in the App Store Connect API delivers the same data in bulk.

These are the metrics that describe how well your store presence converts. Definitions follow Apple's metric reference:

The key detail is the denominator. Apple's conversion rate divides by impressions, not by product page views. Many downloads happen straight from a search result without the product page ever opening, so this rate blends two things: how well your search result card works (icon, name, subtitle, first screenshots) and how well the full product page works.

You can separate them yourself. Compare impressions to product page views to see how often your search card earns a tap, then compare product page views to downloads for a rough product page conversion. It's rough because some downloads skip the page entirely, but the trend over time is useful.

Reading the funnel

The first rows point at creative. Our conversion rate guide goes deeper, and your first screenshot is usually the highest-leverage fix.

Every download is attributed to the source that drove it. Apple's acquisition documentation defines these source types:

Two details catch people out. On iOS, a tap in Chrome or another non-Safari browser counts as an app referrer, not a web referrer. And individual referring apps and websites only appear once they pass a minimum data threshold.

Always read conversion rate per source. Search visitors arrive with intent, browse visitors are casually scrolling, and web referrers often come from your own site already half convinced. A blended number hides all of that. For your own marketing links, App Store Connect's campaign links add a campaign token to your App Store URL, so newsletters, social posts and ads show up as separate campaigns you can filter by.

Apple reports the App Store features you use in the same analytics area:

• Custom product pages. The Product Page filter splits impressions, downloads and conversion by page, so you can compare each custom product page with your default page.
• Product Page Optimization. Test results show each treatment's conversion against the original along with Apple's confidence level. Our PPO guide covers how to set up and read a test.
• In-App Events. The In-App Event filter and the Page Type dimension show how many people discovered you through an event card.

Prefer a test over a before-and-after comparison whenever you can. Seasonality, featuring and ad spend all move conversion, and a PPO test runs both versions at the same time.

Downloads are only useful if people stay. The usage and monetization sections answer that:

• Sessions and active devices show engagement among opted-in users. A session is counted when the app is used for at least two seconds.
• Deletions count removals from the Home Screen or through storage management. A spike after an update is worth investigating.
• Retention is the share of devices that came back on a given day after download. Apple's example: if 100 devices first downloaded on May 1 and 20 had a session on May 8, day 7 retention is 20%. Filter it by source type or campaign to see which channels bring users who stay.
• Proceeds and paying users cover paid apps, In-App Purchases and subscriptions. Proceeds are after Apple's commission and applicable taxes.
• Cohorts group users by download date, source or offer start date, so you can follow one group over time.

There's no universal "good" conversion rate, and any single number you read online won't fit your category. Benchmarks are the honest answer. App Store Connect compares your app against similar apps for:

• Conversion Rate
• Day 1, Day 7 and Day 28 Retention
• Crash Rate
• Proceeds per Paying User (not shown for free apps)
• Day 35 Download to Paid Conversion
• Day 35 Proceeds per Download

Peer groups are built from App Store category, business model and download volume, and each widget shows where you sit against the 25th, 50th and 75th percentiles. Apple applies differential privacy and calls the result directional insight, not an exact ranking. If you're below the median on conversion but above it on retention, your product is fine and your listing is the bottleneck.

Play Console covers the same questions with different names. Store listing performance lives under Grow users, then Store performance, then Conversion analysis.

Google notes that its store listing reports now focus on user intent (clicks) rather than completed acquisitions, with CTR replacing the legacy conversion rate. Acquisitions are still available on the Grow users overview, in Statistics and in downloadable reports. The search term dimension is a real advantage: it shows which queries brought visitors to your listing, something App Store Connect doesn't report. See our Google Play ASO guide for how to use it.