App Store Connect Analytics: What the Numbers Mean

Apple Gives You Data. Understanding It Is on You.

App Store Connect analytics is the first place most developers look after launching an app. It's free, it's official, and it shows you numbers that feel important — impressions, downloads, conversion rates.

But the dashboard doesn't explain what those numbers actually mean in practice or what's missing entirely. This guide walks through every major metric, explains what it tells you and what it doesn't, shows how to pull the raw reports through the API, and points out where the gaps are big enough that you need other tools to fill them.

Impressions — The First Metric in App Store Connect Analytics

Apple counts an impression each time your app is viewed for more than one second on the Today, Games, Apps, or Search tab of the App Store [source: developer.apple.com/help/app-store-connect/reference/reporting/performance-metrics]. That covers search results, editorial placements, category lists, and "You Might Also Like" rows. Product page views are included in the total, and Apple also reports a unique-devices version that counts each device once.

On the surface, impressions look like a reach metric — how many people saw your app. In practice, the number is less useful than it appears.

The problem is that impressions are aggregated across contexts. If your app appears in a search result for "weather" and separately in a "You Might Also Like" row under a competitor, both count. You can filter impressions by source type, which separates search from browse, but within search you can't tell which query produced which impressions.

A sudden increase could be great news (your app started ranking for a high-volume keyword) or meaningless (Apple started showing your app in more "related apps" carousels where nobody taps). Without keyword-level attribution, you're guessing.

What impressions are good for: Tracking macro trends. If impressions are steadily growing month over month, something is working — your ASO changes, a seasonal trend, or improved rankings. If they're declining, something changed and you need to investigate.

What they're not good for: Diagnosing specific ASO changes. You updated your subtitle and impressions went up? Maybe. Or maybe an unrelated editorial feature drove the increase. You can't isolate the cause from this metric alone.

Product Page Views

A product page view is counted each time your full App Store page is viewed, including when another app opens it through StoreKit. This is the step between seeing your app in a list and deciding to download it.

The ratio of product page views to impressions tells you how compelling your listing looks in search results and browse contexts. A low ratio means people see your app but aren't interested enough to tap — your icon, name, subtitle, or first screenshot isn't doing its job.

Apple breaks product page views into "unique device" and "total" counts. The unique count is more useful for understanding actual user interest, since the total count can be inflated by the same person viewing your page multiple times.

Practical use: If you change your app icon or first screenshot and product page views increase relative to impressions, you have evidence the change worked. This is one of the few A/B tests you can run indirectly through App Store Connect data, though Apple also offers official product page optimization tests.

App Units (Downloads)

"App Units" is the Sales and Trends name for first-time downloads. Apple counts an app unit when a customer taps Get or Buy for the first time, for free and paid apps alike [source: developer.apple.com/help/app-store-connect/view-sales-and-trends/view-units-proceeds-sales-and-pre-orders]. These don't count as app units:

• updates to an installed app
• redownloads to the same device
• downloads onto another device signed in to the same Apple Account
• Family Sharing downloads of a paid app (Family Sharing downloads of a free app do count)

App Analytics reports the same idea as First-Time Downloads, with Redownloads alongside it and Total Downloads as the sum of the two. If you're looking for app units in App Analytics, First-Time Downloads is the metric to compare against. Redownloads are worth a look on their own: a redownload is by definition someone who had your app before, so a rising count means lapsed users are coming back, which no first-time figure will show you.

For paid apps, app units track directly with revenue. For free apps (which is most indie apps), they're the top of your monetization funnel.

App units are the metric most developers fixate on, but in isolation they don't tell you much. A hundred downloads from a well-targeted keyword are more valuable than a thousand from users who churn in 24 hours. App Store Connect gives you the count but no context about user quality.

One thing to watch: Divide downloads by product page views to get your product page conversion rate. Apple's own conversion rate (next section) uses impressions as the denominator, so it can't tell you whether people who reached your page liked what they saw.

Conversion Rate

App Store Connect defines conversion rate as total downloads and pre-orders divided by unique-device impressions [source: developer.apple.com/help/app-store-connect/reference/reporting/performance-metrics]. That makes it an impression-to-download rate, not the share of product page visitors who downloaded. Plenty of people install straight from a search result without opening your page, and those installs count here too.

