App Store Connect Analytics can tell you whether your ASO work is creating more visibility and downloads. It cannot tell you everything you need to know about individual keywords.
That distinction matters. Developers often update their title, subtitle, keyword field, or screenshots, then open App Store Connect and look only at total downloads. If downloads did not immediately rise, they assume the update failed. If downloads did rise, they do not know which change caused it.
The better approach is to read App Store Connect Analytics as a funnel:
Impressions → product page views → downloads → retention → revenue.
Each stage answers a different question. Are people seeing the app? Are they opening the listing? Does the page convince them to download? Do they keep using the product after installation?
Apple’s current App Analytics includes acquisition, usage, sales, subscription, cohort, and peer-group benchmark data. Apple’s App Analytics overview
This guide focuses on the metrics that matter most for ASO and the decisions each one should lead to.
The ASO metrics to monitor first
You do not need to track every metric in App Store Connect on day one. Start with the small set that maps directly to the App Store discovery and conversion funnel.
| Metric | What it tells you | Main ASO question |
|---|---|---|
| Unique impressions | How many unique devices saw your app on the App Store | Is visibility growing? |
| Unique product page views | How many unique devices opened your listing | Did the search result earn a tap? |
| Total downloads | First-time downloads and redownloads | Did the listing produce installs? |
| Conversion rate | Downloads and pre-orders divided by unique impressions | Does the listing convert visibility? |
| App Store Search source | Downloads attributed to App Store Search | Is organic discovery contributing installs? |
| Retention rate | How many downloaded devices continue using the app | Are new users finding the right promise? |
| Crashes and deletions | Stability and early product failure signals | Is a product problem damaging ASO outcomes? |
Apple defines impressions, product page views, downloads, and conversion rate in its official Analytics metric definitions.
1. Unique impressions: measure visibility first
An impression is an opportunity to be discovered. It does not mean someone opened your product page or downloaded your app.
Unique impressions measure the number of unique devices that viewed your app on the App Store during the selected period. Use this metric to understand whether your listing is appearing more often after a metadata change or a market expansion.
Impressions can increase because of several different events:
- Your app ranks for more relevant searches.
- Existing keywords move higher in search results.
- Your app receives more Browse or Today tab exposure.
- A campaign or external mention sends more people into the App Store.
- A new country or localization begins generating demand.
That is why impressions alone are not a success metric. More visibility is useful only if it reaches the right users and produces product page views and downloads.
How to use impressions after an ASO update
Record your baseline before submitting a metadata update. Then compare the same time window after the update rather than comparing one unusually strong day with one weak day.
For example:
- Baseline: 1,000 unique impressions per week
- Four weeks later: 1,800 unique impressions per week
- Interpretation: visibility likely improved, but investigate source and conversion before calling the update a win
If impressions stay flat, check whether the update actually changed an indexed field, whether Apple has had enough time to process it, and whether the target keywords are too competitive. Your App Store keyword ranking guide can help measure individual positions that App Store Connect does not expose.
2. Product page views: did users tap?
Product page views show how many times people accessed your App Store listing. Unique product page views show how many unique devices viewed it.
The relationship between impressions and product page views helps diagnose your search-result presentation.
High impressions, low product page views
This pattern usually means your app is visible but not compelling enough to tap.
Possible causes include:
- An unclear app title or subtitle
- An icon that does not stand out
- Weak relevance between the search and the visible listing copy
- A low rating compared with nearby results
- A category where users can understand the alternatives without opening them
Improve the search-result promise first. Review the app name, subtitle, icon, and rating together. Do not immediately rewrite the full description — users may not reach it until they have already opened the page.
Impressions and product page views both rise
This is a stronger visibility signal. Your app is being shown and earning more attention. The next question is whether the product page converts those visitors into downloads.
3. Conversion rate: does the listing persuade?
Apple defines conversion rate as total downloads and pre-orders divided by unique device impressions. This is important: the metric is calculated against unique impressions, not simply product page views.
A simplified example:
1,000 unique impressions
↓
100 total downloads
↓
10% App Store conversion rate
Conversion rate is influenced by more than screenshots. It reflects the complete first impression: relevance, title, subtitle, icon, rating, pricing, screenshots, preview video, description, and the expectations created by your marketing.
High impressions, low conversion
Your app is being discovered, but the listing is not closing the decision. Focus on conversion assets:
- Make screenshot one communicate the primary user outcome.
- Show the product in use instead of presenting only feature labels.
- Make the pricing and subscription model clear.
- Improve the first two lines of the description.
- Respond to recent technical complaints that create doubt.
- Test different icons, screenshots, and previews through Product Page Optimization when enough traffic is available.
The App Store Screenshot Sizes and Dimensions guide covers the technical and conversion side of screenshot design.
Low impressions, strong conversion
This is an important opportunity. Users who find your app like what they see, but not enough people are discovering it.
Focus on visibility rather than redesigning the entire listing:
- Research more achievable keywords.
- Improve the title and subtitle around high-intent phrases.
- Fill unused keyword-field space without repeating indexed words.
- Localize markets where relevant search demand exists.
- Track competitor keyword gaps.
Do not sacrifice a strong conversion rate by stuffing more keywords into the title. Improve reach while preserving the promise that already converts.
4. App Store Search: measure organic acquisition
App Store Connect can break acquisition data down by source type, including App Store Search, App Store Browse, App Referrers, Web Referrers, and campaigns.
For ASO, App Store Search is the most useful source because it shows whether search is contributing downloads. It still does not identify the exact search query behind each install. You need a rank tracker for that.
Use the source breakdown to answer:
- Are downloads growing from search or only from external promotion?
- Did localization produce App Store Search downloads in a new country?
- Does Browse generate more downloads but lower retention than Search?
- Are paid campaigns creating installs that would otherwise be attributed differently?
Compare source type with conversion rate and retention. A channel that produces fewer downloads but stronger retention may be more valuable than one that produces a large number of low-quality installs.
Apple’s Acquisition Analytics guidance explains how to use source types and segment the acquisition funnel.
5. Territory: find where localization is working
Global totals hide market-level opportunities. Always review App Store Analytics by country or territory when localization is part of your strategy.
Look for three patterns:
A country with downloads but no localized metadata
This is a strong candidate for localization. Existing downloads indicate some demand, while local metadata may unlock searches your English listing does not cover.
A country with impressions but weak conversion
Your app is appearing, but the listing may not feel native. Check the localized title, subtitle, screenshots, description, pricing, and reviews. A translated keyword field with English screenshot headlines can create a trust gap.
A country with localized metadata but no impressions
The market may lack demand for your current keyword set, the terms may be too competitive, or the app may not be distributed in that territory. Recheck the local keyword research before assuming that translation failed.
This is the difference between international availability and international discoverability. LocalizeRank’s App Store localization service is built around market selection, local keyword research, metadata, screenshot copy, and post-submission tracking.
6. Retention: did the right users download?
Retention shows the percentage of devices that continue using the app after download. It is not a pure ASO metric, but it tells you whether your listing promise matches the product experience.
Low retention after a metadata change can mean:
- The keyword attracts users who need a different product.
- The screenshots promise a feature that is difficult to find.
- Onboarding does not deliver the result shown in the listing.
- A technical issue affects new users.
- The app is useful, but the first session does not explain how to reach value.
Do not optimize conversion in isolation. A misleading promise can increase downloads temporarily while creating more deletions, negative reviews, and support issues.
Use retention alongside your App Store reviews and ratings workflow. Reviews often explain the reason behind a retention drop better than the dashboard alone.
7. Crashes, deletions, and product health
An ASO update cannot compensate for an unstable app. If crashes or deletions increase after a release, first fix the product problem before changing keywords again.
A useful diagnostic sequence is:
- Check whether the change in crashes started with a specific app version.
- Compare the affected device types and operating systems.
- Read reviews from the same time period for matching complaints.
- Fix the issue and mention it clearly in release notes.
- Recheck conversion, ratings, retention, and deletions after the fix.
This prevents a common mistake: interpreting a product-quality problem as a metadata problem.
How to measure an ASO update correctly
Use a simple before-and-after measurement plan for every meaningful change.
Before submission
Record:
- Metadata version and submission date
- Target keywords and current positions
- Unique impressions
- Product page views
- Conversion rate
- App Store Search downloads
- Ratings and review count
- Top territories
Two to four weeks after approval
Check whether impressions and App Store Search visibility have started to move. Confirm that the new keywords are indexed in your rank-tracking tool.
Six to eight weeks after approval
Compare a stable time window against the baseline. Review conversion, downloads, source type, territory, ratings, and retention together.
Do not change five variables at once if you want to learn. If you update the title, screenshots, icon, pricing, and product at the same time, Analytics may show an outcome but not which change created it.
Metrics that can mislead you
Total downloads alone
Downloads can rise because of a campaign, a feature, a seasonal spike, or a product announcement. Always segment by source and territory.
Average conversion rate alone
A global average can hide a strong market and a weak one. Segment by source, country, device, and product page where possible.
One-day changes
App Store data fluctuates. Use weekly or multi-week trends instead of reacting to a single day.
Search downloads without rank data
Search downloads confirm that search contributes to acquisition, not which keyword caused the result. Combine App Store Analytics with keyword position tracking.
Peer benchmarks without context
Apple’s peer-group benchmarks are useful context, but category, business model, download volume, territory, and product quality still matter. A benchmark is a starting point for investigation, not a universal target.
App Store Connect Analytics checklist for ASO
- Record a baseline before every meaningful ASO update.
- Track unique impressions, not only total downloads.
- Monitor unique product page views.
- Review conversion rate against your own historical baseline.
- Segment App Store Search from Browse and referral sources.
- Compare results by territory when localizing.
- Track keyword positions separately from App Store Connect.
- Check ratings and reviews after each major release.
- Review retention before celebrating a download increase.
- Check crashes and deletions for product-quality issues.
- Wait long enough for indexing and a meaningful sample size.
- Change one major listing variable at a time when possible.
The practical takeaway
App Store Connect Analytics is most useful when you connect each metric to a decision:
- Impressions tell you whether visibility is expanding.
- Product page views tell you whether the search result earns attention.
- Conversion rate tells you whether the listing persuades.
- Source data tells you whether search is producing acquisition.
- Territory data tells you where localization is working.
- Retention and product health tell you whether the promise matches the experience.
Use Analytics to measure outcomes, and use keyword rank tracking to understand the individual search terms behind those outcomes. Together, they turn ASO from a series of guesses into a measurable improvement process.