App Store Conversion Rate: Definition, Benchmarks, Fixes

App store conversion rate is the share of people who see your app and then download it. Apple divides total downloads by unique impressions, so a rate is only “good” when you compare it with similar apps, the same traffic source and your own history. This guide explains how the number is calculated, why published benchmarks disagree, how to find your real peer benchmark in App Store Connect, and which listing changes actually move the rate.

TL;DR

• Apple defines conversion as total downloads (first-time downloads, redownloads and pre-orders) divided by unique impressions. Other tools and Google Play define it differently, so never compare numbers across definitions.
• There is no single good rate. Your benchmark is the 25th, 50th and 75th percentile of your peer group in App Store Connect, which Apple describes as directional.
• Diagnose by traffic source and over time, not from one blended number.
• The biggest levers are the listing assets people see first (icon, screenshots, preview video), localization, and matching custom product pages to the traffic that lands on them.
• Test changes with Product Page Optimization instead of guessing, and read results at the confidence level Apple reports.

Table of Contents

• What app store conversion rate measures
• What counts as a good conversion rate
• How to read your own number
• Changes that raise app store conversion rate
• Test instead of guessing
• A simple 30-day plan
• What we think about conversion rate
• Where appXL fits
• FAQ
• Sources

What app store conversion rate measures

Apple’s own definition is the one that matters for your App Store Connect dashboard. According to Apple’s guidance on measuring app performance, conversion is total downloads, including first-time downloads, redownloads and pre-orders, divided by unique impressions from App Store tabs or the product page. Apple’s worked example: 50 total downloads from 100 unique impressions is a 50% conversion rate. That is a demonstration of the formula, not a market average.

Two details change how you read the figure.

Pre-orders count once. Apple’s peer group benchmarks documentation says a pre-order counts toward conversion and is not counted again when it later downloads.

Redownloads count too. Because the numerator is total downloads, a returning user who reinstalls your app lifts the rate. An app with a large lapsed audience can look better than one that mostly acquires brand-new users, even if its listing persuades fewer strangers.

There is also a data threshold. Apple’s performance metrics reference states that conversion-rate data becomes available once an app has at least five first-time downloads or pre-orders. If your dashboard is empty, you are likely under that line.

Conversion rate, product page views and install rate are different things

Much of the confusion in articles about this topic comes from mixing three ratios:

When a source says the average is 3% and another says it is 30%, they are usually measuring different steps in this funnel, or using different traffic and different periods. Check which ratio a number describes before you hold your own app against it.

What counts as a good conversion rate

Search for a benchmark and you will find figures that differ by an order of magnitude. That is not because someone is wrong. Averages depend on the definition, the store, the country, the period, the set of apps included, and whether the figure starts at an impression or at a product page view. A pooled average across every category also hides the fact that a utility with a clear promise and a hobby game with a crowded category are playing different games.

Google changed the picture further. Google Play Console’s help documentation now centers its performance reporting on unique user clicks (Install, Open or Pre-register) from the store listing, rather than a classic acquisition-based conversion rate. If you run both stores, treat the Android figures as a separate system, not a number to line up against the App Store.

So instead of asking what the average is, ask three narrower questions:

1. How do I compare with apps like mine, in my category and business model?
2. How do I compare with myself, by traffic source, last quarter?
3. Which step of the funnel is weakest?

Use Apple’s peer group benchmarks

The most defensible benchmark is the one Apple gives you. In App Store Connect Analytics, peer group benchmarks let you compare your conversion rate with similar apps. The peer group is based on category and business model (for example free, paid or subscription), and you can refine it by download volume. Results are shown as the 25th, 50th and 75th percentiles.

A simple way to read it:

• Below the 25th percentile: your listing is losing people that most similar apps keep. Start with a listing audit.
• Between the 25th and 75th: you are typical. Gains come from testing, not repairs.
• Above the 75th: you are already persuasive. Look at whether you are leaving volume on the table through discoverability instead.

Apple states that these comparisons are directional, not an exact ranking, and that it uses differential privacy to keep individual apps’ performance data private. Treat the percentile as a signal about where to look, not a grade.

How to read your own number

