Apple defines App Store conversion rate as total downloads and pre-orders divided by unique device impressions. Total downloads include first-time downloads and redownloads. This is not the same as downloads divided by product-page views, which is a useful but different diagnostic ratio.
Apple’s official conversion-rate formula
Apple’s acquisition documentation describes conversion as the percentage of people who download after seeing the app on the App Store. If an app records 100 unique impressions and 25 total downloads during the same period, the reported conversion rate is 25%.
The denominator mistake that changes the diagnosis
Many teams informally call downloads divided by product-page views “App Store conversion.” That ratio can be valuable, especially when evaluating how well a product page converts people who actually opened it. But it answers a narrower question than Apple’s official metric.
| Metric | Formula | What it helps diagnose |
|---|---|---|
| Apple conversion rate | Total downloads ÷ unique impressions | The full path from App Store visibility to download, including downloads that can occur without a product-page visit |
| Product-page download rate | Attributed downloads ÷ unique product-page views | How effectively the detailed page turns page visitors into downloads |
| Impression-to-page rate | Unique product-page views ÷ unique impressions | Whether the icon, title, subtitle, rating, and search context persuade someone to inspect the page |
Mixing these denominators can send a team toward the wrong experiment. A weak impression-to-page rate suggests the search-result promise or audience may be wrong. A healthy page-view rate with weak official conversion can point upstream. A weak page-view rate makes screenshots, previews, localization, and product-page message more plausible areas to investigate.
There is no honest universal benchmark
A single internet-wide “good conversion rate” ignores category, business model, download volume, source type, storefront, and whether an app receives direct downloads from search results. Apple provides a more defensible comparison: privacy-preserving peer groups built from similar apps.
Apple’s benchmark view can compare an app with the 25th, 50th, and 75th percentile for relevant peer groups. The group can account for App Store category, business model, and download-volume tier. Use that context before adopting a generic number from an unrelated category.
How to diagnose a weak conversion rate
- Confirm the metric and denominator. Decide whether you are reading Apple’s impressions-to-download conversion or a product-page-specific ratio.
- Segment by source type. App Store Search, Browse, App Referrers, and Web Referrers carry different intent. A blended average can hide a strong source and a weak one.
- Compare storefronts and product pages. Message, localization, ratings, and audience intent vary by territory and custom product page.
- Align the change timeline. Mark icon, screenshot, preview, localization, price, release, and campaign changes against the metric.
- Check downstream quality. More downloads are not a win if activation, trial quality, paid conversion, or retention declines for the acquired cohort.
Choose the experiment that matches the loss
| Observed pattern | Most relevant next evidence | Possible experiment |
|---|---|---|
| Impressions are healthy; page views are weak | Source type, keyword intent, icon/title/subtitle context | Test the search-result promise or audience alignment |
| Page views are healthy; downloads are weak | First screenshots, preview, rating, localization | Run Product Page Optimization on one clear hypothesis |
| Downloads rise; activation falls | Onboarding funnel by acquisition source | Fix expectation mismatch or first-session friction |
Use Apple’s testing tools without overclaiming causality
Product Page Optimization can test icons, screenshots, and app previews against the original page. Custom Product Pages can align different messages with different audiences. Both are useful when the evidence points to the store experience—but neither explains a downstream activation or billing problem by itself.
Treat the test result as one piece of the growth journey. Check whether the acquired cohort activates, reaches the paywall, starts a trial, becomes paid, and retains. A higher download conversion rate with lower-quality users may move one chart while weakening the business.
Connect conversion to the keywords that drive it
Store conversion is one transition in the search journey. The useful question is not only “did more people download?” but “which keywords bring people who actually convert?”
The public keyword data map explains which search signals are honestly available. For the full workflow, read the practical guide to App Store keyword research .