Measurement & attribution

Beyond Blended ROAS: The KPIs and Budget Model for Real Growth

Blended ROAS gets worse as a decision-making metric the bigger your account gets. It still belongs in the report. It stops belonging in the decision.

May 14, 2026 7 min read Andrew Clay

A blended ROAS of 10:1 looks clean on a dashboard. Pull it apart and you will usually find a large share of it is retargeting revenue — customers who were going to buy anyway.

That is the core problem with blended ROAS: it becomes a worse decision-making metric the bigger your account gets, precisely because a bigger account has a bigger warm pool inflating the number.

The KPIs that should drive decisions above $3K/day

Once Meta spend passes roughly $3K/day, three metrics belong in front of the blended number:

  • New-customer ROAS, measured against LTV through a multi-touch model
  • New-visit percentage — what share of traffic has never been to the site
  • First-time revenue versus retention revenue, reported separately rather than summed

The reason to separate them is not reporting hygiene. It is that KPI targets should be completely different for new versus returning customers. A 2:1 return on a first-time buyer with strong repeat behavior is a good trade. The same 2:1 on a returning customer may be worthless.

Blended ROAS still gets reported. It just stops being the number that drives operating decisions.

The exclusion leak nobody checks

Most large DTC operators we audit have a customer match-rate problem on Meta. On some accounts we have seen as little as a 75% match when uploading 100% of the customer list.

That gap matters more than it sounds. It means a quarter of the customers you believe you excluded are still eligible to see your prospecting ads — so some portion of what you are reading as new-customer acquisition is existing buyers, inflating the ROAS of a campaign you think is pure prospecting.

Before trusting any new-customer metric, verify what your match rate actually is. We built the customer-cohort and match-rate views in AdSignl specifically to pull this apart at account level.

Budget pacing should follow opportunity, not the calendar

Rigid daily budgets feel safe and predictable. What they actually do is constrain campaigns that are working and keep spending on ones that are not.

Adaptive pacing does better:

  • Let budgets flex with demand — sales cycles, seasonality, algorithm learning phases
  • Manage to weekly or monthly spend targets rather than rigid daily caps
  • Give winning campaigns room instead of cutting them off early

Pacing should follow opportunity. At enterprise volume this needs guardrails, because Meta's own weekly pacing will over-deliver against a stated daily budget — the mechanics of that are in the operating system behind $1M+/month accounts.

Reach is the growth input people under-fund

Marketers have obsessed over ROAS for a decade. Incremental reach is the thing that actually determines the ceiling, because reach is what fills the retargeting pool. Without it, even highly efficient ads run out of people to convert.

The metrics that make reach legible:

  • First-time impressions
  • Incremental reach per dollar spent
  • Quality click percentage — landing page views over link clicks, not click-through rate

It is a shift from asking how profitable a click was to asking how many new people you actually reached.

Running top-of-funnel on under $150K/month

Most brands avoid top-of-funnel because it does not make money in Ads Manager. That is a mistake — the goal is not TOF profitability in-platform, it is stronger blended numbers. Here is how we run it on smaller budgets.

1. Measure the right two things. Formal lift tests are not realistic at this level. Track first-time impression rate — how often you are reaching new people — and blended MER, total revenue divided by total ad spend. If your 7-day FTIR stays above 50% and blended MER improves week over week, the campaign is working. In-platform ROAS will look bad. That is not the point.

2. Optimize for the right event. You do not always need Purchase. Test add-to-cart optimization, which suits most ecommerce, and branded search inquiry — page views plus branded-search UTM traffic from Google. Run each about a month and compare which lifts blended MER more.

3. Tighten targeting rather than going fully broad. Because TOF is not driving direct sales, broad delivery wastes it. Take your top-spending 10-year age range from the last 30 days as the base audience, then layer gender, lookalikes, or interests. You are feeding quality signals, not just reach.

4. Exclude everyone who already knows you. TOF should only hit fresh eyes. Exclude 180-day pixel audiences — site visitors, add-to-carts, purchasers, engagers, 25%+ video viewers — and your full email list, not only buyers. Test Meta's incremental attribution; if you are on standard attribution, use 7-day click and exclude view-through.

