Cohort ROAS vs Blended ROAS: Mobile Game Budget Decisions
Learn which ROAS view should control a mobile game budget, with a cohort example and a practical daily decision rule.
A mobile game budget should move when the installs bought by each campaign clear a defined payback target, not when total revenue makes the account look healthy. Cohort ROAS shows whether the new players bought this week are paying back. Blended ROAS shows the overall business picture, including older cohorts and organic revenue.
Both views matter. They answer different questions. This comparison uses a sample puzzle game called Orbit Tiles, made for this article, to show which number should control a daily budget decision.
Cohort ROAS vs blended ROAS measure different money
Cohort ROAS compares revenue from one install group with the spend that acquired that same group. If a network brought 1,000 players on Monday, its D7 cohort ROAS uses only those players’ first seven days of revenue and Monday’s spend. The formula is attributed cohort revenue divided by cohort spend.
Blended ROAS compares all measured revenue in a period with all acquisition spend in that period. It can include revenue from players acquired last month, subscribers renewing today, organic players, and revenue from several campaigns. The formula is total period revenue divided by total period spend.
The difference matters because a mature game carries revenue from older cohorts. That revenue can make blended ROAS look strong while a new campaign buys players who will not pay back. The reverse can also happen during a launch, when a promising new cohort has not had enough time to earn its later revenue.
For campaign optimization, Google Ads recommends tracking more than the final purchase, so its models can use the actions that lead to value. A budget review needs the same discipline: keep the event definition and the revenue window consistent before comparing campaigns.
A mobile game budget can look safe in blended ROAS and fail by cohort
Orbit Tiles has a D30 payback target of 100 percent net of its own operating costs. Its team reviews a seven-day signal before moving spend, then checks the same cohort again at D14 and D30. The table below is a sample made for this article. Each row represents players acquired in the same week.
| Campaign | Spend | Installs | D7 revenue | D7 cohort ROAS | Action |
|---|---|---|---|---|---|
| Network A | $4,000 | 2,000 | $3,600 | 90% | Hold |
| Network B | $3,000 | 1,500 | $3,450 | 115% | Scale carefully |
| Network C | $3,000 | 2,500 | $1,500 | 50% | Cut |
The campaign account spent $10,000 and the new cohorts returned $8,550 by D7. Its cohort ROAS is 85.5 percent. That result does not automatically require a pause. The target is D30, and Network A may still land on target. Network C needs attention because it trails the other two at the same age.
Now add $7,500 of revenue from earlier cohorts and organic players that arrived during the same seven days. Blended revenue becomes $16,050. Blended ROAS becomes 160.5 percent. The business looks profitable, but that does not make Network C a good place for the next dollar. The older revenue did not come from Network C’s new players.
This is why a mobile game budget needs a cohort-level rule. A blended number can support the cash forecast. It cannot identify which current campaign deserves more spend.
Cohort ROAS decides the campaign budget, blended ROAS decides the business guardrail
Use cohort ROAS when the question is local and forward-looking: should a network, geo, creative, or campaign get another budget increase? Compare cohorts at the same age. A D7 result should be compared with another D7 result, not with a D30 total from a previous month.
Use blended ROAS when the question is broad: can the game afford its planned acquisition spend this month? It helps connect UA spending with total cash generation. It also surfaces whether organic growth, renewals, ad revenue, and older purchase cohorts are supporting the business.
| Question | Better metric | Reason |
|---|---|---|
| Should this creative get more spend? | Cohort ROAS | It isolates the installs reached by that creative. |
| Should this geo stay in the test plan? | Cohort ROAS | It compares that geo at the same age and payback window. |
| Can the title fund the month's UA plan? | Blended ROAS | It includes the revenue base that pays the bills. |
| Did a budget expansion weaken current acquisition? | Cohort ROAS | It exposes the marginal cohort after the change. |
Don’t treat blended ROAS as an excuse to keep a weak campaign alive. Older cohorts can carry the total for weeks. A campaign should earn its own next budget increase with installs and revenue that belong to it.
A mobile game budget workflow starts with a fixed payback rule
Set the payback window before looking at performance. A casual game might use D30. A game with slower purchase behavior may need a later window. The right window matches the title’s revenue curve and the time the business can wait for recovery. Keep the target net of the costs that matter to the decision.
- Set a cohort target for each checkpoint. For example, use a D7 signal that predicts a D30 target, then verify the cohort at D14 and D30.
- Split reports by network, geo, campaign, and creative. A campaign total can hide one strong creative and several weak ones.
- Keep a testing reserve. A small fixed share of the mobile game budget can buy evidence from new creatives or geos without disturbing proven spend.
- Increase a winner in steps. Check whether cost per install and cohort quality hold after each increase.
- Cut losers based on the agreed checkpoint, not on an attractive blended dashboard.
A team also needs clean event inputs. Google Ads says app conversion tracking can use Google Analytics 4, server-to-server tracking, third-party analytics, or codeless Google Play tracking for Android. The choice matters less than a stable definition of the valuable actions and a consistent way to connect revenue back to the acquisition cohort.
For a fuller view of the math behind cohort reporting, see this cohort ROAS worked example. Budget changes also need a payback threshold, which the mobile game payback example walks through. The User Acquisition category collects related campaign and budgeting guidance.
A mobile game budget should protect learning and demand proof
Blended ROAS answers whether the game is generating enough revenue overall. Cohort ROAS answers whether the next batch of installs is worth buying. Keep both on the dashboard, but let the cohort target decide campaign-level budget moves. That protects the budget from the comforting effect of revenue earned by yesterday’s winners.
Clean attribution makes this workflow easier because every install can be read against the campaign that paid for it. Roasit measures cohort revenue, retention, and ROAS by campaign so a team can compare each new budget decision on the same basis.
Read Unity's mobile game user acquisition guide for a broader explanation of CPI, LTV, retention, and payback. For conversion data that can support campaign optimization, review Google Ads guidance on app conversion tracking.