A blended conversion rate is the least useful version of the metric. Apple recommends viewing the metric by source type and over time to understand the quality of acquisition and the effect of product page changes. Here is how that plays out in practice.

Split by traffic source

The same page converts very differently depending on how someone arrived:

• App Store search: the person typed a query and has intent. A low rate here often means your listing does not match the keywords you rank for, or the first screenshot does not answer what they searched.
• App Store browse: people exploring tabs or recommendations are less committed, and rates are usually lower.
• Web referrers and App Referrers: visitors come with context from somewhere else. If the destination page does not match the message that sent them, conversion drops.
• Campaigns: paid traffic needs a page built for the ad. This is where custom product pages matched to the ad earn their place.

If your blended rate fell, check the mix first. A new campaign sending colder traffic can lower the average while every individual source stays flat.

Track over time and annotate changes

Keep a change log: icon swaps, new screenshots, a rewritten subtitle, a new localization, a price change, a release that reset your ratings. Without it, a movement in the chart is just a movement. With it, you can connect a step change to its cause.

Watch for seasonality and for ranking shifts too. When you start ranking for broader keywords, impressions rise and the incoming audience is less qualified, so conversion can dip even as downloads grow. Read the rate together with impressions and downloads, never alone.

Compare peers by volume

Small apps see noisy data. A few dozen downloads can swing the rate several points in a week. Judge changes over a long enough window, and prefer tests with a proper sample over before-and-after comparisons.

Changes that raise app store conversion rate

Conversion is a persuasion problem. A visitor decides in seconds, mostly from what is visible without scrolling: icon, name, subtitle, the first screenshots or video, rating and review count. The levers below are ordered roughly by how often they matter.

1. Screenshots and creative

The first two or three screenshots do most of the work. Each should make one promise, in a few words, over a clear image of the product in use. Lead with the outcome the user wants, not a feature name. Our guide to screenshots and creative that convert goes through layouts and caption patterns, and the note on creative asset changes in iOS 27 covers what Apple is changing.

Creative also has to fit the category and the intent. An outdoor app might lean on aspirational imagery, while a finance tool might lean on clarity and trust cues.

2. App preview video

A video autoplays on the product page and can show flows a still cannot. It helps most when the value of the app is in motion or sequence. It can also hurt if the first seconds are slow, because it pushes screenshots down. See how to make an app preview video for specs and strategy.

3. Localization

Apple advises that apps supporting multiple languages should localize descriptions, keywords, app previews and screenshots for each target market, translate the app name where it makes sense and adapt keywords to local values, as described on Apple’s product page guidance. A machine-translated caption on a screenshot that still shows English UI is a common reason a market underperforms.

Do it in order of opportunity, not alphabetically. Start with markets where you already have traffic, measure the effect, then widen. Our articles on testing localization before scaling and on the multi-market approach show how to prioritize.

4. Custom product pages

Apple lets you create custom product pages that highlight specific features or content. They are most valuable when you control the link: paid campaigns, partner promotions, email, and web banners. A user who clicked an ad about budgeting should land on a page that opens with budgeting. You can build the links with our free custom product page URL generator.

Google Play has a parallel feature. Its custom store listings let you tailor content to segments, such as people from different countries or arriving through specific campaigns.

5. Title, subtitle and description

Keywords get people to your page, but copy decides whether they stay. A subtitle that states what the app does in plain words converts better than a slogan. Make sure the promise you rank for is the promise the page keeps. The full listing optimization checklist lists every field and what to put in it.

6. Ratings and reviews

Rating and review count sit beside the install button. A drop in average rating after a buggy release can lower conversion before anyone reads a word of your copy. Respond to reviews, fix recurring complaints, and ask for ratings at moments of success inside the app.

Test instead of guessing

The most reliable way to lift conversion is a controlled test. Apple’s Product Page Optimization lets you run up to three alternative treatments against the original page, comparing icons, screenshots and preview videos to see which drives higher conversion. Its dashboard uses a 90% confidence level to indicate whether a treatment performs statistically better or worse than the baseline.

Practical rules that keep tests honest:

