Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Marketing Frameworks › RACE: Reach, Act, Convert, Engage

RACE for App Installs

RACE planning for app installs: reach through store search and paid placements, act on the store page, convert to an activated install, engage via messaging.
Objective guideintermediate8 min readUpdated

Why a website-centred RACE plan does not fit an app

The standard RACE plan assumes that people reached by marketing arrive on the company's website, act there, convert there and are then engaged by email. Every stage happens on owned property and is measured by one analytics tool. An app breaks the chain twice. Between Reach and Convert sits an app store with its own rules for listings, its own ranking and its own reporting. And after the install, the relationship lives inside the app, where messaging needs permission and campaign context is lost unless something carries it across.

Measurement breaks too. Privacy frameworks on mobile platforms aggregate or delay campaign data on part of the traffic, so a stage KPI that a website plan would count exactly becomes an estimate. A plan that ignores this ends up promising stage targets nobody can verify. The app marketing hub lays out the channels; the RACE plan has to decide which stage each one serves and how each stage will be judged.

Decisions that change for app installs

StageGeneric RACERACE for app installsDecision it forces
ReachPaid, owned and earned media driving site visitsStore search and browse, paid install campaigns, web-to-app routesHow the budget splits between store visibility and paid placements
ActEngaged visits, leads, sign-ups on the siteProduct-page views and page conversion on the store listingWho owns the listing and what can be tested on it
ConvertSales or sign-upsAn activated install, with campaign context carried in by deep linksWhich first-use event defines conversion
EngageEmail, loyalty, repeat purchasePush and in-app messaging, limited by opt-inHow permission is earned before engagement is planned
KPIsCounted in site analyticsPartly aggregated or modelled under platform privacy rulesWhich targets are firm and which are ranges

The web-to-app routes in the Reach row are planned in the guide to web-to-app journeys, which decides which customers to move and measures each route against the web visit it interrupts.

Move Act onto the store page

On the web, Act is a visit that does something: reads, compares, signs up. For an app, the equivalent is the store listing. Its screenshots, preview video, rating, reviews and description decide whether a visitor installs, and they are shaped within the store's own guidelines. Plan this stage as a set of listing changes with an owner, a test plan and a KPI of product-page conversion by traffic source. The app store optimisation guide covers the levers; the planning decision is to give the listing its own column budget and owner rather than treating it as an afterthought to paid media.

Define Convert as an activated install

An install that is never opened has converted nobody. Set the Convert stage at the first meaningful use, the event that shows the person started to get value, and treat raw installs as the bridge between Act and Convert. Deep links matter here: a person who tapped an advert for a specific offer should land on that offer after install, not on a generic welcome screen, and the link carries the campaign's context into the app so that Convert can be measured by source. Deferred deep linking, covered in the deep links and app analytics guide, is what makes that possible for new installs.

Plan Engage around permission

Push and in-app messages are the app's equivalent of email, but they only reach people who granted permission, and the prompt can usually be shown only sparingly. That makes the opt-in rate the first Engage KPI, ahead of any message performance figure. Plan when to ask, after the person has seen enough value to say yes, and what the messages will do once allowed. The push notifications and in-app messaging guide covers timing and frequency. Paid Remarketing to lapsed users is the fallback for people who declined, and it belongs in the Engage budget, not Reach.

Split Reach three ways

Reach for an app has three distinct routes. Store search and browse are earned through relevance, ratings and ranking. Paid install campaigns on search, social and video networks buy placements; the app install campaigns guide explains their optimisation choices. Web-to-app routes, such as banners on the mobile site or links in emails, send people who already know the brand. The three interact: paid volume can lift store ranking, and web-to-app visitors convert differently from strangers. Give each route its own line and KPI, and judge paid campaigns on cost per activated install rather than cost per install (CPA).

Accept that some stage KPIs are estimates

Reach and paid installs on privacy-restricted traffic are reported in aggregate and with delay, so their stage KPIs are ranges rather than counts. Store consoles count listing views and installs directly, and the app's own analytics count activation and engagement. Write the plan's targets accordingly: firm targets for counted stages, directional ones for modelled stages, and an Attribution approach agreed before the quarter starts so that nobody changes the method mid-plan.

Decision points in a worked RACE plan for app installs

Illustrative example — not a real result

An invented fitness-class booking app, Studiohop, writes a quarterly RACE plan around a store relaunch

