Beyond the install: optimizing mobile campaigns for day-7 value
Installs are the easiest mobile metric to buy and the weakest predictor of revenue. How to move optimization toward early value signals.
Installs are the most visible number in a mobile campaign and the least reliable predictor of whether it will make money. Two sources can deliver the same installs at the same price and produce completely different revenue a month later.
Why the install is a weak signal
An install says that someone downloaded the app. It says nothing about whether they registered, returned the next day, or ever paid. Optimizing purely for install volume tends to find the users who install most easily — not the ones who stay.
Find an early value event
The goal is an in-app event that:
- happens within the first few days
- correlates with long-term value (retention, purchases, subscriptions)
- is hard to fake
Examples include completing onboarding, making a first transaction, finishing a first lesson or level, or adding a payment method. Look at your own cohorts: which early events best separate users who are still active on day 30 from those who are not?
Measure by cohort, not by day
Group users by install date and source, then follow each cohort forward. Useful views include:
| Metric | What it tells you |
|---|---|
| D1 / D7 retention | Whether users come back at all |
| Event rate by D3 | Whether users reach the value event |
| Revenue by D7 | Early monetization per source |
| ROAS D7 | Early return on spend per source |
Move sources up the funnel
Once you know which sources produce users who reach the value event, you can:
- keep paying CPI on proven sources while monitoring post-install quality,
- offer those sources a CPA on the value event,
- pause sources whose installs never reach it.
Read the app install campaigns guide or see app growth with UniconAds.
New writing, when there is some
Guides and analysis on performance marketing. No more than one email a month, and never a partner's list.
Unsubscribe in one click, any time. See the privacy policy.