Measurement / ASO LENS GUIDE
What "App Store conversion rate" actually means
“Conversion rate” means something different depending on which App Store Analytics number you’re actually looking at. This article explains what Apple counts, and how ASO Lens computes each rate — with the exact denominator — using only facts verified against this codebase and Apple’s own documentation.
Published: 2026-09-17
Apple counts three separate kinds of events
App Store Connect’s analytics data tracks three broad kinds of events. Impressions are how many times your app’s icon appeared in App Store search results or browse listings. Product Page Views are how many times your app’s product page was actually opened. Downloads combine first-time downloads and redownloads. Each of the first two also has a “unique devices” version (Unique Impressions / Unique Product Page Views), so the same device seeing your app repeatedly in one day is only counted once.
The important part: these are independent counters. Apple does not track and publish individual user journeys — “this specific user went from impression to product page to download.” What’s published is period totals for each counter.
Search Page View Rate is not click-through rate
To express what share of App Store Search impressions actually led to an opened product page, ASO Lens computes a “Search Page View Rate” (Unique Product Page Views ÷ Unique Impressions, restricted to the App Store Search source). We deliberately never call this “CTR.” The App Store lets users download directly from a search result without ever opening the product page, so “impression → product page visit → download” isn’t a strict funnel every user passes through. A user who downloads without opening the product page never counts toward this metric’s numerator (Product Page Views), even though they do count toward Downloads. That’s a different premise than a typical web-ad CTR (share of impressions clicked, regardless of what happens after), so borrowing the word “CTR” here would misrepresent what’s being measured.
For the same reason, traffic from App Store Browse (listings, featured placements, etc.) gets its own separate “Browse Page View Rate.” Since Search and Browse can have meaningfully different paths to the product page, ASO Lens keeps them apart by source rather than blending them into one number.
“Conversion rate” changes meaning depending on the denominator
What ASO Lens calls “Apple Conversion Rate” is Total Downloads ÷ Unique Impressions — a whole-funnel figure: of everyone who saw the icon, what share eventually downloaded.
“Page Download Rate” (Total Downloads ÷ Unique Product Page Views) is a different question: of everyone who opened the product page, what share downloaded. The denominator is no longer everyone who saw the icon — it’s only the people who already made it to the product page. Because of the direct-download path from search results mentioned above, this rate can mathematically exceed 1.0 (100%), so ASO Lens treats it as meaningful only against the app’s own prior period, never as an absolute benchmark.
So the same phrase, “conversion rate,” can mean Unique Impressions (everyone who saw the app) or Unique Product Page Views (only those who already reached the page) as its denominator — and those describe very different things, with very different plausible ranges. If a number is presented as just “conversion rate: X%” with no stated denominator, there’s no way from the outside to know which of these it is, or whether it’s something else entirely. Since methodology can differ, comparing raw percentages across tools or apps isn’t comparing like with like.
What ASO Lens’s diagnosis logic actually looks at
ASO Lens’s acquisition-funnel diagnosis estimates bottlenecks by comparing these metrics against the app’s own immediately preceding period — never against an external “industry average CVR.” For example, when App Store Search’s Search Page View Rate drops meaningfully from the prior period, or sits at a structurally low absolute level (with enough impression volume to trust the reading), the diagnosis points at the product page itself — icon, screenshots, subtitle — ahead of keywords. Similarly, a drop in Page Download Rate points at screenshots and subtitle, and a drop or low level in the Browse-sourced metric gets the same treatment. These thresholds are ASO Lens’s own heuristics, not independently verified industry standards.
Summary
Before comparing conversion-rate percentages, check what the denominator actually is. ASO Lens records Apple Conversion Rate, Search Page View Rate, Browse Page View Rate, and Page Download Rate as separate metrics, each with its denominator stated explicitly. Collapsing any of them into one generic “conversion rate” makes it easy to fix the wrong thing.
ASO Lens records these metrics broken down by source (App Store Search, Browse, etc.) and always shows which denominator was used.
Get startedSources
- Apple, “App Store Search” — developer.apple.com/app-store/search (Apple’s own explanation of the relationship between search results and the product page, including direct downloads from a search result)