• Change one idea per test. A new icon plus new screenshots tells you nothing about which worked.
• Let it run to a conclusion. Stopping at the first green number inflates false wins.
• Test where traffic is. A test on a market with a trickle of impressions will take forever. Pick your largest locale first.
• Carry winners forward. Apply the winner, then test the next idea against it.
• Record losers. A failed hypothesis is still knowledge about your audience.

Our guides explain how to set up App Store A/B testing, free tools and sample size, and how Product Page Optimization works in detail.

A simple 30-day plan

Week 1: Baseline. Open App Analytics and note your conversion rate by source for the last 90 days. Check your peer group percentile. Write down your top five locales by impressions.

Week 2: Audit. Walk through your page as a stranger. Does the first screenshot make a promise? Do the title and subtitle match it? Are ratings healthy? Are localized pages truly localized? Use the 24-point ASO checklist if you want a structure.

Week 3: Launch one test. Pick the highest-impact asset, usually the first screenshot set, in your largest locale. Start a Product Page Optimization test with a clear hypothesis.

Week 4: Read and repeat. If the result reaches confidence, apply it and queue the next test. If not, extend the run or sharpen the hypothesis. Meanwhile build one custom product page for your best-performing campaign.

Repeat monthly. Compounding small wins is how listings get materially better over a year.

What we think about conversion rate

Most teams treat conversion rate as a number to look up. We treat it as a loop to run. Benchmarks are useful for deciding where to start, but the real gains come from a steady rhythm: look at the data by source, form a hypothesis, change an asset, test it, ship the winner, and do it again. The reason this rarely happens is not lack of ideas. It is the manual work between the idea and the live page: writing the variations, localizing them, setting up the test, waiting, reading it correctly, and pushing the update through App Store Connect.

That gap is why we built appXL to act as an agent rather than another dashboard. Data-only tools tell you the rate is low and leave the work to you. We would rather analyze competitors and market trends, rewrite metadata, localize listings into more than 35 languages, and ship the changes to App Store Connect, so optimization keeps moving every day instead of every quarter. If you remember one thing from this guide, make it this: the team that runs more good tests wins, and the way to run more tests is to remove the friction around them.

— Samuel

Where appXL fits

If you would rather not carry the manual work yourself, appXL handles ongoing optimization for you: competitor and trend analysis, metadata rewriting, localization, rank tracking, review management and A/B testing that is run and read for you, with updates shipped straight to App Store Connect. Our conversion rate optimization approach is built for startups, established companies and marketing teams who want results without the hassle of manual updates. See the plans on the pricing page.

FAQ

What is a good app store conversion rate?

There is no universal number. The useful answer is your position among similar apps: Apple’s peer group benchmarks show the 25th, 50th and 75th percentiles for your category and business model. Aim to move from where you are, and compare by traffic source rather than one blended figure.

How does Apple calculate app store conversion rate?

Apple divides total downloads, including first-time downloads, redownloads and pre-orders, by unique impressions. Fifty downloads from 100 unique impressions would be 50%. Data appears once an app has at least five first-time downloads or pre-orders.

Why do published benchmarks disagree so much?

They often measure different steps, such as impression to download versus page view to download, and they cover different stores, countries, categories and periods. Google Play has also shifted its reporting toward unique user clicks from the listing. Use a benchmark only when its definition matches yours.

What is the fastest way to improve conversion?

Start with the first screenshots in your biggest market and run a Product Page Optimization test against them. Pair that with a localized page for your top non-English markets and a custom product page for your main paid campaign. Each of these changes what people see before they decide.

How long should a Product Page Optimization test run?

Run it until the dashboard reports a result at Apple’s 90% confidence level rather than stopping at the first promising number. Low-traffic apps need longer, so test in your highest-impression locale first.

Sources

• Measuring app performance, Apple Developer
• Peer group benchmarks, App Store Connect Help
• Metric definitions, App Store Connect Help
• Product Page Optimization, Apple Developer
• Create your product page, Apple Developer
• Understand and grow your app’s user base, Play Console Help

Recommended

• App Store CRO: Turn Impressions Into Installs
• App Store A/B Testing, Run and Read For You
• App Store Rank Tracking, Explained Properly
• App Store Listing Optimization: The Full Checklist