At a weekly Meta app campaign review, the buyer may bring acquisition costs, the product team may bring activation data, and finance may bring revenue from older users. All three can be accurate while describing different cohorts. A budget decision becomes difficult when the meeting treats them as one result.
Quick take: A useful Meta app campaign quality review memo puts cost, activation and revenue at a defined cohort age on one page, states what remains unknown, and assigns one next action. Increase investment only when measurement is credible, the comparison has enough mature evidence, and acquisition cost makes sense against business value. Otherwise, name the check or bounded test that will resolve the uncertainty.
Contents: The one-page memo · Comparable evidence · Missing data and uncertainty · Illustrative memo · Next week's action

Build the memo around a decision
The memo should let a budget owner understand the recommendation without reconstructing the dashboard. Start with a decision sentence: continue within the approved limit, investigate measurement, run a specific test, reduce exposure, or propose a bounded increase. Follow it with evidence and the condition that would change the recommendation.
The Meta app advertising guide separates installs, activation and downstream value. This memo turns those checkpoints into a weekly handoff. Keep detailed diagnosis in supporting reports; bring only the evidence needed for the decision onto the page.
| Memo block | What to write |
|---|---|
| Decision and scope | Name the app, Meta account and campaign scope, OS, country, review period and proposed action. |
| Cost and volume | Show spend, installs and CPI for the stated acquisition period, with the source and comparison period. |
| Activation | Show unique activated users, eligible installs, activation rate and cost per activated user. Define the event and observation window. |
| Mature revenue | Show revenue and ROAS for cohorts that have completed the chosen observation window. Identify their acquisition dates and corresponding spend. |
| Uncertainty | State missing data, immature cohorts, small samples and changes that weaken the comparison. |
| One next action | Name the task, accountable owner, due date, spend boundary if relevant, and evidence required at the next review. |
Put report references next to the relevant figures in your working memo. Preserve the export timestamp so another analyst can reproduce the snapshot. Keep the previous recommendation visible long enough to record whether it was completed and what was learned.
Show cost, activation and mature revenue without mixing cohorts
A cheaper install is useful only in the context of what that user does afterward. If activation weakens, cost per activated user may worsen even while CPI falls. Revenue then helps determine whether activated users generate enough value to support acquisition spending.
Use two clearly labeled views when necessary: recent acquisition and activation for operational monitoring, and older cohorts for revenue evaluation. Older revenue provides context for the campaign's economics; it does not prove that newly acquired users will behave the same way.
| Check | Required definition | Memo treatment |
|---|---|---|
| Population | App, campaign scope, OS, country and acquisition dates | Keep comparison populations aligned; disclose changes in their mix. |
| Time basis | Reporting timezone, acquisition date versus event date, export cutoff | Avoid dividing this week's revenue from all users by this week's acquisition spend. |
| Attribution | Source, attribution window and click/view inclusion | Label Meta, MMP and internal business figures separately when definitions differ. |
| Activation | Selected event, unique-user counting and time allowed after install | Activation rate = unique activated users ÷ eligible installs. |
| Acquisition cost | Spend corresponding to the selected install cohort | CPI = spend ÷ installs; cost per activated user = spend ÷ unique activated users. |
| Revenue maturity | Completed observation window, revenue source, currency and gross/net treatment | Cohort ROAS = attributed cohort revenue through that age ÷ corresponding acquisition spend. |
| Sample sufficiency | Install, activation and payer counts; concentration of revenue | State whether a few users could materially change the conclusion. |
If a denominator is zero or unavailable, mark the ratio as not calculable and explain why. Do not fill the cell with zero. Also distinguish revenue maturity from profitability: completing an observation window does not establish lifetime value, and revenue ROAS does not account for every business cost.
When the overall result changes after budget shifts between markets, use a Meta app campaign country mix review to investigate the shift. Summarize its decision-relevant finding in the memo rather than reproducing the full country analysis.
Make uncertainty actionable
“Data is incomplete” does not tell a reviewer what can safely be decided. Write the missing item, the conclusion it blocks, the responsible owner and the expected resolution. Separate an unavailable event feed from a measured absence of events.
- Missing: Revenue data has not arrived for the selected cohort. Revenue quality remains unknown; the measurement owner must check the feed.
- Immature: Users have not completed the selected revenue window. Set a review date when they will be eligible.
- Sparse: Too few outcome events support a stable comparison. Report counts and explain the sensitivity to additional outcomes.
- Confounded: Creative, onboarding or delivery mix changed together. Describe the association and avoid assigning the cause to one change.
A useful confidence statement is specific: “Activation can be compared under the recorded definitions; the revenue conclusion remains pending.” This allows the team to investigate activation without presenting a full business-value verdict.
If reports disagree, make report reconciliation across platforms, MMPs and revenue the next task. The memo should retain unresolved differences rather than force the totals into apparent agreement.
An illustrative weekly decision memo
The example below demonstrates wording and ownership. It contains no observed campaign results or performance benchmarks. In a working memo, replace the evidence instructions with verified figures and report references.
Scope and recommendation
Scope: One app's Meta acquisition campaign in one country and one OS. Record the account and campaign IDs, acquisition dates, timezone, data cutoff and comparison cohort.
Recommendation: Defer the proposed budget increase while the analyst checks whether the apparent cost advantage survives an activation comparison. Review mature revenue separately before approving additional exposure.
Evidence to attach
| Evidence line | How to complete it |
|---|---|
| Cost | Insert spend, installs and calculated CPI for both acquisition periods. Identify the reporting source. |
| Activation | Insert unique activations and eligible installs at the same cohort age, then calculate activation rate and cost per activated user. |
| Revenue | Insert revenue, payer count where relevant, matching acquisition spend and ROAS for the latest fully observed cohorts. Label recent cohorts pending. |
| Limits | Record any missing feed, event-definition change or difference in campaign composition that prevents a clean comparison. |
One action and its decision rule
Action: The analyst completes the matched activation comparison before the next weekly review, using the documented event definition and observation window.
Decision rule: If the acquisition cost advantage disappears at activation, investigate the post-install journey before proposing more spend. If the advantage remains, assess mature revenue against the team's agreed economics. If measurement or sample sufficiency still blocks interpretation, return a specific unresolved item and review date.
This memo produces a defined analytical task. If the resulting evidence points to a mismatch between the ad and first use, the next memo can assign an ad-to-onboarding promise review. Keep each week's main action narrow enough to complete and evaluate.
Turn the review into next week's single action
Choose the action that resolves the most consequential uncertainty. A reporting repair, a creative test and a budget change answer different questions. Combining all three makes the next review harder to interpret.

XMP can support execution after the memo establishes what to do. Its 2026 feature update notice documents Meta recommendation adoption in April and Quick Create updates in June and July. These are campaign workflow capabilities; they do not establish that acquired users are valuable or that the memo's revenue comparison is valid.
If the chosen action requires a new campaign test, the Meta Quick Create guide explains the creation workflow. Carry the memo's scope, hypothesis and approved spending boundary into setup, then record the actual launch time and changed settings for the next review.
Before circulating the memo, run this final checklist:
- Validate measurement: Can another reviewer trace each decision-critical figure to its source and definition?
- Check maturity and sufficiency: Have cohorts completed the chosen windows, and are outcome counts adequate for the proposed decision?
- Connect cost with value: Does the interpretation include activated-user cost and observed revenue on a compatible basis?
- Choose the next action: Assign one owner, a deadline and the evidence that will determine whether to continue, revise, stop or expand.
At the next meeting, open with that action's outcome. If it remains unresolved, explain what still blocks the decision before adding another test.