ASO Metrics to Track: The KPIs That Matter

Track five groups of ASO metrics: visibility (keyword rankings and impressions), conversion (product page views and conversion rate), acquisition source (where installs come from), quality (ratings, reviews, crashes, retention) and change impact (before and after results for each listing edit). Most teams watch too many numbers and read too few. This guide defines each metric the way the stores do, shows how the numbers connect, and explains how to decide whether a change helped.
TL;DR
- Visibility comes first: keyword rankings and unique impressions tell you whether people can find the app at all.
- Conversion is the multiplier: Apple defines conversion rate as downloads and pre-orders divided by unique device impressions, so it reflects your whole listing, not just the page.
- Split installs by source before celebrating growth. App Store Search includes paid ads, so organic needs separating.
- Judge every listing change against a baseline, by territory, over a long enough window to rule out noise.
Table of Contents
- The ASO metrics worth tracking, at a glance
- Visibility: keyword rankings and impressions
- Conversion: where listing work pays off
- Acquisition source: separating organic from everything else
- Quality: ratings, reviews, crashes and retention
- How to compare metrics across countries and stores
- How often to review, and how to tell if a change worked
- A worked example
- Perspective: why we track fewer numbers, more often
- Put the metrics to work with appXL
- FAQ
- Sources
The ASO metrics worth tracking, at a glance
The metrics below follow the path a user takes: they see your app, open the page, install, and stay. Each stage has one or two numbers that matter most.
| Stage | Metric | What it tells you | Where to read it |
|---|---|---|---|
| Discovery | Keyword rankings | Whether you appear for the searches that matter | A rank tracker |
| Discovery | Unique impressions | How many devices saw your app | App Store Connect, Play Console |
| Consideration | Product page views | How many people opened your listing | App Store Connect, Play Console |
| Conversion | Conversion rate | How well the listing turns viewers into installers | App Store Connect, Play Console |
| Source | Downloads by acquisition source | Organic versus paid and referral | App Store Connect, Play Console |
| Quality | Ratings and reviews | Trust at the moment of decision | Both consoles |
| Quality | Crashes, sessions, active devices | Whether the product holds up after install | Both consoles |
| Retention | Retained installers or active devices | Whether installs turn into users | Both consoles |
The rest of this article takes these in order.
Visibility: keyword rankings and impressions
Keyword rankings
Rankings answer a simple question: for the searches your buyers type, where do you appear? Neither store gives you a full ranking report, so teams use a rank tracker. What matters is the set of keywords you track, not the number. Track three groups separately:
- Brand terms, which should sit at or near the top and rarely need work.
- Core category terms, the high-volume phrases competitors fight over.
- Long-tail terms, where a smaller app can realistically reach the top results.
Report movement by group. A single blended average hides the story: you can lose three positions on a hard category term while gaining ten across the long tail, and the average will look flat. If you are setting up tracking from scratch, our explainer on app store rank tracking covers what to monitor and how often, and the keyword research process shows how to choose the terms in the first place.
Rankings also need context. A position on a term nobody searches is worth nothing, so pair each tracked keyword with an estimate of difficulty and popularity. A free keyword difficulty checker helps you separate terms worth chasing from vanity targets.
Impressions
Impressions are the outcome of rankings. App Store Connect reports Unique Impressions as the number of unique devices that viewed your app on the App Store for a given day, week or month. Because it counts devices, not views, it is a cleaner measure of reach than a raw count.
Read impressions next to rankings. If rankings improve and impressions do not, the terms you moved up on have little search volume. If impressions rise without any ranking change, look at seasonality, a feature placement or a paid campaign.
On Google, the Play Console reports store listing visitors and store listing acquisitions, which play the same role as the Apple page-view and download pair.
Conversion: where listing work pays off
Visibility brings people to the door. Conversion decides whether they walk in. This is the stage where screenshots, the icon, the title and subtitle, the preview video and the ratings all work together.
Product page views and conversion rate
Apple’s metric definitions describe product page views and conversion rate as the measures of how effective your App Store presence is. The precise definition matters: Apple measures conversion rate as total downloads and pre-orders divided by unique device impressions. That is impressions to install, not page view to install.
Two consequences follow:
- A change to your icon or first screenshot can move conversion rate even if nobody opens the page, because the icon appears in search results.
- If you compare your number with a figure from another tool or a blog post, check which denominator it uses. Page view to install and impression to install differ a lot, and comparing them will mislead you.
Rather than chase an industry benchmark, benchmark against yourself: the same app, the same territory, the same source type, over time. Google also shows how your store listing conversion rate compares with similar apps in its acquisition reports, which is a more useful reference point than a number from a random article.
If conversion is your weak stage, our guide to turning impressions into installs walks through the listing elements to change first.
Custom product pages
Once you run paid traffic or several audiences, a single conversion rate stops being informative. Apple lets you create custom product pages that highlight specific features or content, and App Analytics shows impressions, downloads and conversion rate for each page. Track each page as its own row. A page built for one campaign should be judged on that campaign’s traffic, not blended into the default page.
To build the tracked links, the custom product page URL generator creates them without manual editing, and the guide on matching ad to page explains how to pair each ad with a page.
Acquisition source: separating organic from everything else
A rising download count is not proof that ASO is working. You need to know where the downloads came from.
App Store Connect lets you compare acquisition by source type, including search, browse, referrals and campaigns, and filter by territory. One trap deserves attention: App Store Search includes ads that appear in search results. If you run Apple search ads, some of what looks like organic search is paid. Check your campaign reports and subtract what you paid for before you credit your metadata.
A workable routine:
- Report downloads by source type every week.
- Keep search and browse in separate lines, since they respond to different changes. Metadata mostly moves search. Featuring, charts and category position move browse.
- Flag any week with a campaign, a press hit or a featured placement, so it does not get credited to an unrelated edit.
Campaign traffic from outside the stores has its own measurement logic. If you buy creator or influencer placements, judge them on the reach and audience data behind the price, the same way reach-based campaign metrics are used to evaluate streamer bookings, then tag the traffic with its own custom product page so it shows up as its own source.
Quality: ratings, reviews, crashes and retention
These metrics are not conversion levers on their own, but they feed into conversion and into how the store treats your app over time.
Ratings and reviews. Rating average and volume appear on the listing, so they affect how many viewers install. Track the average for the current version separately from the lifetime average, and monitor the share of reviews that mention a specific issue. A pattern of complaints about one bug is both a product signal and a conversion risk.
Crashes and sessions. Apple’s usage metrics include active devices, sessions and crashes. A release that raises crashes will often lower ratings a week later, so watch crashes right after every version ships.
Retention. App Store Connect reports Active Devices and Active in Last 30 Days. On Google, the Retained Installers view in the acquisition reports shows unique users who visited your listing, installed, and kept the app for up to 30 days. Use these to check that the people your listing attracts actually stay. If a new screenshot set lifts installs but retention falls, the listing may be promising something the app does not deliver.

