Why app stores carry the installs objective
Every route to an install ends on a store listing. A paid social ad opens it, a creator's link opens it, a QR code in a shop opens it, and a person who heard about the app from a friend searches the store and lands on it. The listing is the one landing page every channel shares, and the advertiser does not control it except through what each store's console allows. That makes the stores less a channel to be funded than a conversion point to be maintained: a gain in listing conversion lowers the cost per install of every other channel without a change to any of them.
The stores are also a source of demand in their own right. The app store optimisation guide describes search as the way most installs arrive for apps that are not already famous, with browse placements earned by quality, releases and engagement. A plan that treats the store only as the end of paid journeys misses the installs that arrive with no media cost at all, and those installs often retain well because the person went looking. Earning them, in store search and on the listing, is the job of ASOImproving an app's visibility in app store search and the share of store visitors who install it..
The limit is that the stores rarely create demand. Store search captures people who already know they want an app for a job; it does little for an app that solves a problem people do not yet describe in store search terms. Store visibility also responds slowly, because ranking depends partly on install and rating history the app has to earn. A listing can be made to convert well in weeks, but climbing for a contested category term takes sustained work, and a new app in a crowded category will need paid routes to build the history the store reads.
App store tactics for app installs
| Tactic | What it does for app installs | Playbook |
|---|---|---|
| Write metadata for store search | Uses the title, subtitle, keyword fields and description to match the terms people type in the store | App store optimisation |
| Test the listing | Runs store listing experiments on icons, screenshots and copy to raise page conversion | A/B testing guide |
| Sell the first session in the screenshots | Shows the moment of value the person will reach on opening, so the install leads to activation | App store optimisation |
| Prompt for ratings at the right moment | Asks satisfied users for a rating after a success moment, within store rules | Reviews and social proof |
| Buy store search on own and category terms | Protects the app's name and tests category terms with store search ads | App install campaigns |
| Match listings to campaigns | Uses custom listings and deep links so people from an ad see the matching message and land on the right screen | Deep links and app analytics |
Write the listing for the store's search, not the web's
Store search reads only a few fields, and the stores document which ones: Apple's documentation describes the app name, subtitle and a hidden keyword field, while Google Play also indexes the full description. The tactic for an installs objective is to spend those fields on the specific phrases that describe the app's job and that the app can plausibly rank for, rather than on the broadest category word it cannot win. Put the brand in the title alongside a plain statement of the job, so that people searching the job see it in the result. Revise the fields only when keyword data shows a term underperforming, because ranking for a term is earned over time and frequent changes reset it.
Test before believing
Both stores provide listing tests, Apple through product page optimisation and Google through store listing experiments, and they are the only reliable way to know what changes conversion on a page the developer cannot instrument. Run one hypothesis per test, on the assets most people see: the icon and the first screenshots. Treat each test as a normal A/B TestControlled comparison of two variants., with enough visitors to reach a decision and the decision taken on the store's result rather than on the team's taste.
Make the screenshots promise the first session
For this objective a screenshot has two jobs. It must persuade the visitor to install, and it must describe what they will see when they open the app, because a listing that over-promises wins the install and loses the user. Lead the sequence with the activation moment: the screen where the person first gets value. A preview video that shows the interface in use does the same job in motion; the stores play previews without sound, so the opening frames have to read silently. The expectation-disconfirmation model explains the risk: users judge the first session against what the listing led them to expect.
Ask for ratings after success, not at launch
The rating appears beside the app in search results, so it works on conversion before anyone reads a review. Both stores provide a system rating prompt, and their rules prohibit incentivising ratings or filtering who is asked by how happy they seem. The lever left is timing: trigger the prompt after the activation event or a later success, never during onboarding or after an error. Reply publicly to reviews that describe a problem, because prospective users read the reply too.
Buy the store's own search, in two tiers
Apple Search Ads places ads inside the App Store, in search results and other placements its documentation lists, and Google's app campaigns include Google Play among their placements, as the Google Ads app installs playbook describes. Split store search buying into a brand tier, which protects the app's name from rivals at low cost, and a category tier, which tests whether paid visibility on job terms brings users who activate. The category tier also shows which terms convert, which feeds back into the metadata.
Send each campaign to its own listing
Both stores allow custom listings with their own address: Apple's custom product pagesA variant of an app's store page, with its own address and screenshots, built for a specific campaign, audience or feature. and Google's custom store listings. Give each major campaign theme a listing whose first screenshots repeat the ad's promise, and pair it with a deferred deep linkA link that opens a specific screen inside a mobile app rather than its home screen. so that a new user opens on the screen the ad showed. The app install campaigns guide covers how networks use those listings as destinations. The tutorial on building custom store listings for campaigns walks through choosing the themes, briefing the screenshots and reading each page against the default.
A complete plan for one such listing test, with a priority traffic source named in advance and retention as a guardrail, is set out in the app store screenshot test.
Budget posture and KPI targets
Fund listing work before store ads, because it raises the conversion of every paid install. The listing budget is mostly people and production: someone who owns keyword research and the indexed fields, design time for screenshots and previews in each market, and engineering time for the rating prompt and deep links. That work has no natural ceiling, but it has diminishing returns once the core terms rank and the first screenshots have been tested; after that, its job is maintenance and localisation.
Store search ads get a separate line with two parts. The brand tier is funded to protect the name, at whatever level keeps rivals from taking the top result for it. The category tier is the test allowance: a fixed amount for job terms, read on cost per activated user (CPACost of each conversion.) rather than cost per install. Raise the category tier only while that cost stays under the limit set by cohort payback, the period in which a cohort's margin covers what it cost, derived from the value of an activated user over that period (LTVTotal value a customer brings over time.). Money moves out of a category term when its installs activate or retain worse than organic store installs, because the ad is then buying people the listing would not otherwise have converted for good reason.
The tactics in a worked plan
Tidemark, an invented tide and weather app for small-boat sailors
Tidemark is free to install, with a paid plan for offline charts. Its activation event is saving a first home harbour. The store listing converts 19% of page views to installs, and the app ranks for its own name and little else. A paid activated user is worth about £6.40 over the six-month payback period the founders accept.
| Tactic | Before | After the quarter |
|---|---|---|
| Metadata | Title "Tidemark" only | "Tidemark: Tide Times and Marine Weather"; keyword field rebuilt around harbour and tide terms |
| Listing test | None | Screenshot set leading with a saved harbour beat the logo-led set, 24% against 19% conversion |
| Ratings | Prompt on second launch | Prompt after a harbour is saved and a forecast viewed; average rating rises from 3.9 to 4.4 |
| Store search ads | None | Brand tier £150 a month; category tier £600 a month on tide and sailing terms |
| Custom listings | One default page | A sailing-club listing used by a partner newsletter, with a deep link to harbour set-up |
At the end of the quarter, organic store installs have risen from about 2,100 to 3,400 a month. The category tier delivers activated users at £3.90 each, but two terms bring installs whose day-seven retention is half the organic level, so they are paused and their £180 moves to the brand tier in a second storefront.
The plan follows the posture: listing work first, a small and separately judged store ads line, and money moved out of terms on retention evidence rather than on install cost.
KPI set for app stores and app installs
| KPI | What it tells you | Read how often |
|---|---|---|
| Store page conversion rate (page views to installs) | Whether the listing turns visitors from every source into installs | Weekly, by traffic source |
| Organic installs from store search and browse | How much demand the store supplies without media | Weekly |
| Rank on core store keywords | Whether metadata and install history are earning visibility on the terms that describe the job | Fortnightly |
| Average rating and recent review sentiment | How the page persuades before anyone reads it, and what users complain about | Weekly |
| Day-seven retention of store installs | Whether the listing is attracting people who use the app, not just people who tap install | Weekly, per cohort |
Read conversion (CVRShare of visits or clicks that convert.) by source rather than as one figure: if paid visitors convert well below store search visitors, the ad and the listing are making different promises, which custom listings fix. The conversion rate calculator for app store listings works from the console's page views and installs. Treat the rating as a leading KPIA metric tied directly to an objective. for conversion and the review text as research for the next listing test.
When app stores are the wrong route
Store work cannot be skipped for an app, but it can be the wrong place to expect growth. If people do not search the store for the job the app does, because the category is new or the need is not one people describe in a few words, metadata and store ads will capture very little, and the budget belongs in paid social, video or creators that show the app to people who did not know to look. Store work is also the wrong lever when the listing already converts well and the problem is what happens after the install: if activation or day-seven retention is poor across every source, the fix is onboarding and the first session, and more store visibility will only buy more users who leave.
