Fixing a Falling App Store Conversion Rate
Your conversion rate is the share of people who see your app in the store and go on to install it. When impressions stay steady but installs slide, something on the listing, in the reviews or in the traffic mix has stopped persuading people.
The fall rarely has one obvious cause, and changing everything at once usually makes it worse because you lose track of what helped. This guide shows how to read the conversion numbers each store gives you, split them until you find the stage and source that is leaking, and test one fix at a time.
The two-stage store funnel
Both stores report a similar path from being shown to being installed, but they name the steps differently and a "conversion rate" can mean different things depending on which report you read.
| Stage | App Store Connect | Google Play Console | What decides it |
|---|---|---|---|
| Seen | Impressions: the app was shown in search, browse or a referral | The store listing reports start at the visit to the listing, so this stage is harder to see | Ranking, category, featuring, ads |
| Looked closer | Product page views | Store listing visitors | Icon, name, subtitle or short description, rating, first screenshots in results |
| Installed | First-time downloads (and redownloads, shown separately) | Store listing acquisitions | The full listing: screenshots, video, description, reviews, price, size, privacy details |
On iOS, the conversion rate in App Analytics compares downloads with unique impressions, so it blends two decisions: whether someone taps into your page from a search result, and whether they install once there. Many apps are installed straight from the search result without the page ever being opened. On Google Play, the store listing acquisition rate compares installs with listing visitors, so it mostly measures what happens on the page itself. Keep that difference in mind before comparing one store with the other: the numbers are not like for like.
Why conversion falls
A drop usually comes from one of four places. Working out which one saves a lot of wasted redesign.
1. The traffic changed, not the listing
If you started ranking for a broader search term, won a feature placement or began a new ad campaign, you gained impressions from people less likely to want your app. Total installs may rise while the rate falls. That is not a problem to fix; it is a mix change to recognise.
2. The rating or recent reviews got worse
Stars appear in search results and at the top of the listing, and the most recent reviews are often the ones people read. A buggy release that brings a run of one-star reviews can cut conversion within days, even though nothing on the listing changed.
3. Competitors improved
Search results are a comparison. If the apps shown next to you refreshed their icons and screenshots, dropped their price or gained reviews, yours now looks weaker by contrast. The App Store Audit benchmarks you against direct competitors for exactly this reason.
4. You changed something
A new icon, reordered screenshots, a price rise, a larger download, a new permission, a more demanding privacy label or a sign-up wall mentioned in the description can all put people off. The change log matters here: without one, you are guessing.
The fix, step by step
Step 1
Confirm the drop is real
Compare at least four weeks of conversion against the same length of time before the drop, not one bad day against one good day. Low-traffic apps swing wildly from day to day, so look at weekly totals. Check that the date range does not straddle a public holiday, a school term change or a feature placement that ended, and that you are reading the same metric in both periods, such as unique impressions rather than total impressions.
Step 2
Split conversion by traffic source
In App Store Connect, view App Analytics by source type: App Store Search, App Store Browse, App Referrer, Web Referrer and paid sources where shown. In the Play Console, split store listing performance by traffic source and by country. Often only one source has fallen, for example search, while browse is steady. That narrows the cause immediately and stops you redesigning parts of the listing that are still working perfectly well for other visitors.
Step 3
Find the stage that leaks
On iOS, compare impressions with product page views, and product page views with downloads. If fewer people open the page, the problem is what shows in search results: icon, name, subtitle, rating and the first screenshots. If they open it but do not install, look at the full page, the reviews, the price and the privacy details. On Google Play, compare listing visitors with acquisitions and check whether the fall is concentrated in one country or device type.
Step 4
Match the date to a change
Lay the date of the drop beside your change log, your release history, your rating history and any ad or featuring activity. Then check your top competitors in the store app on a phone, searching for your main terms, and note anything new on their listings. A drop that begins the week a rival replaces its screenshots, or the day your rating dips, points straight at the cause and tells you what to fix first.
Step 5
Fix the first thing visitors see
Work on the element that the leaking stage depends on. If search visitors are not tapping in, improve the icon, the subtitle or short description and the first two screenshots so the benefit is obvious at a glance. If page visitors are not installing, address the recent reviews, move the strongest screenshot forward and make the first lines of the description state clearly who the app is for. Change one element per round.
Step 6
Test the change with the store tools
On iOS, run a Product Page Optimization test in App Store Connect for icon, screenshot or preview changes, splitting traffic between your original and the new version. On Google Play, run a store listing experiment in the Play Console, which can also test the short and full descriptions. Let each test run until the console reports a result with enough confidence, then apply the winner and record the outcome, including tests that lost.
What people judge in the first glance
Most store visitors decide from very little. In a search result they see your icon, name, a line of text, the star rating and, on many layouts, the first screenshots or video. Improving those elements usually moves conversion more than rewriting the long description.
- Icon. It should be recognisable at small sizes, distinct from the icons next to it in search results and consistent with what the app looks like inside. Tiny text in an icon is unreadable on a phone.
- Name and subtitle or short description. A visitor should understand what the app does from these alone. A clever brand name with no descriptive line leaves them guessing.
- Rating. A low or thin rating is often the single biggest drag. See fixing low review velocity for how to ask for ratings properly.
- First screenshots. Each should show one clear benefit with a short caption, readable without zooming. The first frame carries the most weight because it is the one almost everyone sees.
- Price and in-app purchase signals. "Contains in-app purchases" or a subscription price is shown on the page. If the description hides that a subscription is needed, people who install and hit a paywall leave bad reviews, which harms conversion later.
Custom pages for different visitors
If different groups of people reach your app for different reasons, one listing cannot speak to all of them equally well. Both stores let you show tailored versions.
- Custom product pages (iOS). Alternative versions of your page with their own screenshots, app previews and promotional text, each with its own link. They are commonly used so an ad or campaign about one feature leads to a page that shows that feature first. Check App Store Connect for how many you can create and where they can appear, because Apple has extended what they can do over time.
- Custom store listings (Google Play). Alternative listings for particular countries, for users arriving through a specific link, or for other audiences the Play Console supports. They can change text as well as graphics.
Custom pages help most when you can show that one traffic source converts badly on the default page. Measure each custom page separately in the analytics so you can see whether it beats the default for its own visitors.
A worked example
Ledgerlight, a fictional invoicing app, saw conversion fall over a month. Splitting by source showed search conversion steady and web referral conversion down sharply. The date matched a new partner article that sent visitors looking for a free tool, while Ledgerlight's listing led with paid features. The listing was not broken for most visitors; one new audience was a poor match. The team created a custom page for that link that opened with the free plan, and left the default listing alone.
Testing mistakes that give false answers
- Stopping early. A variant that leads after two days often loses by the end. Let the test run until the console gives a confident result.
- Testing during a spike. A feature placement, a press mention or a big ad push changes who visits. Results from that week may not hold afterwards.
- Testing tiny differences. A slightly different shade of blue rarely produces a measurable change for an app with modest traffic. Test ideas that differ enough to matter, such as a new first screenshot message.
- Changing text on iOS during a test. Product Page Optimization tests visual assets; changing the name or subtitle in a release while the test runs muddies the result.
- Ignoring what happens after install. A variant that wins more installs but brings more one-star reviews or quicker uninstalls is not a real win. Watch retention and ratings for the period after you apply it.
The example App Store Audit shows how conversion findings sit alongside keyword, screenshot and review findings, which helps you decide whether conversion is the right problem to work on first.
1. What is a good conversion rate for an app store listing?
There is no single good figure, because typical rates differ widely by category, country, price model and traffic source. A paid app will convert far lower than a free one, and search traffic for your brand name converts much better than browse traffic. Use the peer benchmarks in App Store Connect and the Play Console, which compare you with similar apps, and track your own rate over time. Improvement against your own baseline matters more than any general number.
2. Why do my App Store and Google Play conversion rates look so different?
They are measured differently. App Store Connect's conversion rate compares downloads with impressions, which includes people who only saw the app in a search result. Google Play's store listing acquisition rate compares installs with people who opened the listing, so it leaves out everyone who scrolled past in search. The Play figure therefore usually looks higher. Compare each store with its own history and its own benchmarks rather than against each other.
3. Can a lower rating really reduce installs?
Yes. The star rating is shown in search results and at the top of the listing, so it is one of the first things people see, and many visitors also read the most recent reviews before installing. A run of poor reviews after a buggy release can reduce conversion quickly even when nothing else changed. Fixing the cause of the complaints, replying to reviewers and asking satisfied users for ratings with the official prompts is often the fastest route back.
4. Should I change my icon to improve conversion?
Only if evidence points to it, and only through a test. The icon appears in search results, on the home screen and in notifications, so a new one affects recognition for existing users as well. Use Product Page Optimization on iOS or a store listing experiment on Google Play to test a new icon against the current one on real visitors. If the test shows a clear win, apply it; if the result is flat, keep the familiar icon.
5. How long should a store listing test run?
Until the console reports a clear result, not a fixed number of days. Low-traffic apps need longer because each variant needs enough visitors for the difference to be trustworthy. Try to cover at least one full week so weekday and weekend behaviour are both included, avoid running tests across a feature placement or large ad campaign, and do not stop early because one variant leads after a couple of days. Early leads often disappear.
6. My impressions went up and my conversion rate went down. Is that bad?
Not necessarily. If you started appearing for broader search terms, got featured or began advertising, you are being shown to more people who are less likely to want the app, so the rate falls even though total installs rise. Check absolute installs alongside the rate. If installs are up, the lower rate is a sign of wider reach. If installs are flat or down while impressions climb, the new traffic is poorly matched and the listing needs attention.
7. Do custom product pages improve organic conversion?
They are designed mainly for directing specific traffic, such as an ad or a campaign link, to a page that suits it. Whether they can also appear in organic results depends on what Apple currently supports, so check App Store Connect. On Google Play, custom store listings can target countries and other audiences, which can help organic visitors in those groups. Either way, measure each custom page against the default for the same visitors before assuming it helps.
The App Store Audit checks your iOS and Google Play listings for keyword visibility, screenshot effectiveness, review velocity and rating, and conversion from impression to install, and benchmarks you against direct competitors.
Open App Store Audit Fixes →