Your mobile game already runs acquisition campaigns on Meta and Google. Both bring in players, but there is only enough additional budget to expand one first. The channel with the stronger overall ROAS may look like the obvious choice. Yet that average includes spend already committed; it does not show what another increment will deliver.
Quick take: Compare the additional business value associated with additional actual spend on Meta and Google, using the same game, country, operating system and cohort age. Fund a bounded next step only when the evidence meets your business target. If attribution differences or immature cohorts could reverse the decision, resolve that uncertainty before declaring a winner.
This meta google app marginal budget comparison focuses on that next spending decision. For the broader allocation framework, XMP’s mobile game budget guide explains how to balance established channels and new tests.

Define the increment before choosing the channel
A useful comparison starts with two concrete proposals: increase spending on a defined Meta acquisition scope, or increase spending on a defined Google App campaign scope. Each proposal needs a starting spend level, an affordable additional spend limit, a business outcome and a review date.
Use actual delivered spend when evaluating the result. A higher configured budget that does not produce additional spend has not tested the economics of a larger investment. Also distinguish adding budget from moving it: transferring funds from Google to Meta requires considering the value lost through the Google reduction as well as the value gained on Meta.
Choose the outcome that makes the investment worthwhile. For an app funded by purchases, that may be verified cohort purchase revenue. For an app funded by advertising, it may be cohort ad revenue. Activation can provide an earlier quality signal, but it should not silently replace the revenue or contribution target that determines affordability.
The opening review in XMP’s Meta app campaign guide makes this distinction useful in practice: installs, activation and revenue are separate checkpoints. A cheaper install only supports more budget when its downstream value also makes sense.
Match the cohorts before comparing the response
Country, OS and cohort maturity can change the meaning of a result. Comparing a mature Meta cohort in one market with a younger Google cohort in another can direct money toward the wrong opportunity. Begin with one comparable slice, then expand the analysis when there is enough evidence.
Here, cohort age means elapsed time since acquisition, not the player’s demographic age. Use the same acquisition dates across channels where practical, and measure each cohort through the same elapsed age. A calendar report of revenue received this week may include older users and cannot automatically stand in for the value of users acquired this week.
| Comparison field | What to record for Meta and Google | Decision implication |
|---|---|---|
| Acquisition scope | Same game, country, OS and definition of a new user; separate re-engagement. | Keeps different business tasks out of one ranking. |
| Time and maturity | Acquisition dates, cohort age, reporting cutoff and timezone. | Gives users equal time to generate the chosen outcome. |
| Spend | Actual spend, currency, baseline period and comparison duration. | Measures the delivered increase rather than the budget setting. |
| Business value | Event definition, revenue source, included revenue types and treatment of refunds or fees. | Prevents unlike revenue definitions from deciding the allocation. |
| Attribution | Source, windows, click/view inclusion, date basis and modeled or delayed data where applicable. | Shows which differences remain unresolved. |
| Campaign conditions | Optimization event, bidding approach, creative changes and destination changes. | Defines what the tested spending proposal actually includes. |
The channels do not need identical creative files or identically named settings. They need comparable business goals and an explicit record of how each campaign pursues them. XMP’s Google app advertising guide distinguishes acquisition from engagement workflows; keep that distinction when selecting the Google campaigns for this comparison.
Calculate what changed for each additional dollar
For each channel, compare the expanded spending scope with an explicit baseline. If you use a previous period, match its duration and cohort maturity, and record why it is a reasonable reference. A before-and-after calculation is an observed response; by itself, it does not prove that the budget change caused the entire difference.
- Calculate additional spend: actual spend in the expanded scope minus baseline spend.
- Calculate additional outcome: the selected outcome for the expanded scope minus the comparable baseline outcome, measured at the same cohort age.
- Calculate the response: additional revenue divided by additional spend, or additional spend divided by additional qualified users.
- Evaluate affordability: compare the response with your own contribution, payback or acquisition-cost requirement.
Write the revenue calculation as observed marginal revenue return = Δ cohort revenue ÷ Δ actual spend. The denominator must be positive. If spending did not increase, this calculation cannot answer the expansion question. If additional qualified users are zero or negative, a positive marginal acquisition cost is not meaningful; report the underlying change instead.
Keep average ROAS beside the calculation for context, but do not substitute it for the marginal result. A channel can retain a strong average because its existing spend performs well while the additional spend produces a weaker return.
Revenue return also differs from profit. If the numerator is gross revenue, account separately for fees, refunds and other relevant costs before deciding how much you can afford to spend. Any forecast of later value should be labeled as a forecast, with its assumptions separate from realized cohort revenue.
Example: the average winner may not deserve the next increase
Illustrative decision scenario, with no measured results: a studio is choosing between expanding Meta and Google for the same game, country and Android acquisition scope. Meta has the stronger historical average ROAS. The analyst prepares comparable baseline and expanded-spend cohorts for each channel, using one revenue definition and the same cohort age.
The review should then follow the marginal evidence. If Google’s additional spend is associated with a stronger revenue response and that response meets the studio’s business requirement, Google becomes the candidate for the next bounded increase. Meta’s historical average remains useful context, but it does not overturn the evidence about the proposed increment.
Now change one condition: Google’s apparent advantage depends on a few unusually valuable purchasers. The right next step is to assess whether that concentration could reverse the ranking. Show the purchase count and revenue concentration alongside the return; ask the analyst to assess uncertainty. A small apparent advantage with wide uncertainty is insufficient grounds for a large transfer.
If neither channel’s added spend meets the business requirement, retain the option to hold the additional budget. If one cohort is still immature, wait for the agreed observation age. Neither outcome requires naming a permanent platform winner.
Keep attributed response separate from causal lift
A budget decision becomes less reliable when Meta and Google receive credit under different measurement rules. Maintain a common analytical view where possible, while preserving each native report for delivery diagnosis. Record which source assigns users to channels and which source verifies business revenue.
Do not add platform-reported conversions together and assume they represent unique additional users. Attribution assigns credit; causal incrementality asks what would have happened without the spending change. A comparable before-and-after analysis can guide a limited test, but a stronger causal claim requires a suitable control or experiment and an assessment of uncertainty.
When reporting differences could change the allocation, use the live app advertising report reconciliation guide to structure the investigation. When creative, bids or product conditions changed alongside spend, document the limits and refer to paid UA confounding factors rather than attributing the entire result to budget.
There is also a specific product boundary to preserve. The April entry in XMP’s 2026 feature updates documents Meta incremental attribution for specified website advertising workflows. That entry does not establish equivalent support for app campaigns or a Meta-versus-Google incrementality experiment. Do not treat the feature name as validation of this comparison.

Choose a bounded action and record why
Use the comparison to authorize a specific next step, with an owner and a spending boundary. The incremental mobile UA budget decision brief is a relevant next document for recording the proposal and evidence.
- Validate measurement. Confirm that spend, acquisition events and business revenue refer to the intended scope. Investigate unresolved discrepancies that could change the choice.
- Check maturity and sample sufficiency. Wait for the chosen cohort age and reporting completion. Assess whether sparse outcomes or concentrated revenue make the ranking unstable.
- Connect cost with value. Compare each channel’s observed marginal response with your business requirement, including uncertainty and the value potentially lost if funding is transferred.
- Choose the next action. Increase one channel within the agreed limit, extend observation for a defined reason, investigate a measurement issue, or hold the additional budget. Record the review date and conditions for reconsideration.
The decision record should identify the game, market, OS, acquisition dates, cohort age, reporting sources, actual spend change, outcome change and remaining uncertainty. That makes the next Meta-versus-Google review a comparison of explicit investment proposals rather than a recurring argument over dashboard averages.