Attribution Windows for Shopify: Why 7-Day Click Hides Slower Buyers

Attribution windows define how far back an ad platform looks when deciding which ad click or view caused a purchase. On Shopify, the default attribution window for Meta Ads is 7-day click and 1-day view, and for Google Ads it is 30-day click and 0-day view by default. For many Shopify stores, these defaults hide real conversions: a customer who clicks a Meta ad on Monday, browses for two weeks, then buys on a Saturday falls outside the 7-day click window entirely. The purchase happened, the order is in Shopify, but Meta never connects it to the ad that started the journey. The result is underreported conversions, inflated cost per acquisition, and an optimization algorithm that optimizes against an incomplete picture.

The Shopify signal recovery guide explains the broader strategy for fixing underreporting, and the iOS ATT impact on Shopify ads article covers the client-side tracking loss that makes attribution windows matter even more for mobile-heavy stores. This guide focuses specifically on how attribution windows work, why the defaults fail Shopify merchants, and how server-side Pulses address the window problem at its root.

The Quick Answer

An attribution window is the time limit an ad platform imposes on matching an ad interaction to a conversion. Meta defaults to 7-day click and 1-day view; Google defaults to 30-day click. When a Shopify customer’s purchase falls outside that window, the platform does not count it even if the order exists in Shopify. The fix is twofold: extend the attribution window where possible, and ensure server-side Pulses reach the platform so the conversion is at least eligible for matching regardless of the window setting. Stores with average order cycles longer than 7 days, high mobile traffic, or considered purchases lose the most revenue to window mismatch.

What Is an Attribution Window?

An attribution window is the maximum number of days between an ad interaction (click or view) and a conversion event (purchase, add to cart, checkout start) that the ad platform will use to connect the two. If a customer clicks your Meta ad on day one and purchases on day eight, Meta will not attribute that purchase to that ad because the 7-day click window has expired. The purchase still exists in Shopify, but Meta’s reporting treats it as if no ad caused it.

This matters because attribution windows determine what the optimization algorithm sees. When the algorithm thinks an ad generated fewer conversions than it actually did, it shifts budget away from that ad, that campaign, or that audience. The real-world effect is a slow bleed: your best-performing campaigns gradually lose spend because the platform is undercounting their actual impact.

There are two types of attribution windows in most ad platforms. Click-through attribution counts a conversion when the user clicked an ad and then converted within the window. View-through attribution counts a conversion when the user saw (but did not click) an ad and then converted within a shorter window. View-through windows are typically 1 day for Meta and 0 days for Google, because a view without a click is a weaker signal and platforms do not want to over-attribute organic purchases to ads the user barely noticed.

Why the Default Windows Fail on Shopify

The default attribution windows are designed for an average of all advertisers across all industries. They do not account for Shopify’s merchant profile: small to mid-size DTC stores with purchase cycles that vary wildly by category. A fashion store with a 48-hour average purchase cycle fits comfortably within a 7-day click window. A home goods store with a 14-day average purchase cycle does not. A beauty store where customers research, compare, and return to buy over 10 days sits right at the edge, and any friction in the journey pushes the purchase outside the window.

The problem compounds with iOS App Tracking Transparency. When a customer using an iPhone clicks a Meta ad, the purchase journey often continues across multiple devices and sessions. If the customer clicks on their phone, later browses on a laptop, and buys on a tablet, the attribution chain breaks because the pixel cannot connect the sessions across devices. The click happened on the phone, the purchase happened on the tablet, and neither the 7-day click window nor the view-through window can bridge the gap without server-side identity matching.

Alex Schultz, VP of Analytics at Meta, has noted that the shift toward privacy-restricted environments means the platform must rely more heavily on server-side data and modeled conversions to fill gaps that client-side attribution can no longer cover. The implication for Shopify merchants is that the window is not just a time limit; it is a time limit applied to an already degraded data stream.

How to See Your Actual Attribution Gap

Before changing any settings, measure how many purchases fall outside your current attribution window. Export Shopify orders for the past 30 days and note the time between the first ad click (from Meta or Google reporting) and the order timestamp. Count the orders where this gap exceeds 7 days for Meta or 30 days for Google. This count is your window-related underreporting.

A more direct method compares Shopify order counts against platform-reported conversions for the same dates. If Shopify shows 500 orders in a week and Meta reports 320 conversions, the 180-order gap includes both window-related loss and delivery loss (pulses that never reached the platform). A Clarity Score, which measures delivery health per Channel, separates these two problems: a high Clarity Score with a large order-to-conversion gap means the attribution window is the primary culprit; a low Clarity Score means the delivery itself needs fixing before the window discussion matters.

The distinction matters because the fixes are different. Delivery loss is solved by ensuring server-side Pulses reach the platform. Window loss is solved by extending the window, improving identity matching so the platform can connect the click to the purchase across devices, or both.