Studiohop lets people book classes at independent gyms in four cities. For the autumn quarter it relaunches its store listing with new screenshots, a preview video and a prompt asking satisfied users for a rating. The quarter's objective is 9,000 activated installs, defined as a first class booked within 7 days of install, at no more than £12 per activated install on paid routes.

StageObjectiveKPIMain channelsOwnerBudget
Reach400,000 store impressions; 40% of installs from store search and browseImpressions by source (store console); paid reach as a rangePaid social and search install campaigns, web banner, gym partner posters with QR codesGrowth marketing£54,000
ActLift product-page conversion from 28% to 34%Page conversion by source (store console)New screenshots and preview video, rating prompt, store listing testsStore optimisation£6,000
Convert9,000 activated installs from about 22,000 installsFirst booking within 7 days by source (app analytics)Deferred deep links to the advertised class, first-class creditProduct and growth£8,000 in credits
Engage45% push opt-in; 30% of activated users book again within 30 daysOpt-in rate, second-booking rate (app analytics)Permission prompt after first booking, class reminders, lapsed-user remarketingLifecycle£4,000

The arithmetic is checked before the plan is signed. Paid routes are expected to deliver 13,200 of the 22,000 installs and 5,000 activated installs, so £54,000 of Reach spend gives £10.80 per activated paid install, inside the ceiling. The relaunch carries a risk: if page conversion stays at 28%, the same impressions produce about 18,000 installs and roughly 7,400 activated users, short of target. That scenario sets the trigger: if page conversion is below 31% after 3 weeks, the listing test is reverted and £5,000 moves from paid social to search campaigns.

The plan shows each adaptation earning its column. Act has its own owner and budget because the relaunch is the quarter's main bet. Convert is defined by booking, not download, so the cost ceiling sits on the right number. Engage starts with opt-in, without which reminders reach nobody. And Reach carries a range, not a point target, for the paid portion the platforms report in aggregate.

Measuring a RACE plan for app installs: KPIs and cadence

Weekly: store impressions and product-page conversion by source, paid spend and installs, and activation rate by source, since listing tests and campaign changes show within days. Fortnightly: cost per activated install on each paid route, with the caveat that privacy-restricted figures settle late. Monthly: push opt-in, second-use rate and lapsed-user recovery for the Engage stage. Quarterly: the full plan against objectives, with Reach reviewed as a range. The store consoles, the measurement partner and the app's own analytics each own part of the picture; the plan should name the source of every KPI so that a disagreement between tools is not mistaken for a change in performance.

Where RACE misleads for app installs

The stages imply a sequence, but app growth often runs in loops: engaged users rate the app, ratings lift store conversion and ranking, and ranking brings more installs. The growth loops framework describes that better than four columns. Store-side changes outside the team's control, a new listing rule, a ranking change or a featuring, can swing Act and Reach with no change in the plan. Modelled data makes paid stage results look more precise than they are. And RACE's Engage column is thin for an app whose value depends on habit; the AARRR framework gives more structure to the stages after install.

Common mistakes

  • Convert set at the install. The plan hits target with people who never open the app.
  • No owner for the store listing. Act becomes whatever the paid team's creative happens to imply.
  • Engagement planned before permission. Reminders budgeted for an audience that never opted in.
  • Paid reach given a precise target. Aggregated figures cannot confirm a point estimate.
  • Deep links missing from campaigns. New users land on a welcome screen instead of the offer they tapped.
  • Lapsed-user remarketing booked under Reach. Re-engaging existing users is Engage work with its own measure.

Frequently asked questions

What is the Act stage in a RACE plan for an app?

The visit to the store listing: reading the description, looking at screenshots and the preview video, checking ratings. It is the first step the prospective user takes, and it happens on a page the store governs. The plan's Act objective is usually product-page conversion, and its owner is whoever runs app store optimisation.

Should Convert in an app RACE plan be the install or something later?

Something later. An install that is never opened has converted nobody. Define Convert as an activated install, the first booking, first workout or first saved item, so that the stage measures a person who started to use the app. Install counts remain a supporting measure between Act and Convert.

Why does opt-in matter so much for the Engage stage?

Because push and much in-app messaging only reach people who agreed to receive them. The size of the audience the Engage stage can work with is set by the permission rate, so a plan that budgets for re-engagement campaigns without a plan for earning permission is budgeting for messages few people will see.

Terms used on this page

Tools to try

Frameworks

Where this page is used

Also related

Sources

  1. App Store — Apple Developer
  2. Firebase documentation — Google

Related