It's still arguably the most actionable metric in the dashboard, because it moves with everything a searcher sees: icon, name, subtitle, first screenshots, rating. Category, business model, and traffic mix swing it too much for one universal "good" number, so judge yours against the peer group benchmarks covered below. For how to move it, see our app store conversion rate guide.

The main levers that affect conversion rate:

• Screenshots and app previews. This is the single biggest factor. Users make snap decisions based on your first two screenshots. If they don't immediately communicate what your app does and why it's good, people bounce.
• Ratings and reviews. Apps below 4.0 stars see measurably lower conversion rates. See our guide on how to get more reviews. A handful of negative reviews at the top of your review section can tank conversions even if your overall rating is fine.
• App size. Large apps hit a confirmation prompt before downloading over cellular (by default, above 200 MB). It's a small step, but it's friction at exactly the wrong moment.
• Price. Obvious, but worth stating. Free with in-app purchases converts significantly better than upfront paid, even at $0.99.

The limitation: You can filter conversion rate by source type, so search and browse can be compared. But inside App Store Search every query is blended. People who typed your exact app name convert far better than people who typed a generic term, and Apple reports them as one number. A rise in branded searches can make search conversion look healthier while your listing does no better for the generic keywords you're actually trying to win.

Sources: Where App Store Connect Analytics Says Your Traffic Comes From

App Store Connect assigns each impression and first-time download to a source type: the place the customer tapped through from. Understanding what each one means — and doesn't mean — is critical.

App Store Search

This is traffic from users who typed a query into the App Store search bar. For most apps, this is the largest source of organic traffic — Apple says almost 65% of downloads happen directly after a search [source: ads.apple.com/app-store].

Here's the frustrating part: App Store Connect tells you how many impressions and downloads came from search, but not which keywords drove that traffic. You know 500 people found your app through search last week, but not whether they searched "weather app," "rain forecast," or your app's name.

This is the single biggest gap in App Store Connect's analytics. Keyword-level data is essential for ASO — without it, you can't know which keywords drive downloads, which you're wasting effort on, or which opportunities you're missing. This is the primary reason ASO tools exist.

App Store Browse

Browse traffic comes from users who discovered your app through non-search surfaces — the Today tab, category charts, "You Might Also Like" recommendations, and curated lists.

Browse traffic tends to be spikier and less controllable than search traffic. If Apple features your app in the Today tab, you'll see a massive spike that has nothing to do with your ASO efforts. Conversely, browse traffic can drop for no apparent reason as Apple's algorithms shift. It's nice when it happens, but you can't build a growth plan on it.

Web Referral

Web referral traffic comes from links on websites, social media, and other web sources that lead to your App Store listing. This captures everything from Product Hunt listings to your own website's download buttons. It's one of the few sources you have direct control over.

App Referral

App referral traffic comes from links within other apps. This includes cross-promotion from your own apps, referral programs, or third-party apps that link to yours. If you run a portfolio of apps — common among indie developers — cross-promotion between your own apps shows up here.

Retention

App Store Connect provides day-1, day-7, and day-28 retention metrics, showing what percentage of users who downloaded your app returned to it on those days.

Retention data is critical because it tells you whether you're acquiring the right users and whether your app delivers on the promise your listing makes. High downloads with poor retention usually means one of two things: your marketing is reaching the wrong audience, or your app's onboarding experience isn't good enough.

Keep in mind who's in the sample. Retention, sessions, active devices, and crashes come only from users who agreed to share analytics with developers [source: developer.apple.com/help/app-store-connect/reference/reporting/performance-metrics], so they're a sample rather than a full count. Rather than chase a generic target, compare your day-1, day-7, and day-28 numbers with your peer group (next section). For what actually moves early retention, see onboarding that protects day-1 retention.

The limitation: Retention data takes days to populate, and you can't tie it back to the search term that brought a user in. Users who found you through one keyword may retain very differently from those who came through another, but you see them blended together.

Peer group benchmarks