Meta Attribution Windows: What You Can Change

Meta offers several attribution window configurations for Shopify merchants. The default is 7-day click, 1-day view, but you can change this at the ad set level and at the account level. The available options for click-through are 1-day, 7-day, and 28-day. The available options for view-through are 1-day, 7-day, and 28-day. The combined window options include 1-day click 1-day view (the shortest), 7-day click 1-day view (the default), 7-day click 7-day view, 28-day click 1-day view, and 28-day click 7-day view.

Changing the window affects two things: reporting and optimization. For reporting, the window determines which conversions appear in your results. A 28-day click window will show more attributed conversions than a 7-day click window because more purchases fall within the longer time limit. For optimization, the window determines what the algorithm learns from. A wider window gives the algorithm more data about which clicks led to purchases, which generally improves targeting over time.

However, wider windows also introduce more noise. A 28-day click window attributes purchases to ad clicks that happened nearly a month ago, and in that time the customer may have seen other ads, visited other stores, or changed their mind for reasons unrelated to the original click. Avinash Kaushik, Digital Marketing Evangelist at Google, has written that attribution accuracy degrades as windows extend because the causal link between a specific ad interaction and a specific purchase weakens over time. The practical advice is to match the window to your actual purchase cycle: if your average time from first click to purchase is 10 days, a 7-day window is too short and a 28-day window is unnecessarily wide. A 7-day click with 7-day view or a 14-day click (available through custom attribution modeling) gives you a more accurate picture.

The View-Through Problem

View-through attribution is particularly problematic for Shopify merchants because it can over-count organic purchases. A customer sees a Meta ad, does not click, then later searches for your brand on Google and buys through an organic result. If view-through attribution is enabled with a 1-day window, Meta may claim that purchase as caused by the ad view, even though the customer’s intent was driven by something else entirely. This inflates reported conversions and makes Meta’s ROAS look better than reality.

The fix for view-through inflation is server-side identity matching. When a Pulse carries a stable external event ID and the customer’s email or phone, the platform can connect the purchase to the correct user regardless of which device or session the ad view happened on. Without server-side identity, view-through attribution is guesswork. With it, the platform has the data to make a more accurate connection.

Google Attribution Windows: The Default Advantage

Google’s default attribution window of 30-day click is more generous than Meta’s 7-day click default, which means Google under-reports fewer conversions for stores with longer purchase cycles. However, Google’s window configuration is less flexible for individual merchants: the 30-day click window is the standard for Google Ads conversion tracking, and adjusting it requires using Google Analytics 4 attribution modeling or custom conversion settings.

The more significant issue for Shopify merchants using Google Ads is consent mode. Google Consent Mode v2 expects a consent signal to accompany conversion events, and when consent is absent or defaults to denied, Google may hold conversions regardless of the attribution window. A purchase within the 30-day window still does not get counted if the consent state says the user did not allow ad storage. This is why the consent mode v2 Shopify guide is a prerequisite for accurate Google attribution: the window is useless if the conversion is held on the platform side.

Google also uses data-driven attribution, which distributes credit across multiple ad interactions based on machine learning. Unlike last-click attribution, which gives all credit to the final click, data-driven attribution assigns fractional credit to earlier touches. This means a customer who saw three Google Ads before buying may have the purchase attributed partially to each ad, and the attribution window determines which of those three interactions are eligible for credit分配. A narrower window excludes earlier interactions; a wider window includes them.

Enhanced Conversions and Server-Side Delivery

Google enhanced conversions solve part of the window problem by sending hashed first-party customer data (email, phone) alongside the conversion event. This data lets Google match the purchase to a Google account even when the browser-level conversion tag is blocked or the click ID is missing. Enhanced conversions work within the existing 30-day window but improve the match rate inside that window.

Server-side Pulses through a signal layer like Hawklists go further by delivering the conversion event from the Shopify server to Google’s server, bypassing the browser entirely. This means the conversion is not subject to ad blockers, Safari ITP cookie deletion, or iOS ATT restrictions. The 30-day window still applies, but the conversion is more likely to be delivered and matched within that window because the server-side Pulse carries complete identity data.

Extended Windows: When They Help and When They Hurt

Extending attribution windows is not always the right move. For stores with fast purchase cycles (fashion, beauty, consumables), a 7-day click window is usually accurate because most purchases happen within a week of the ad click. Extending to 28 days in these cases adds noise: organic purchases that happen to occur within 28 days of an ad click get attributed to the ad even though the ad was not the cause.

For stores with slow purchase cycles (home goods, furniture, B2B, considered purchases), extending the window is essential. A customer buying a $500 sofa does not click an ad and buy the same day. They browse, compare prices, read reviews, check with a partner, and return days or weeks later. A 7-day window misses these purchases entirely, and the algorithm learns from an incomplete picture of what actually drives sales.

