68% of attribution models expire before WooCommerce customers finish deciding. That’s not a tracking failure—it’s a mismatch between platform defaults and how your customers actually shop. Facebook defaults to a 7-day click window. Google Ads uses 30 days. Your customers might take 11. And no one told you to check.
Here’s the thing: there is no universally “right” attribution window. There is only the one that matches your store’s real purchase timeline. If those two numbers don’t match, you’re making budget decisions on phantom data—cutting channels that actually work because their customers just take a little longer to decide.
And Why It’s Systematically Breaking Your Attribution
Attribution time lag is the number of days between a customer’s first marketing touchpoint and their completed purchase. Most attribution guides skip straight to “which model should I use?”—but the model doesn’t matter if the window is wrong to begin with.
Every ad platform is designed to claim as many conversions as possible within its window. That’s not deception—it’s how attribution is architecturally designed. Facebook sees a click, starts a 7-day timer, and counts any purchase within that window as its own. Google does the same with its 30-day window. If both platforms touched the same customer before they bought on day 8, both will claim the sale.
According to Triple Whale’s DTC Benchmark (2025), ad platforms overclaim attribution by 40–60% versus actual revenue. You’re not looking at what each channel earned. You’re looking at what each channel claimed. That’s a meaningful difference when you’re deciding where to shift next month’s budget.
The result: channels with longer consideration cycles—content marketing, top-of-funnel social, email nurture sequences—look terrible on reported ROAS. Fast-closing channels look great. Budgets shift toward closers. Openers get cut. Growth plateaus, and no one can explain why.
You may be interested in: Every Ad Platform Is Claiming the Same Sale
Why Attribution Windows Are Set Wrong By Default
Platform default windows were calibrated for average customer behavior across all advertisers—not your specific store, product category, or price point. A $15 impulse purchase converts in hours. A $300 considered purchase might take three weeks of research, price comparison, and re-targeting before the customer clicks “buy.”
The defaults in use today:
- Facebook / Meta Ads: 7-day click, 1-day view (Meta Ads Help, 2025)
- Google Ads: 30-day click, 1-day view (Google Ads Help, 2025)
- GA4 data-driven attribution: requires 400+ monthly conversions to activate—below that threshold, GA4 falls back to last-click automatically (Google Analytics Help, 2025)
If your median time-to-purchase is 11 days, Facebook’s 7-day window misses every customer who bought on day 8, 9, 10, or 11. Those sales happened. Facebook influenced them. Facebook gets zero credit. You see low ROAS. You cut Facebook. Your top-of-funnel dries up. Six months later, even your “good” channels start underperforming.
73% of marketers report significant attribution challenges since iOS 14.5 (Direct Agents, 2025). Privacy changes didn’t create this problem—they made an existing measurement gap impossible to ignore.
How to Calculate Your Store’s Real Time-to-Purchase
Before changing any platform settings, measure your actual data. Three methods, from simple to precise.
Method 1: WooCommerce Order Data (Free, Approximate)
Go to WooCommerce → Reports → Orders. Filter by a 90-day range and export. For customers with email addresses in your list, cross-reference their subscriber join date with first purchase date. If someone joined March 1st and bought March 12th, their consideration window was approximately 11 days. Run this across 50–100 customers and calculate the median. That number is your starting benchmark.
This method is imprecise—email subscription isn’t the same as first ad touch—but it gives you a directional answer within an hour.
Method 2: GA4 Explorations (Better, If Your Data Is Clean)
In GA4’s Explorations, create a funnel exploration from first_session to purchase. Add the dimension “Days to conversion” to see the distribution. GA4 will show you how many customers converted same-day, within 3 days, 7 days, 14 days, and beyond.
The limitation is significant: GA4 only tracks sessions it can reach. With 31.5% global ad blocker usage (Statista, 2024) and Safari’s ITP restrictions, a meaningful slice of your consideration journey is already invisible before you start this analysis.
Method 3: BigQuery Time-Lag Query (Most Accurate)
If your event data is streaming to BigQuery, you can calculate the exact median time-to-purchase per acquisition channel—unfiltered by cookie limits or ad blockers.
The SQL logic: for each purchase event, find the earliest session event with the same user ID. Calculate the difference in days. Group by acquisition source to see which channels have the longest consideration cycles:
SELECT
traffic_source,
APPROX_QUANTILES(days_to_purchase, 100)[OFFSET(50)] AS median_days,
COUNT(*) AS total_purchases
FROM (
SELECT
p.user_id,
p.traffic_source,
DATE_DIFF(DATE(p.event_timestamp), DATE(s.event_timestamp), DAY) AS days_to_purchase
FROM purchases p
JOIN first_sessions s USING (user_id)
)
GROUP BY traffic_source
ORDER BY median_days DESCThis gives you channel-level time-lag data. If organic search converts in 2 days but paid social takes 14, those channels need fundamentally different attribution windows—and you now have the data to prove it.
You may be interested in: Your GA4 Audience Data Is Biased, Not Just Incomplete
What to Do With Your Time-Lag Data
Once you know your store’s real purchase timeline, adjusting platform windows is straightforward.
Facebook / Meta Ads
In Ads Manager, go to Columns → Customize Columns → Attribution Settings. You can extend to 14-day click or 28-day click (28-day is available for some account types). Match the window to your actual median time-lag. If your median is 10 days, a 14-day click window is substantially more accurate than the default 7-day—and your reported ROAS will rise accordingly, reflecting conversions that were always happening but not being counted.
Google Ads
Google’s 30-day default is more forgiving than Facebook’s. The larger issue is GA4’s attribution model. If GA4 is running last-click because your store is under the 400 conversion threshold for data-driven, Google Search gets credit for every sale it closed—regardless of what other channels opened the relationship.
The fix: in GA4, go to Admin → Attribution Settings and manually increase the acquisition conversion lookback window to 60 or 90 days if your consideration cycle warrants it. This is one setting that most WooCommerce store owners have never touched.
The Platform Overlap Problem
68% of multi-touch attribution models over-credited digital channels in 2025 (MarTech Series, 2025). Adjusting windows helps, but it doesn’t solve the deeper issue: every platform reports its own version of what it contributed. You need a neutral source of truth that isn’t filtered through anyone’s business model.
Why First-Party Event Data Is the Long-Term Answer
Platform-reported attribution is designed to make each platform look good. When Apple introduced ATT in 2021, Facebook’s reported ROAS dropped 30–40% overnight for many advertisers. The actual ad performance didn’t change. The visibility did. The same structural vulnerability exists in every window-dependent reporting system.
First-party server-side tracking doesn’t fix what platforms choose to report. But it gives you a parallel source of truth that isn’t filtered through any platform’s window logic or incentive structure.
Transmute Engine™ is a dedicated Node.js server that runs first-party on your subdomain—not a plugin installed on WordPress, but a separate server application at an address like data.yourstore.com. The inPIPE WordPress plugin captures WooCommerce events and sends them via API to your Transmute Engine server, which streams every event—purchase timestamps, session starts, traffic sources—directly to BigQuery. This is the raw material for the time-lag query above: your own event log, owned by you, queryable by you, not filtered through any platform’s attribution window or consent to track.
For stores where consent mode is further compressing attribution visibility, see GDPR Consent Mode V2 Is Breaking WooCommerce Tracking—Here is the Math for the compounding effect on cross-channel measurement.
Key Takeaways
- Platform default windows are averages, not your store’s reality. Facebook’s 7-day click and Google’s 30-day click were calibrated across all advertisers—not your product category, price point, or customer behavior.
- Measure your real time-to-purchase before changing anything. Use WooCommerce order data, GA4 Explorations, or BigQuery queries to find your store’s actual median days-to-convert by channel.
- The mismatch is systematic. 68% of attribution models over-credited channels in 2025 simply because windows expired before customers finished deciding (MarTech Series, 2025).
- Channels with long consideration cycles look worst on default ROAS. Top-of-funnel social, content marketing, and email nurture are the most likely victims of mismatched windows—and the first to get cut.
- First-party event data in BigQuery lets you calculate time-lag accurately—unfiltered by platform reporting, unconstrained by cookie limits, and not lost to ad blockers.
Yes—significantly. Facebook’s default 7-day click window only counts conversions that happen within 7 days of an ad click. If your customers typically take 10–21 days from first touch to purchase, a substantial proportion of Facebook-influenced sales are never attributed to the channel. Your reported ROAS reflects only the fast-converting customers, making Facebook appear worse than it actually performs. You can extend Facebook’s window to 14-day or 28-day click in Ads Manager’s attribution settings to recover visibility into longer-cycle conversions.
The most accessible method is your WooCommerce order database—cross-reference customer subscriber dates with first purchase dates to get a directional estimate. For more precise analysis, use GA4 Explorations with the “Days to conversion” dimension. For the most accurate channel-level data, stores with Transmute Engine and BigQuery can query first_session events against purchase events per user ID to calculate the exact median time-to-purchase by acquisition source.
Only after measuring your actual time-lag first. If your store’s median time-to-purchase is 10 days, switching Facebook to a 14-day click window will capture more of your real conversions and improve reported ROAS accuracy. If your median is 3 days, the default 7-day window is already generous. The key risk is optimizing both channels with mismatched time-horizon assumptions—cutting top-of-funnel spend that is actually building your customer base, just on a timeline the default windows can’t see.
Every ad platform claims credit for conversions that occurred within its attribution window—including conversions that other platforms also claimed. This is normal behavior, not a misconfiguration. Ad platforms are architecturally designed to maximize claimed conversions within their windows. Triple Whale’s DTC Benchmark (2025) found platforms overclaim by 40–60% versus actual revenue. First-party data in BigQuery lets you count each sale once and assign it to the channel that most influenced the decision, rather than accepting each platform’s self-reported totals.
Attribution time lag is the number of days between a customer’s first marketing touchpoint and their completed purchase. Most WooCommerce stores never measure this—they accept platform default windows as correct for their store. But if your average time-lag is 11 days and Facebook’s window is 7 days, 4 days of conversions are systematically invisible to Facebook’s reporting. Measuring your store’s actual time-lag is the prerequisite for any meaningful attribution window configuration.
See how Transmute Engine™ streams every WooCommerce event to your own BigQuery so you can calculate your real purchase time-lag—and finally set attribution windows that match how your customers actually buy. Learn more at seresa.io
