Reading Meta Attribution Windows Without Fooling Yourself
How Meta's 7-day click and 1-day view attribution windows work, why they overstate ROAS, and how to reconcile them with Shopify's real order data.
Written by Mantas Jurgutis — Founder, Adsify — builds the Google & Meta automation merchants use daily
Editorially reviewed by Adsify Editorial on April 23, 2026 — Reviewed against Shopify, Google Ads and Meta official documentation.
What the default attribution window actually counts
Meta's default reporting setting is 7-day click and 1-day view, meaning a purchase is credited to an ad if the customer clicked it within the past 7 days or saw it (without clicking) within the past 1 day, before converting. This setting is chosen in Ads Manager > Attribution settings and applies retroactively to how existing campaign data is displayed, not just future data — changing it changes the historical ROAS numbers shown for the same campaigns.
Why 1-day view attribution inflates reported ROAS
A view-through conversion means the customer never clicked the ad; they merely had it appear in their feed and later, within 24 hours, purchased through any path — direct traffic, a Google search for your brand name, an email link. Meta's algorithm can still credit that purchase to the ad impression. For stores running heavy retargeting or broad prospecting to an audience that already knows the brand, view-through credit can account for a meaningful share of reported conversions that would very plausibly have happened without that specific ad impression.
Why 7-day click attribution also overstates causality
Even click-based attribution has a causality problem: if a customer clicks an ad on Monday, browses without buying, then returns organically on Friday and completes a purchase, Meta attributes the full order to Monday's ad click. This is a legitimate part of the customer journey the ad may have influenced, but it is not proof the ad was the deciding factor — the customer might have found the store through a different channel entirely in the interim.
The gap between Meta-reported ROAS and Shopify's total orders
This is the most common confusion for Shopify merchants: Ads Manager might report a 4x ROAS from Meta ads, while Shopify admin > Analytics shows total store revenue only grew by an amount consistent with a 2x blended return once all channels and organic traffic are accounted for. Both numbers can be technically accurate under their own definitions — Meta measures attributed conversions under its window, Shopify measures total transactions — but only the total-store view tells you what actually happened to revenue.
A worked reconciliation example
Suppose Shopify shows 500 total orders in a month, and Meta Ads Manager reports 220 attributed Purchases from a EUR 4,000 spend, implying a 3.3x ROAS at a EUR 60 AOV (EUR 13,200 attributed revenue). If organic and direct traffic converted roughly 280 orders on their own in a comparable pre-campaign baseline period, the true incremental contribution of the EUR 4,000 spend might be closer to 100-150 additional orders once overlap and view-through inflation are accounted for — still profitable, but a genuinely different ROAS than the platform-reported 3.3x.
Switching to a stricter attribution setting for analysis
In Ads Manager > Attribution settings, you can view historical data under 1-day click only, which removes view-through credit and shortens the click window. Comparing the same campaign's ROAS under 7-day click/1-day view versus 1-day click only reveals how much of the reported number depends on longer-window and view-through credit; a large gap between the two is a signal to treat the headline ROAS cautiously, not a bug.
Using Shopify's UTM and referrer data as a cross-check
Shopify admin > Analytics > Sessions by traffic source, combined with UTM parameters set on your Meta ad URLs (utm_source=facebook, utm_medium=cpc, utm_campaign matching your campaign name), gives you a last-click, non-modeled view of how many sessions and orders genuinely arrived via a Meta ad click. This number will typically be lower than Meta's self-reported attribution because it doesn't include view-through credit or the extended 7-day click window, but it's a useful lower bound to compare against Meta's upper-bound number.
Why holdout tests are the only real answer
Neither platform-reported attribution nor UTM last-click data can fully answer 'how much revenue would I have made with zero ad spend' — only a controlled holdout can. A geo holdout, where you pause spend in one region while continuing in a matched comparable region for 1-2 weeks, then compare total Shopify order volume between the two, gives a genuine incrementality estimate. This is more work than reading a dashboard, but it's the standard method advertisers use to validate whether reported ROAS reflects real lift.
How attribution window choice affects Advantage+ scaling decisions
Since ASC and Meta's optimization broadly optimize toward whatever your account-level attribution setting credits as a conversion, a longer window with view-through included can make the algorithm appear to find more 'winning' impressions than a stricter window would credit, potentially pushing budget toward tactics (like broad reach to already-aware audiences) that inflate attributed conversions without proportionally growing real revenue. Reviewing performance under a stricter window periodically helps sanity-check scaling decisions.
Attribution and Conversions API don't change the window itself
It's a common misconception that fixing Conversions API deduplication or improving Event Match Quality changes the attribution window logic — it doesn't. CAPI and pixel setup affect how completely and accurately events are captured and matched to users; the attribution window setting (7-day click/1-day view, etc.) is a separate configuration that determines which captured events get credited to which ad exposure.
A practical reporting cadence
Rather than trying to fully solve incrementality every week, adopt a simple monthly cadence: report Meta's standard 7-day click/1-day view ROAS for trend tracking, cross-check it against Shopify total revenue growth and UTM-tagged sessions, and run a geo or budget holdout test once a quarter to periodically validate that reported ROAS direction still roughly matches real incremental lift, adjusting your internal ROAS 'trust discount' if the gap has changed meaningfully.
Communicating this to stakeholders honestly
If you manage ads for a Shopify brand and report ROAS upward, it's worth stating explicitly which attribution window the number reflects and that it includes view-through and extended-click credit, rather than letting a stakeholder assume it means 'for every euro spent, this many euros in genuinely new revenue occurred.' This single clarification prevents most of the disputes that arise later when total store revenue doesn't match the sum of platform-reported ROAS across all ad channels.