Peer group benchmarks are App Store Connect's answer to "is my number good?" Apple compares your app with apps that share its primary category, business model (free, freemium, or paid), and download-volume tier, and shows where you sit against the group's 25th, 50th, and 75th percentiles, refreshed weekly [source: developer.apple.com/help/app-store-connect-analytics/benchmarks/peer-group-benchmarks]. The benchmarked metrics are:

• 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

Apple uses differential privacy and adds noise so no single app's values can be read out of a group, and only publishes a peer group once it holds enough apps. If yours is too small, pick a broader one, such as a secondary category or all categories with your business model.

Because this is Apple's own data on comparable apps, it beats any industry average quoted elsewhere. The catch: it tells you where you stand, not which keywords or listing changes put you there.

Pulling App Store Connect analytics through the API

To get the numbers into a spreadsheet, a warehouse, or next to your keyword rankings, you pull them through the App Store Connect API. Every request carries a short-lived JWT signed with an API key: a .p8 private key plus its Key ID and your team's Issuer ID. Apple rejects tokens set to live longer than 20 minutes [source: developer.apple.com/documentation/appstoreconnectapi/generating-tokens-for-api-requests], so generate a fresh one per job instead of caching it.

Two different report families sit behind the dashboard, and they behave differently:

• Sales and Trends reports (salesReports): gzipped TSV files (daily, weekly, monthly, or yearly) with app units, redownloads, updates, in-app purchases, and proceeds. They need your vendor number, which you'll find in Payments and Financial Reports; the API won't look it up for you.
• Analytics Reports API (analyticsReportRequests): the impressions, product page views, source types, sessions, and installs and deletions behind App Analytics. It's asynchronous: you file a report request once, as ONE_TIME_SNAPSHOT for the history Apple holds or ONGOING for daily, weekly, and monthly files from then on, and Apple generates the files on its own schedule.

Which API key role you need

The role you choose when you create a key decides which reports it can reach, and you can't edit it later; to change a key's access, you revoke it and generate a new one. Team keys apply to every app in the account, so you can't limit one to a single app. Only the Account Holder or an Admin can generate them, and Apple lets you download the .p8 exactly once [source: developer.apple.com/help/app-store-connect/get-started/app-store-connect-api]. Keep it in your CI's secret store, not the repo.

Sources: Apple's Analytics Reports API page [source: developer.apple.com/help/app-store-connect-analytics/overview/analytics-reports-api] and role permissions reference [source: developer.apple.com/help/app-store-connect/reference/account-management/role-permissions].

The Admin requirement is the one that trips people up. A Sales and Reports key pulls downloads and proceeds without complaint, so it looks like the sensible least-privilege choice for a reporting script, right up until the first analytics request comes back 403. We ran into exactly this building Sonar's App Store Connect sync: sales reports work with a Sales and Reports key, while App Analytics needs an Admin key to file the report requests. You can either run the whole job on an Admin key, or use an Admin key once to file the requests and a narrower Sales and Reports or Finance key for the downloads after that.

Reading listing metadata (title, subtitle, the keywords field) is a separate permission again. It needs an Admin or App Manager key, and a Sales and Reports key gets a 403.

What to expect when the reports arrive

• Timing. After an ONGOING request, the first report arrives roughly 24 to 48 hours later, and Apple only treats a day's data as complete two days after that date.
• Thresholds and noise. Rows with data from fewer than five users or devices are left out, some usage reports aren't generated at all below minimum thresholds, and Apple adds a small amount of statistical noise [source: developer.apple.com/help/app-store-connect-analytics/overview/analytics-reports-api]. Small apps should expect gaps rather than zeroes.
• Impressions arrive split. The engagement report delivers product page views as a separate event from impressions. App Store Connect's Impressions total includes page views, so add them back if you want your numbers to match the dashboard.
• In-app purchase rows point elsewhere. In Sales and Trends, in-app purchase and subscription rows carry the product's own Apple Identifier, with the parent app's SKU in the Parent Identifier column. Roll them up by parent, or your per-app revenue will come up short.
• Quiet days return 404. A daily sales report for a day with no sales comes back as "not found" rather than an empty file. A report that simply hasn't posted yet looks the same for the first day or two, so treat a recent 404 as "try again later" and an older one as a zero-sales day.

