Why yesterday’s ROAS lies (and when to trust it)

· marketer who learned this the expensive way📊 with a live slider, not a lecture

Published September 10, 2026

The 60-second version

  • Monday’s number moved by Thursday because buyers take days to decide — the dashboard counted Day-1 buyers as if they were all buyers.
  • Fresh numbers always under-read. Roughly half the purchases arrive after Day 1 for a typical store.
  • The fix: use fresh numbers for pacing (“are we spending on plan?”) and 7-day-old numbers for decisions (“scale or kill?”).
bottom line: never fire a campaign that’s one day old

On Monday morning your dashboard says last week's ROAS was 2.1x, and the growth chat is drafting uncomfortable questions. By Thursday the same week reads 3.4x and nobody changed anything — no new creative, no budget shift, no optimisation. The week did not improve. It grew up.

Every conversion number you read in the first few days after spending money is incomplete because buyers take time to purchase. Someone clicks an ad on Monday, thinks, compares prices, and buys on Friday. The ad platform then credits that purchase back to Monday's clicks. This delay is conversion lag. Until that delay plays out, yesterday's ROAS is half a measurement wearing the costume of a finished number.


The Monday mystery

A lag curve answers one simple question: of all the sales a day's clicks will eventually produce, what percentage has arrived by day N? The curve starts low, climbs quickly over the first few days, and then flattens out.

LIVE · DRAG ITHow old is this number?
1.7xtoo young to judge ✎
DAY 01 · 50% OF BUYERS ARRIVED
Day 0 · todayDay 7 · matureDay 14 · final

Day 1: only 50% of buyers have arrived. The dashboard shows a fraction of the final number and calls it ROAS. It isn’t lying — it’s early.

curve verifiedtypical mid-AOV store · measure your own once, reuse forever

Higher order values stretch this curve out — a ₹25,000 furniture order might see less than 30% arrive on day 1, while a ₹499 impulse buy could be 70% complete on day 1.

Look at this from the buyer's perspective: same-day purchasers are the minority. Most people need days — salary cycles, a second opinion, or waiting for a weekend. When a dashboard reports Monday's ROAS on Tuesday morning, it reports the impatient slice of your buyers as if they were the entire group.

The early-read trap: early reads always make performance look worse than it is. Every panic about "ROAS collapsed yesterday" comes from the exact same mistake: you compared full ad spend against a half-arrived group of buyers. Ad spend registers instantly; revenue trickles in over weeks.


Why fresh numbers lie

Three boring delays stack on top of each other. All three fix themselves if you wait:

People take time

Most buyers don’t purchase the day they click — payday, comparisons, a second conversation. Nothing can count a purchase before the human makes it.

Data takes time to travel

After the purchase, the event hops from pixel to platform — sometimes in batches days late (iPhones are slowest). The dashboard can’t show what hasn’t arrived.

History gets rewritten

Platforms quietly update the past as late purchases land. Monday’s number on Tuesday and on Friday are two different photos of the same week.

And here’s the kicker: the error always points the same way — down. Spend is booked instantly; revenue strolls in over days. So every “ROAS collapsed!” alarm on a fresh cohort is the same artefact: you measured half the buyers against all of the spend.

The paused winner that was just young

Real pattern, anonymised
Tuesday readMonday cohort at 1.6x ROASDay-1 maturity, ~50% of conversions arrived
Action takenScale cut 40%Budget moved to an older, 'stable' campaign
Friday readSame cohort at 3.3xDay-4 maturity, curve mostly played out
Cost of impatience₹2.8L of efficient spend pausedThree days of learning reset for nothing
The campaign was never failing. It was one day old. Optimisation actions taken before day 7 are actions taken on half the evidence — restrict early reads to spend pacing, never to kill/scale calls.

How long to wait

Different ad channels mature at wildly different speeds because buyer intent and tracking delays vary by platform:

TAP THROUGHMaturity by surface
Meta prospecting: 5 to 9 days to mature

Discovery ads catch early-journey shoppers. The click often precedes the purchase by most of a week. Retargeting cohorts mature much faster (2 to 4 days), so separate them before judging performance.

