Incremental Mobile UA Budget Decision Brief: Checklist and Examples

A mobile game’s weekly UA review ends with two requests: add budget to an established campaign, or fund a first test on another channel. Both compete for the same money, but they require different evidence. Historical campaign results describe what the team has already bought; a new-channel proposal describes an opportunity it has yet to validate.

Quick take: An incremental mobile UA budget decision brief should record one proposed spending change, the business outcome it serves, the evidence supporting it, and the conditions for the next review. Separate expansion from exploration. If measurement is unreliable, resolve it first; if evidence is immature, record what would make waiting or a bounded extension useful.

Here, “incremental budget” means the next addition to spending. Proving that advertising caused additional business outcomes requires a separate incrementality measurement design; attributed revenue alone does not establish that causal effect.

Define what the next increment is meant to buy

Start with the current channel’s business job. Is it acquiring paying players within an agreed payback horizon, bringing in players who retain and generate advertising revenue, or testing whether a new audience can become valuable? “Increase installs” leaves the budget owner without enough information to judge the request.

Write the proposed change separately from the current commitment. Specify the existing budget, requested addition, currency, spending period and resulting total. State whether the money is additional funding or a transfer from another campaign. For a transfer, record which activity loses funding and why that trade-off is acceptable.

The existing mobile game UA budget guide provides the broader allocation framework: connect spend to useful player outcomes, give a new-channel test an affordable limit, and compare cohorts at a defined age. This brief turns that framework into a specific, reviewable spending decision.

Choose expansion or exploration

Expansion asks whether more spend in an established setup can still serve the business target. Bring comparable cohort results and explain why they support trying the proposed addition. A favorable historical average is useful context, but it does not guarantee the next spending level will perform similarly.

Exploration asks whether a defined channel, audience or creative hypothesis deserves further investment. Name the uncertainty and the evidence the test should produce. A test can be worth funding for learning even when it cannot yet support a scaling claim.

Keep those purposes explicit if both requests proceed. A single combined budget can obscure how much money is maintaining acquisition and how much is buying evidence.

An incremental mobile UA budget decision brief checklist

Keep the decision summary short enough to read in a budget meeting, with supporting reports attached. The following fields make the recommendation reproducible: another reviewer should be able to understand the proposal without reconstructing the analyst’s work.

Make the evidence answer the spending question

Connect acquisition cost with downstream value. A lower cost per install does not by itself justify more spend if acquired players fail to activate, retain or pay. The opening review method in XMP’s Meta app campaign guide separates those checkpoints and recommends consistent app, country, OS, attribution basis and cohort age.

For every performance figure, preserve its source and definition. Platform-attributed purchases, MMP-attributed revenue and internally verified revenue may describe different populations or accounting bases. Keep them identifiable in the brief. State whether revenue is observed or forecast, and which costs the business target includes.

Ask the analyst to explain whether the available sample can support the proposed decision. Record the number of relevant outcomes and whether a small number of high-value players dominates the result. There is no universal event count or review interval in this method. The required evidence depends on the outcome, its variability and the financial exposure.

When several inputs changed together, record that limitation and narrow the recommendation. Use the separate guide to paid UA confounding factors for that analysis; the decision brief needs the resulting limitation and its consequence for funding.

Two decision briefs for different budget requests

The following examples are illustrative planning scenarios, with no observed performance results. Replace the described evidence and limits with your own approved figures before execution.

Example: a bounded increase to an existing campaign

Request: Increase the budget of an existing Android game campaign in its current market. The business objective is to acquire additional paying players within the studio’s agreed payback requirement. Keep the proposed budget change distinct from any creative or bidding changes.

Evidence to attach: Current spend, mature acquisition cohorts, purchase and revenue definitions, and performance around previous spending changes where available. Explain how those observations support the requested addition and what remains uncertain about performance at higher spend.

Decision wording: Recommend a bounded expansion only after comparable mature cohorts support the business target and the budget owner accepts the remaining uncertainty. Record the exact addition and spending limit. Review the new cohorts at the agreed age before recommending another increase.

If evidence is missing: If the revenue feed is incomplete, defer the increase and assign the reconciliation. If measurement is sound but the newest cohorts are too young, specify the date when their outcomes can be reviewed. Waiting for existing cohorts to mature does not automatically require extra spend.

Example: a first test on a new channel

Request: Fund a test for the same game on a new channel in one market and OS. The question is whether a prepared gameplay concept can acquire players who reach the selected downstream event at economics worth investigating further.

Evidence to attach: The audience or inventory hypothesis, validated event flow, approved creative, launch requirements and a test cost the studio can absorb. State the outcome that would justify a follow-up test and the conditions that would make the result inconclusive.

Decision wording: Recommend a capped exploration allocation once launch readiness and affordability are established. Judge the test against its stated learning objective. Require comparable downstream evidence before treating it as an expansion candidate.

A platform’s entry requirement belongs in this calculation. For example, Moloco’s official Ads page, captured on November 9, 2026, lists a minimum of $300 per day for new campaigns. That is a platform minimum, not a total test budget or evidence that a test will be conclusive. A Moloco proposal must account for the planned funded duration, reporting maturity and production costs before claiming it is affordable.

Check whether the approved decision can be executed as written

A sound budget recommendation needs a clear operational handoff. Confirm that the intended action is available at the intended campaign level, and record how the operator will verify completion. Feature availability supports execution; it does not establish the business case for spending.

The October entries in XMP’s 2026 release notes document Moloco campaign editing and TikTok funding and attribution controls. Their practical relevance is specific:

These details reflect the supplied release notes last modified November 3, 2026. Confirm the controls available in the authorized account before applying the change.

If automation will execute the decision, document its scope, limits and review owner. XMP’s cross-channel automation guide describes budget boundaries and cooldown settings, with actions dependent on channel and object level. Translate the approved decision into supported controls and verify the resulting settings.

Close the review with a decision that can be revisited

At the review, append the evidence and outcome to the original brief. Preserve what the team expected before spending so that later results can improve the next decision.

1. Validate measurement. Confirm that spending, events and revenue definitions are reliable enough for this decision. Assign unresolved discrepancies.
2. Check maturity and sample sufficiency. Determine whether the selected cohorts have reached the intended age and whether the observed outcomes support a conclusion. Separate waiting for reports from funding more acquisition.
3. Connect cost with business value. Compare the evidence with the agreed economics, including the costs and revenue basis stated in the brief. Label forecasts and remaining uncertainty.
4. Choose the next action. Expand within a new approved limit, continue within the existing allocation, authorize a justified extension, stop the test, or investigate a named problem. Record the owner and next review date.

A useful final entry states the action, the evidence that supports it, the uncertainty that remains, and what would change the decision. That gives the next budget meeting a clear starting point.

Qu Jun Xing

AdOps & Growth Notes

Ad Ops AI & SaaS Automation

10+ years in mobile growth and AdTech operations. I build practical systems across AdOps, automation, SEO/SEM, GEO, and lifecycle marketing.

in LinkedIn 🗂️ More notes ⚡ Request an XMP Trial

Questions or updates? Reach out on LinkedIn or use the “Give feedback about this article” button.