If you'd rather skip the plumbing, Sonar's App Store Connect connection takes the same four pieces (Issuer ID, Key ID, .p8, and vendor number), encrypts the key at rest, and shows your daily downloads, proceeds, and the impressions-to-downloads funnel next to your keyword rankings. The funnel needs an Admin key; a Sales and Reports key covers downloads and proceeds.

What App Store Connect Analytics Doesn't Show You

The gaps are well-documented but worth restating, because they define where you need supplementary tools:

No keyword-level data or rankings. You cannot see which keywords drive your impressions, product page views, or downloads, or where you rank for any of them. You might be position 3 for your most important keyword or position 150, and you'd never know from Apple's dashboard. This is the gap that matters most for ASO.

No competitor data. You have zero visibility into competitor download numbers, keyword rankings, or conversion rates. Peer group benchmarks compare you with a category in aggregate, not with any named app.

Awkward history. The dashboard is built around recent periods. For long-term trends and year-over-year seasonality, keep your own copy, exported from the dashboard or pulled through the API snapshot described above.

No real-time data. Most metrics update daily with a 24-48 hour delay. After a metadata update you're waiting at least two days for directional data and a week or more for meaningful trends.

Where ASO Tools Fit In

App Store Connect tells you what happened at a high level. ASO tools tell you why it happened and what to do about it.

The core value of an ASO tool is keyword-level visibility: which keywords you rank for, where, how that rank changes over time, and how much search demand each keyword carries. A rank tracker covers the first three; competitor keyword analysis shows what your competitors rank for and where the gaps are. Combined with App Store Connect's conversion data, you get the full picture: ASO tools help you win the right traffic, App Store Connect measures whether it converts.

A tool like Sonar is built for indie developers who need that keyword-level data without the enterprise price tag.

Other places to find keyword-level data

Apple Ads search terms

Advanced campaigns in Apple Ads include a Search Terms report: the actual queries that triggered your ads, with impressions, taps, and installs for each. It's paid traffic, so it isn't a clean read on organic behavior, and Apple groups the rarest queries together instead of listing them. Even so, a small always-on campaign is the most direct look at real iOS search terms you can get from Apple. Our Apple Search Ads guide covers the setup.

Custom product pages with assigned keywords

Apple lets you publish up to 70 custom product pages and assign keywords to them, so a page appears in organic search results for those keywords instead of your default page. Each page gets its own impressions, downloads, redownloads, conversion rate, retention, and proceeds per paying user in App Analytics [source: developer.apple.com/app-store/custom-product-pages]. Give a page one tight keyword group, don't send ad or link traffic to it, and its numbers are about as close as App Store Connect gets to keyword-level conversion data.

Google Play Console, for the Android side

If you also ship on Android, Play Console's acquisition reports show the search terms that brought visitors to your listing, something Apple never shows. It won't describe iOS behavior, but terms that convert well on Google Play make a reasonable shortlist to test on the App Store. See how to read Play Console search analytics.

Making the Data Work Together

The practical workflow looks like this:

1. Use App Store Connect to monitor overall trends — impressions, conversion rate, retention — and the peer group benchmarks. These are your outcome metrics.
2. Use an ASO tool to track keyword rankings and identify opportunities. These are your input metrics — the levers you can pull.
3. When you make a change (update subtitle, add keywords, refresh screenshots), check both. The ASO tool shows whether your rankings moved. App Store Connect shows whether that ranking change translated to more impressions and downloads.
4. Watch conversion rate closely. If rankings improve but conversion drops, you might be ranking for keywords where user intent doesn't match your app. Adjust your keyword strategy or your product page accordingly.
5. Compare against last year, not just last week. Many categories are seasonal (fitness in January, finance around tax season), so a lift right after a metadata change may just be the calendar. Check the same period a year earlier before you credit the change.
6. Check sources periodically. A healthy app gets most organic traffic from search. If browse is your dominant source, your rankings may be weaker than you think and you're relying on algorithmic placement that could disappear.

App Store Connect analytics is a useful baseline, but it was designed as a reporting tool, not an optimization tool. Understanding what each metric actually means — and what's missing — is the first step toward making data-driven ASO decisions instead of guessing.