LTV: Lifetime value
The total revenue a player is expected to bring in over their whole time in a game.
Revenue earned from a campaign's players divided by what the campaign cost.
ROAS, or return on ad spend, is the revenue generated by users from an ad campaign divided by the money spent on that campaign, shown as a percentage. In mobile games it is measured by cohort day, such as D7 or D30 ROAS, because players keep earning revenue for weeks or months after they install.
ROAS tells you whether user acquisition is paying for itself. A ROAS of 100% means the players from a campaign have earned back exactly what they cost. Below 100%, you are still in the red. Above it, the campaign is profitable on that revenue basis.
ROAS = revenue from the campaign's users ÷ campaign spend × 100%
In mobile games you almost always add a time window:
DN ROAS = cumulative revenue from the cohort up to day N ÷ spend on that cohort
A studio spends $5,000 on a campaign in one week. The players it brings in generate:
| Day since install | Cumulative revenue | ROAS |
|---|---|---|
| D7 | $1,500 | $1,500 ÷ $5,000 = 30% |
| D30 | $3,500 | $3,500 ÷ $5,000 = 70% |
| D90 | $5,600 | $5,600 ÷ $5,000 = 112% |
The campaign breaks even somewhere between day 30 and day 90, and by day 90 it has returned $600 more than it cost. That point is the payback period.
You cannot wait 90 days to decide whether to keep a campaign running. So teams learn, from past cohorts, how early ROAS relates to later ROAS, and set a target for day 7.
Example. In this game's past cohorts, D90 revenue has been about 3.7 times D7 revenue. To break even by day 90, a campaign needs D7 ROAS of at least 100% ÷ 3.7 ≈ 27%. The campaign above reached 30% on day 7, so it was on track, and the D90 result confirmed it (30% × 3.7 ≈ 111%, close to the 112% actually reached).
That multiplier comes from your own data and changes by game, country, platform and channel. Recheck it every month.
There is no single industry target for D7 ROAS. Published ranges vary widely and mostly come from vendor blogs, because the right number depends on your genre, your platform, how you earn (ads or purchases) and how long you can wait to break even. The reliable method is the one above: take the ratio between your later revenue and your D7 revenue from past cohorts, then work back from the payback day you need.
Treat that ratio with care. Liftoff, a mobile ad platform, argues in Why LTV is essential for UA, and D7 ROAS should be retired that D7 revenue does not always predict long-term value. Its example is a game where the cohort with higher D7 revenue had worse retention, and the two curves crossed by day 60. A campaign that looks weaker on day 7 can pay back better. That is one more reason to read D7 ROAS next to retention and your D30 result.
Be clear about which revenue you use:
A campaign at 100% gross ROAS can still lose money once the store takes its share of purchase revenue. Many teams set targets on net revenue for that reason.
ROAS and LTV describe the same thing from two angles:
ROAS on day N = LTV on day N ÷ cost per install
If D30 LTV is $1.40 and you paid $2.00 per install (eCPI), D30 ROAS = $1.40 ÷ $2.00 = 70%.
That makes the two levers obvious: earn more per player (higher LTV), or pay less per player (lower CPI, often through better creatives with a higher IPM).
To calculate ROAS by campaign you need three things joined together: spend from each ad network, installs attributed to each campaign, and revenue from each player. An MMP usually does this for you, including ad revenue at the user level where networks report it. On iOS, much of the data arrives through SKAdNetwork in aggregated form, so iOS ROAS often relies on modelling.
See our ads and user acquisition service if you want help setting ROAS targets.
ROAS is the revenue from the players a campaign brought in, divided by what the campaign cost. In mobile games it is read by cohort day, so D7 ROAS is the revenue from a cohort in its first seven days divided by its ad spend.
Add up all revenue from players who installed in one cohort during their first seven days, including ad revenue, then divide by the spend on that cohort. If $1,500 came in from a $5,000 campaign, D7 ROAS is 30%.
It depends on your game. Work back from the day you need to break even, using the ratio of your later revenue to your D7 revenue in past cohorts. A game whose D90 revenue is 3.7 times its D7 revenue needs about 27% D7 ROAS to break even by day 90.
ROAS compares revenue with ad spend only. ROI compares profit with all costs. A campaign can have a ROAS above 100% and still lose money once store fees, development and support costs are counted.
Day N ROAS equals day N LTV divided by the cost per install. Raise LTV or lower the cost per install and ROAS goes up.
Most iOS ROAS is modelled, because SKAdNetwork gives only delayed, aggregated signals. Teams combine conversion values with their own cohort data to estimate it.
The total revenue a player is expected to bring in over their whole time in a game.
The average cost of each install, including organic installs the ads helped bring.
A service that attributes app installs and in-app events to the ads that drove them.
Tell us what you are working on. We reply with a clear next step.
Contact us