How to compare metrics across countries and stores
The two stores do not report the same things in the same way, and territories do not behave alike. Three rules keep comparisons honest.
- Compare like with like. Apple counts impressions to downloads. Google reports store listing visitors and acquisitions. Treat the two conversion rates as separate series and never average them.
- Segment by territory. App Store Connect lets you filter acquisition by territory, so use it. A strong US result tells you nothing about Germany or Japan, where search terms, competitors and seasonality differ.
- Separate language from country. One language can span many markets, and one market can use several languages. Track localized metadata by the storefront it ships in, then compare a translated market with its own pre-translation baseline rather than with the home market.
Localization is a common source of misread results. A localized listing may improve rankings for new keywords while the headline download figure barely moves, because the market is small. Look at impressions and ranked keyword count in that market first. Our localization guide covers how to structure multi-market reporting.
How often to review, and how to tell if a change worked
A good review rhythm has three layers:
- Daily or weekly: rankings, crashes, new reviews. These move fast and allow quick reaction.
- Weekly or biweekly: impressions, page views, conversion rate, downloads by source.
- Monthly: retention, territory comparisons, keyword set review.
For listing changes, the standard is stricter than “the number went up.” Treat a change as a success when it produces a lasting, statistically meaningful lift in organic downloads or conversion rate, not a bump you could get from a normal week. To get there:
- Record a baseline of at least a few weeks for the metric and territory.
- Change one major element at a time where you can, or log everything you changed and when.
- Exclude weeks with campaigns, featuring or outages.
- Compare the same weekdays and similar seasons.
- Where traffic allows, run a controlled test instead of a before and after comparison. Our guide to product page optimization explains how Apple’s native tests work, and A/B testing covers running and reading them.
After store algorithm changes, rankings can swing for reasons unrelated to your listing. Resist rewriting metadata the first time you see movement. First check which keywords moved, whether competitors moved too, and whether impressions followed.
The ASO checklist gives you 24 checks to run before shipping, which makes later attribution easier. Our deeper reference on ASO KPIs and ranking factors and the ASO metrics guide go further on how each number is read.
A worked example
Suppose a fitness app has the following in one territory over four weeks, before and after a subtitle and screenshot update (illustrative numbers, not client data):
| Metric | Before | After |
|---|---|---|
| Unique impressions | 40,000 | 41,000 |
| Downloads | 1,200 | 1,435 |
| Conversion rate | 3.0% | 3.5% |
| Ranked keywords in top 10 | 22 | 21 |
Impressions barely moved and rankings are flat, so the lift comes from conversion: the new creative persuades more of the same audience. The conclusion is that the screenshots worked, not the subtitle. If you had looked only at downloads, you might have credited the wrong change. This is why you read the full chain, not a single headline number.
Perspective: why we track fewer numbers, more often
We build appXL around one belief: an ASO tool that only reports data leaves the hardest part to you. Most teams do not fail at ASO because they lack metrics. They fail because the metrics sit in three dashboards, nobody reads them on a schedule, and acting on them means a manual metadata rewrite, a translation round and a submission.
So our advice is to pick a short list, connect each metric to a decision, and shorten the gap between reading and acting. Rankings falling on a core term should trigger a keyword review. Conversion falling in one territory should trigger a creative or localization check. Crashes rising after a release should trigger a hold on promotion. If a metric does not lead to a decision, stop reporting it.
That is also why we built our product to monitor rankings daily, rewrite metadata and ship updates through App Store Connect. The measurement is only worth the action it triggers.
— Samuel
Put the metrics to work with appXL
If you want these metrics monitored and acted on without a manual loop, appXL analyzes competitors and market trends, rewrites metadata, localizes listings into over 35 languages, tracks rankings daily and ships updates directly to App Store Connect. Plans (Starter, Growth and Scale) are on the pricing page. You can also start with our free tools for ASO audits and keyword coverage checks to see where your listing stands today.
FAQ
What are the most important ASO KPIs?
Start with keyword rankings, unique impressions, conversion rate and downloads by source. Together they show whether people can find you, whether they install, and whether the installs came from organic search. Add ratings, crashes and retention once those four are reliable.
How is conversion rate defined in the App Store?
Apple measures conversion rate as total downloads and pre-orders divided by unique device impressions. That differs from the common page-view-to-install ratio, so check the denominator before comparing your figures with any outside benchmark.
How can I tell whether installs are organic?
Use the acquisition report in App Store Connect and compare source types such as search, browse, referrals and campaigns. Remember that App Store Search includes ads in search results, so subtract paid activity before attributing growth to ASO.
How long should I wait before judging a listing change?
Wait until you have enough traffic to separate the change from normal weekly variation, which for most apps means several weeks, not a few days. Exclude weeks with campaigns or featuring, and compare against the same territory and source type. A controlled test gives a cleaner answer than a before and after comparison.
Sources
- Acquisition, App Store Connect Analytics (Apple)
- Metric definitions, App Store Connect Analytics (Apple)
- Configure multiple product page versions (Apple)
- View app statistics (Google Play Console Help)
- Measure your app’s acquisition and retention (Google Play Console Help)
- Reach-based campaign metrics