The practical test is your own data. If your average time from first ad click to purchase (measured in Shopify, not in the ad platform) is under 5 days, keep the default 7-day window. If it is 5 to 14 days, switch to 7-day click with 7-day view or explore custom windows through Meta’s conversion API settings. If it is over 14 days, a 28-day click window is necessary, and you should pair it with server-side delivery to ensure the conversion reaches the platform within that wider window.

How Server-Side Pulses Solve the Window Problem

The core issue with attribution windows is not the window itself; it is the data quality inside the window. A 7-day click window works perfectly well if every purchase within that window is delivered to the platform with complete identity data and a stable event ID. The window only fails when conversions fall outside it or when the platform cannot match the conversion to a user.

Server-side Pulses address both failure modes. First, they deliver the conversion event immediately at the point of purchase, not when the browser finishes loading. This means the conversion timestamp is accurate and the event reaches the platform in real time rather than being blocked or delayed by browser-level issues. Second, server-side Pulses carry the full identity set (email, phone, browser ID, external event ID) because they are captured at the order confirmation point on the Shopify server, where the customer has already provided this information.

A Hawklists deployment captures purchase Pulses at the server level and delivers them to Meta CAPI and Google enhanced conversions automatically. The Clarity Score on the Overview shows delivery health per Channel, so you can verify that every Pulse is reaching the platform. When Clarity Score is healthy (above 75), the attribution window is the remaining variable, and you can adjust it based on your actual purchase cycle data rather than guessing.

The identity matching that server-side Pulses provide also helps the platform connect cross-device journeys. A customer who clicks an ad on their phone and buys on their laptop generates two separate browser sessions, but the server-side Pulse carries the email and phone that link both sessions to the same user. This means the platform can attribute the purchase to the original ad click even though the purchase happened on a different device, effectively extending the functional reach of the attribution window without changing its duration.

A Practical Framework for Window Selection

Start by measuring your actual purchase cycle. Pull the average time from first ad click to purchase from Shopify order data for the past 90 days. This number, not the platform default, should drive your window setting. If your average is 4 days, a 7-day click window is fine. If your average is 12 days, you need a wider window or server-side delivery to close the gap.

Next, verify delivery health. A Clarity Score below 70 percent means the platform is not receiving all the Pulses you are sending, and extending the attribution window will not fix delivery loss. Fix the Channel connection first, then measure the attribution gap on the delivered Pulses.

Finally, test one change at a time. If you extend the window from 7-day click to 28-day click, watch reported conversions, cost per acquisition, and ROAS for two full weeks before judging the result. The extended window should show higher reported conversions and lower cost per acquisition if the wider window is capturing real purchases that the narrower window missed. If reported conversions rise but cost per acquisition stays flat, the additional conversions are likely organic purchases that the wider window is over-attributing to ads.

FAQ

What is the default attribution window for Meta Ads on Shopify? The default is 7-day click and 1-day view. This means Meta attributes a purchase to an ad click if the purchase happens within 7 days of the click, or to an ad view if the purchase happens within 1 day of the view.

Why does Shopify show more orders than Meta reports as conversions? The gap comes from three sources: purchases outside the attribution window, conversions blocked by iOS ATT or ad blockers before reaching Meta, and identity mismatches where Meta receives the conversion but cannot match it to a user. A signal layer addresses all three by delivering server-side Pulses with complete identity data.

Can I change the Meta attribution window for my Shopify store? Yes. You can change the attribution window at the ad set level or at the account level in Meta Ads Manager. The available options range from 1-day click to 28-day click, and you can pair these with view-through windows of 1 day, 7 days, or 28 days.

How do I know if my attribution window is too short? Measure the average time from first ad click to purchase in Shopify. If this average exceeds the attribution window (for example, 12 days with a 7-day window), a significant share of real purchases are falling outside the window and being undercounted.

Does server-side tracking change the attribution window? Server-side tracking does not change the platform’s attribution window setting, but it ensures the conversion event reaches the platform with complete identity data, which improves the match rate inside the existing window. It also delivers the conversion in real time so the timestamp is accurate and the event is eligible for attribution from the moment the purchase occurs.

Should I use 28-day click attribution? Use 28-day click only if your average purchase cycle exceeds 14 days. For stores with faster cycles, 28-day click over-attributes organic purchases to ads and inflates reported ROAS without improving actual performance.

Related Resources

• The Shopify signal recovery guide covers the full strategy for fixing underreported conversions, including attribution window optimization.
• The iOS ATT impact on Shopify ads article explains how Apple’s privacy changes compound the attribution window problem for mobile-heavy stores.
• The server-side tracking guide walks through the technical setup for delivering Pulses directly from Shopify to Meta CAPI and Google enhanced conversions.
• Consent mode v2 for Shopify explains how consent state affects Google conversion reporting regardless of the attribution window.