Meta Advantage+ “on average” uplifts are not a company ROAS target
Analysis
By Isaac Turner, Measurement Editor — 2 min read
View author profile
Keep Meta’s disclosed average CPA improvement separate from selected case studies and from your own ROAS goal.
Meta’s Advantage+ explainer states that businesses using Advantage+ app campaigns saw a 7% improved cost per action on average. That is a Meta-reported product average—not a disclosed sample you can paste into a company ROAS target, and not the same object as a selected advertiser lift study. Meta Advantage+ explainer.
Separate averages, cases and targets
The same page also cites broader Advantage+ revenue-per-dollar and other product averages. The main text does not list campaign count, vertical mix, geography or study window for the 7% app-campaign figure. Selected success stories, such as Hallow’s multi-cell conversion lift, report different metrics, windows and baselines for one advertiser.
A buyer who collapses “7% on average”, “44% incremental purchases in one case” and “our ROAS goal” into one planning number mixes three claim types. Preserve which object is a Meta product average, which is a named case and which is an internal target.
Use the card in the planning deck
Our recommendation is to keep Meta’s average outside the ROAS target cell. If the footnote sample is not readable in the public page body, record sample size as missing rather than estimating an industry denominator.
Inspect the evidence
Download the source-population and comparability card. The extraction separates documented facts from our analysis and unknowns.
| Field | Evidence or limit |
|---|---|
| Report / publisher | Meta Advantage+ explained in two minutes / Meta |
| Period | Not disclosed in the public page body for the 7% app-campaign average |
| Population | Businesses that used Advantage+ app campaigns (Meta-reported); sample size not in main text |
| Metric under review | 7% improved cost per action on average for Advantage+ app campaigns |
| Aggregation | Meta-reported average across users of the product; weighting undisclosed in body |
| Critical limit | Public body does not disclose campaign count, vertical mix or geography for the 7% figure; selected cases use different metrics and cannot fill those blanks. |
| Comparable with | The same Meta product average with the same footnote definition |
| Not comparable with | A company ROAS target or an unmatched single-advertiser lift case |
Further reading in the existing archive: Blended ROAS Calculation: Where It Quietly Goes Wrong; The benchmark report is selling you something. These links provide background; this check does not independently verify their full contents.
Research checked 19 September 2026. Local draft; human editorial review and byline assignment pending.
Featured
Related posts
measurement
media buying
·1 min read
Using predicted LTV in bids: disclosure checklist for the UA team
measurement
media buying
·1 min read
Blended ROAS targets that hide channel failure in F2P portfolios
measurement
media buying
·2 min read
Web-shop LTV with VAT-inclusive prices versus store net proceeds (labelled synthetic)
measurement
media buying
·1 min read
View-through attribution windows on F2P rewarded and interstitial traffic
More from the Measurement desk
measurement
·2 min read
Airbridge adds Amazon Ads as an app measurement channel
measurement
·2 min read
When to freeze a cohort for payback review (and when not to)
measurement
·1 min read
Web-shop purchaser quality vs store IAP purchaser quality
measurement
·1 min read