Blended ROAS / MER: the scoreboard number when attribution can't be trusted

Blended ROAS, also called MER (Marketing Efficiency Ratio), is total revenue divided by total marketing spend across every channel, not just one platform. $12,000 spent across Meta, Google, and email that produced $53,800 in revenue is a 4.48x blended number, regardless of what each individual platform claims to have driven.

Why the same account can show conflicting numbers

Channel-level ROAS is attributed by that channel’s own model, and channels routinely claim overlapping credit for the same customer journey: someone clicks a Meta ad, opens a follow-up email, then converts through a Google search for the brand name. Each platform reports that sale as its own. Blended ROAS sidesteps the double-counting entirely by comparing what actually left the bank account against what actually came in, independent of which platform gets to claim it.

Why this became the standard after iOS tracking changes

Apple’s App Tracking Transparency prompt meant a large share of users opted out of cross-app tracking, and platform-reported ROAS dropped in response, not because performance changed, but because visibility into conversions did. Cutting budget based on a platform ROAS drop that’s really an attribution gap is a common and avoidable mistake. Blended ROAS doesn’t depend on knowing which ad caused which sale, it only needs total spend and total revenue, both of which are unaffected by what any single platform can or can’t see.

Where it’s easy to misread

A high channel ROAS can coexist with a flat blended number. Retargeting reliably reports strong ROAS because it targets people who were already close to buying. Shifting budget toward it because the reported number looks better can shrink the pool of new customers retargeting depends on, and the blended number falls over the following weeks as that pool dries up.

It’s a portfolio signal, not a channel-level one. A drop in blended ROAS says the whole system needs a look; it doesn’t say which channel to cut. Reading it as “kill whichever platform reports worst” skips the step of checking whether that platform is actually driving the new-customer volume the rest of the funnel depends on.

Seasonal spend swings move it without changing anything structural. A Black Friday spike in blended ROAS reflects the season, not a channel mix worth replicating in February. Comparing year-over-year holds up better than comparing month-to-month.

How this relates to attribution and effective windows

Blended ROAS is, in a sense, what attribution models and effective windows are trying to approximate at the channel level: crediting a conversion to the touchpoint that actually drove it, over the period that actually matters for the funnel. Reading both together, the incremental, windowed model at the ad level, and the blended total at the account level, covers the two questions attribution alone can’t fully answer: which ad drove this, and is the whole operation actually working.

How YieldBI applies this

Growth Controls report ad-level performance using your configured attribution model rather than a single platform default. That keeps the ad-level numbers you’re acting on daily closer to the blended, whole-picture number than a same-day, single-touch attribution model would ever get on its own.