WINDOW DAY 5–9 · JUDGE ON DAY 7+

The key rule: there is no single maturity date for your entire account. Branded search can be judged by day 3; social discovery and video require at least 7 to 10 days. An account-level blended ROAS is only as mature as its slowest channel.


The two-read habit

The solution is not a fancy tool; it is a clear reporting habit. Never put an early number and a mature number in the same table without labels. Split every report into two distinct reads:

Days 0–3 · grey it out

⚡ The flash read

Pacing only. “Are we spending on plan?” No judgements, no kill/scale calls. Mark it *provisional* so nobody screenshots it into a verdict.

  • Spend vs plan
  • Anything broken?
  • No efficiency talk
Day 7+ · this one counts

🌳 The mature read

Decisions live here. ROAS, CAC and budget moves are computed only on weeks old enough that ~85%+ of buyers have arrived.

  • ROAS & CAC verdicts
  • Scale / kill / keep
  • Budget shifts

In a hurry — big sale, can’t wait a week? Use the bridge: divide the flash number by the share you expect to have arrived. Day-2 revenue of ₹6.2L at ~60% maturity nowcasts ≈ ₹10.3L final. Show the maths, label it a forecast, and nobody mistakes weather for climate.

In practice: Monday's weekly review examines last Monday's clicks (7 days mature) to judge channel efficiency. The past weekend's spend is shown only as a pacing check (greyed and marked provisional).

Your Monday checklist do these in order →

  • Grey out Days 0–3 in every report — label them “provisional”, never screenshot them into a verdict.
  • Judge efficiency on Day-7+ cohorts only — ROAS, CAC and budget moves live in the mature read.
  • Sale week? Pace on spend, nowcast via the bridge, and demand a 30%+ miss before touching anything.
Maturity-Window Query: Current vs. Mature ROAS

Quick gut-check

Two questions. If you get both, you’ve got it — and you’ll never panic at a Day-1 number again. 2 mins, no grading!

Q1. Monday’s cohort reads 1.6x on Tuesday and 3.3x on Friday. What happened?

Q2. You must decide during a big sale and can’t wait 7 days. What do you do?


Frequently asked questions

My ROAS always recovers a few days later. Is tracking broken?

No — that recovery is the lag curve playing out normally. A group of clicks that reads 1.6x on day 1 and 3.3x on day 7 is behaving as expected. Only worry if your numbers stay flat from day 1 to day 7; that means demand actually dropped.

Should I lengthen attribution windows to catch late buyers?

Lengthening your attribution window captures later buyers, but it also claims credit for accidental sales that had little to do with the ad. Match your window to your measured lag curve: if 90% of buyers purchase within 7 days, a 7-day click window is plenty.

How do sales and festive spikes change the curve?

Promotional spikes compress the curve. Shoppers feel urgency, so day-0 and day-1 sales jump 10 to 20 percentage points higher than usual. After the sale ends, the curve stretches back out. Never use holiday numbers to set your year-round reporting rules.

Can I optimise intraday during a big sale?

Yes, but with guardrails: pace on spend, judge efficiency only through the bridge formula (flash revenue divided by expected maturity share), and require campaigns to miss expectations by at least 30% before pausing them.


Takeaways for your next report

  • Every fresh conversion number is an incomplete count against full ad spend — early reads always make ROAS look artificially low.
  • A typical store sees roughly 50% of buyers arrive by day 1, 70% by day 3, and 90% by day 7.
  • Channels mature at different speeds — branded search takes 3 days, while social prospecting and video need 7 to 10 days.
  • Split your reporting into a flash read for spend pacing and a day-7 mature read for budget and scaling decisions.
stick this on your Monday report
Free tool

Budget Pacing Calculator

Project whether a campaign will land under, on, or over its monthly budget, based on spend-to-date and days elapsed.

Chinmay Raibagkar

Chinmay Raibagkar

About author →

Founder of DataLens AI. He helps non-technical teams read their ad and database numbers with confidence — which number to trust, what to do next, and what to ignore.

Glossary terms referenced