Meta Ads attribution windows: which one to choose to measure your campaigns' real ROAS

What is an attribution window in Meta Ads?

An attribution window (or conversion window) defines the period during which Meta credits a sale to an ad. If someone clicks your ad on Monday and buys on Friday, Meta counts that sale if the configured window covers it.

The available options are:

• 1-day click — Meta attributes purchases made up to 24h after clicking the ad
• 7-day click — the most common; attributes purchases up to 7 days after the click
• 1-day view — attributes purchases to someone who simply saw the ad (no click) within 24h
• 7-day click + 1-day view — the default setting, which maximizes the credit Meta gives itself

Why does the window affect the ROAS you see so much?

Imagine you run a clothing store and someone clicks your ad on Monday. That same shopper was already thinking about buying that t-shirt, had it in their cart at another store, and finally buys on Thursday — but in another store of yours, where they arrived directly. Meta, with a 7-day window, can attribute that purchase to your campaign even though it wasn't the cause.

This isn't a bug; it's how a last-click or impression-based attribution model works. The result: your ROAS in Meta can be 4x or 5x when your real ROAS — after subtracting every cost — is 1.5x.

Switching from "7-day click + 1-day view" to "1-day click" can drop a campaign's ROAS 30-50% overnight, without you changing anything in your strategy. The only thing that changed is how much credit you give yourself.

Which attribution window should you use?

It depends on your purchase cycle:

• Impulse-buy products (low ticket, quick decision): use 1-day click. If they don't buy that day, the ad was unlikely to be the cause.
• Slow-decision products (furniture, electronics, premium apparel): 7-day click can be reasonable, but always compared against your real numbers.
• Never use "1-day view" on its own: someone who saw your ad but didn't click was unlikely to be convinced by it. This window only inflates numbers.

Meta's official advertiser documentation explains the technical options, but it doesn't tell you which one to use to measure honestly — that's what we cover here.

How does the window affect the quality of the data Meta uses to optimize?

Here's the underlying problem few people mention. Meta uses the conversions it records to feed its optimization algorithm. If you have a 7-day window and many of those conversions are purchases that would have happened without the ad anyway, you're "teaching" the algorithm to look for profiles that behave like that — not necessarily profiles your advertising converts.

But there's something more serious: the problem isn't just which conversions you count, but what data comes with those conversions. If you have a 7-day window and the event arrives on day six but is missing the buyer's email or phone, Meta records the conversion but can't match that event to a real profile in its database.

This ties directly to the Event Match Quality (EMQ) problem: if you send conversions with incomplete data — no email, no phone, no name — Meta can't identify who bought, can't build good lookalike audiences, and your acquisition cost goes up even if ROAS in the dashboard looks fine.

Why isn't the browser pixel alone enough to record conversions?

The Meta pixel you install on your store captures browser events — when someone makes a purchase, the pixel fires a "Purchase" event. But that firing can fail for many reasons: ad blockers, iOS tracking restrictions, Safari deleting cookies, or simply the user closing the tab before the pixel loaded.

With a 7-day attribution window, that kind of event loss piles up. Many purchases that happened never reach Meta, which makes the algorithm underestimate your campaigns' real performance.

The fix is server-side tracking: events go out from your server, not the user's browser, and arrive with complete identification data — email, phone, name, city and postal code — so Meta can make the match.

What's the difference between Meta attribution and real attribution?

Meta attribution tells you how many sales Meta says it caused. Real attribution requires comparing that against your total sales, by period, after subtracting costs.

If Meta reports 200 sales this week with a 7-day window, and your store had 250 total sales, that doesn't add up — Meta can't have caused more than 80% of your sales. The difference between what Meta claims and what actually happened is called over-attribution, and it's the central problem with measuring on long windows.

Tools like Escalafy solve this by calculating real ROAS from your real sales data — not from the Meta dashboard — and subtracting every cost: shipping, platform fees, product costs, agency fees. The result is a metric you can use to make decisions, not just to report.

The number that matters isn't in the Meta dashboard

The ROAS you see in Meta Ads depends on which window you configured, whether the pixel fired correctly, whether blockers were active, and how generously the algorithm credits itself. It's useful as a directional indicator, but it's not the number you should make spending decisions with.

The number that matters is your real profit per peso of ad spend — after subtracting product, shipping, Mercado Pago fees, agency fees and fixed costs. That's what Escalafy calculates in real time, without you touching a spreadsheet.