5. Use complementary creative. This is where most brands go wrong: they run their purchase ads at the top of the funnel. Better options are old winners that still engage but no longer scale, new concepts that performed well without converting directly, whitelisted creator ads, and advertorial content. TOF creative should create attention and curiosity, not close.

What works: mixing old winners with near-winners, using post IDs from high-engagement organic, committing 5–10% of budget for at least three weeks before judging, and watching FTIR alongside blended MER.

What does not: killing TOF because in-platform ROAS looks bad, over-broad targeting with no exclusions, running identical creative themes across every campaign, and switching objectives before you have enough data.

TOF is not about making money on day one. It is about keeping the ecosystem healthy — lower blended CAC, a fuller remarketing pool, and a first-time impression rate that stays high enough to keep scaling.

When the platform goes sideways, fly the plane

One operating discipline is worth as much as any metric: when Meta becomes unstable, do not start changing variables to match the chaos.

Backend instability is routine — bugs, UI problems, delivery anomalies. When you stack operator-side changes on top of it (new tests, new structures, panic budget pulls) you produce mixed signals that make the account genuinely worse rather than merely noisy.

Stay consistent on the operator side and let the algorithm side settle. Tighten budgets if you must, hold your structure, trust your creative, and accept an ugly stretch. Then push spend back up and restart testing. When you are hunting for a cause, eliminate one variable at a time.

Operators who get this wrong are usually not making a skill mistake. They are making a context mistake. If you have only ever managed one account, every dip looks like the worst dip you have seen, because you have no baseline separating a real anomaly from a Tuesday. So you react to noise, because noise is all that is visible.

That is an argument for continuity over coverage. Most agencies give media buyers 10 to 15 accounts. We keep it to a handful and keep the same senior buyer on an account for the life of the relationship, not the first 90 days. The value is not the SOPs they ran on day one — it is the months of context watching that specific account behave across different conditions. That context is what lets someone sit still while the dashboard panics.

Pilots do not panic when the instruments get noisy. They fly the plane.

Where to start

  1. Split first-time from returning revenue in your reporting. Nothing else works until this exists.
  2. Check your customer match rate. If it is well under 100%, your prospecting numbers are contaminated.
  3. Set separate KPI targets for new versus returning customers.
  4. Move to weekly or monthly spend targets with hard caps rather than rigid daily budgets.
  5. Fund TOF at 5–10% and judge it on FTIR and blended MER over three weeks, not on in-platform ROAS.

FAQ

Why is blended ROAS a bad metric for large accounts?

Because it improves as your warm audience grows, independent of whether acquisition is working. A 10:1 blended ROAS often contains a large share of retargeting revenue from customers who would have purchased anyway. The bigger the account, the more the returning-customer pool inflates the number — so the metric gets less diagnostic exactly as the stakes rise.

What KPIs should replace ROAS above $3K/day in spend?

New-customer ROAS measured against LTV through a multi-touch model, new-visit percentage, and first-time revenue reported separately from retention revenue. The point is to set different targets for new versus returning customers, since the same nominal return means very different things depending on which you acquired.

What is a good first-time impression rate for top-of-funnel?

We look for 7-day FTIR above 50% on accounts under $150K/month, paired with a blended MER that improves week over week. Those two together indicate a healthy top-of-funnel campaign even when in-platform ROAS looks poor, which it usually will.

Why does my Meta customer list only partially match?

Match rates depend on the identifiers Meta can resolve against accounts, and they are rarely complete. We have seen accounts match as little as 75% of a fully uploaded customer list. The consequence is that suppression audiences leak: some existing customers remain eligible for prospecting delivery, which inflates the apparent performance of campaigns you believe are reaching only new people.

What should you do when Meta performance drops suddenly?

Hold your structure and change one variable at a time. Platform instability is common, and stacking operator-side changes on top of it destroys the signal you need to diagnose the problem. Tighten budgets if necessary, keep creative and structure consistent, let delivery settle, then resume testing. Reacting to every dip is the most common way accounts get worse during a rough stretch.

Originally published in Beyond ROAS · adapted from 3 issues. Get it weekly →

If you cannot separate new-customer performance from returning revenue in your account today, that is the first thing worth fixing. We do it as a matter of course.

Talk to an operator → Get the newsletter
← All resources