ROAS targets versus payback windows

A UA team walks into a quarterly review with a D7 ROAS target they hit. Finance walks in with a cash position that says the studio spent more this quarter than it recovered. Both numbers are correct. The two sides are measuring different things, and the argument that follows is rarely about arithmetic; it is about which number should have governed the decision in the first place.

Two different questions

A ROAS target answers a percentage question: for every pound spent, how much revenue came back within a defined window. It's a ratio. Because it stays comparable across campaigns and channels whatever the scale, UA teams like it as an operating metric and reach for it first. A payback window answers a cash question instead: how long until the spend actually comes back in real money. That's a duration, and it decides whether a studio can keep spending at the current rate without going outside for financing.

The two diverge sharply whenever the revenue curve is long-tailed, which describes most successful mobile games. A campaign can post a strong D7 ROAS off a fast-monetising minority of players while the majority pay back over months, so the ratio target lands early and the cash does not. Finance, watching the studio's bank balance rather than a dashboard percentage, reasonably asks why a good quarter still shows negative net cash from acquisition.

Why blended makes this worse

Blended ROAS folds organic installs into the denominator alongside paid ones, which pushes the two conversations further apart. A UA team reporting blended ROAS is often reporting a number inflated by organic uplift the paid spend did not directly cause, and Blended ROAS calculation covered how easily that inflation goes unnoticed inside the number itself. Put that figure into a cash-focused review and finance sees a ratio that already overstates paid performance, sitting on top of the ratio-versus-duration mismatch described above. Target comfortably hit on paper. Cash payback quietly extending underneath it.

Setting a target that survives a CFO review

Neither metric is wrong, and both belong on the report; the mistake is letting one of them settle a question it cannot settle.

ROAS windows are the right tool for day-to-day campaign optimisation and channel comparison, because they normalise for scale and let a buyer put a small test campaign next to a large established one on equal footing. Payback windows belong in the capital allocation conversation. That is what finance actually needs answered: how long the studio's cash sits tied up before this spend returns.

A target that survives review states both numbers and ties them together: a D7 ROAS floor for tactical decisions, paired with a stated maximum acceptable payback period that reflects the studio's actual cash position and risk appetite rather than an industry benchmark borrowed from a different business model. A studio with strong reserves can rationally accept a twelve-month payback window in exchange for scale. A studio managing cash tightly cannot, however good the ROAS ratio looks on the same spend.

Consider two campaigns with an identical D7 ROAS of 35 percent. The first is a casual game where most revenue arrives through ads within the first fortnight, so the D7 figure works as a fair proxy for the eventual payback timeline. The second is a mid-core RPG where the bulk of revenue lands from a small cohort of payers over four to six months, which puts the payback period several times further out on the same ratio. On ROAS alone the pair look equivalent. Report the payback window beside the ratio and the gap in cash risk shows up immediately, with no separate meeting needed to explain it.

The conversation that actually needs to happen

Bring finance into the payback window decision rather than defending a ROAS number that never set out to answer the cash question. Ask what payback period the business can sustain given its runway and growth targets. Make that the binding constraint, then let ROAS targets work underneath it as the day-to-day optimisation lever.

Put the two numbers side by side, say plainly which one binds, and the review stops being an argument about which metric is right; it turns into a conversation about whether the current spend rate fits the studio's actual financial position, which is the question both sides were trying to answer all along.

Related archive reading

These articles provide related context and remain subject to their stated review status.

• UA and product teams optimise against each other
• The CFO conversation every UA lead has