← Back to Blog

Safari’s 7-Day Cookie Cap Plus CNAME Blocking Breaks WooCommerce Attribution

Quick Answer: Safari’s 7-day client-side cookie cap combined with Safari 27’s CNAME blocking eliminates both primary attribution mechanisms for roughly 27% of mobile traffic (CookieStatus / Apple, 2026). Any WooCommerce store running paid ads loses attribution on Safari visitors whose purchase cycle exceeds 7 days — and the CNAME workaround that identity resolution vendors used to extend cookie lifetimes is now blocked at the infrastructure level. Server-set first-party cookies on a genuine subdomain are the only mechanism that survives both restrictions.

Safari deletes client-side JavaScript cookies after 7 days, which means any visitor who clicks an ad, browses your store, and returns 8 or more days later appears as a new visitor — the conversion is attributed to direct traffic rather than the paid campaign that drove it (CookieStatus, 2024). For any product with a consideration period longer than a week, Safari’s cookie cap breaks the attribution chain completely.

The mechanism is part of Safari’s Intelligent Tracking Prevention (ITP). Every cookie set by JavaScript — which includes the tracking cookies from GA4, Google Ads, and Meta Pixel — gets a 7-day expiry enforced by the browser, regardless of what expiry the cookie’s creator intended. Your tracking script might set a 90-day cookie. Safari overrides it to 7 days.

For a WooCommerce store selling $200+ products, this is devastating. Few customers see an ad for a premium product and buy within 7 days. The research, comparison, and consideration cycle typically runs 2 to 4 weeks. By the time the customer returns to purchase, Safari has deleted every cookie that connected them to the original ad click. The sale still happens — your revenue is real — but your attribution data says it came from nowhere.

Safari caps client-side JavaScript cookies at 7 days — any WooCommerce purchase cycle longer than a week loses its attribution chain entirely (CookieStatus, 2024).

What does Safari 27’s CNAME blocking add on top of the 7-day cap?

CNAME cloaking was the main workaround — identity resolution vendors used DNS records to disguise their tracking domains as your subdomain. Safari 27 detects and blocks this pattern at the infrastructure level, eliminating the last method for extending cookie lifetimes beyond 7 days on Safari (Apple, 2026). The door that was cracked open is now shut.

The workaround was clever: instead of setting cookies from a third-party domain (which Safari blocks entirely), vendors would create a CNAME DNS record pointing a subdomain of your site — say, `track.yourstore.com` — to their server. Because the cookie appeared to come from your domain, Safari treated it as first-party and gave it a longer lifetime. Hundreds of identity resolution, analytics, and attribution vendors relied on this technique.

Safari 27 looks beyond the DNS surface. It checks whether the IP address behind a CNAME record belongs to a known tracking infrastructure, and if it does, the cookie gets the same 7-day cap — or outright blocking — as any other third-party tracking mechanism. The technical sophistication of the workaround doesn’t matter. Apple’s position is clear: if the cookie serves a tracking purpose and doesn’t genuinely originate from the site’s own server, it doesn’t get first-party treatment.

Related: Safari 27 Just Killed Identity Resolution: What Apple’s Network-Level Blocking Means for Your WooCommerce Ad Tracking

What percentage of e-commerce traffic comes from Safari?

Safari holds roughly 27% of global mobile browser share (Statista, 2026) and dominates in high-spending e-commerce markets like the UK, US, and Australia — meaning about a quarter of your traffic is affected by these attribution restrictions. In Apple-heavy markets, the share is higher.

The numbers are worse than the global average suggests. In the US, Safari’s mobile share sits closer to 55%. In the UK, it’s roughly 50%. Australia runs around 55%. These are also the markets with the highest per-visitor revenue for English-language WooCommerce stores. The visitors most likely to buy expensive products are the visitors most likely to be on Safari — and the ones whose attribution data is most likely to be broken.

Desktop Safari adds another layer. While Chrome dominates desktop browsing globally, MacBook and iMac users browsing on Safari face the same cookie restrictions. A WooCommerce store with a strong US or UK audience can easily have 40 to 50 percent of total sessions running on Safari across mobile and desktop combined.

How much marketing budget is misallocated due to broken attribution?

Businesses with broken attribution misallocate an estimated 30% of their marketing budget (Search Engine Land, 2025) — spending more on channels that get false credit and less on the channels that actually drive conversions. Safari’s cookie restrictions are a direct contributor because they systematically under-report paid channels and inflate direct traffic.

The misallocation pattern is predictable. When Safari deletes the cookie that links a visitor to their original ad click, the eventual conversion gets attributed to “direct” — the category for visitors who supposedly typed your URL directly into the browser. Your Google Ads dashboard shows fewer conversions than actually occurred. Your Meta Ads Manager reports lower ROAS than reality. Both platforms’ bidding algorithms receive weaker conversion signals, so they optimise less effectively.

What actually happenedWhat attribution reportsBudget consequence
Customer clicked Google Ad, returned 10 days later, purchasedDirect traffic conversionGoogle Ads budget cut — appears to underperform
Customer clicked Meta ad on iPhone, browsed on Safari, bought on day 12Direct / organic conversionMeta budget cut — low reported ROAS
Customer clicked email link, Safari deleted cookie, returned via bookmarkDirect traffic conversionEmail attributed value drops — less investment in campaigns

The result is a store that thinks direct traffic is its best channel and paid acquisition doesn’t work — when in reality, paid acquisition is driving sales that Safari makes invisible.

30% of marketing budgets are misallocated due to broken attribution — Safari’s cookie restrictions systematically inflate direct traffic at the expense of paid channels (Search Engine Land, 2025).

Related: Safari ITP’s 7-Day Cookie Kill vs Server-Set 400-Day Cookies: The Attribution Gap Costing WooCommerce Stores Real Revenue

How did iOS 14.5 compound the Safari attribution problem?

iOS 14.5’s App Tracking Transparency reduced Facebook’s attribution accuracy by roughly 50% (Meta, 2021) — and this operates on top of Safari’s cookie restrictions, creating a double layer of data loss for any WooCommerce store running Meta ads to iOS users. The cookie problem and the ATT problem aren’t alternatives. They stack.

ATT blocks cross-app tracking: when a user opts out (and roughly 75% do), Meta can’t link the ad impression in the Instagram or Facebook app to the purchase event on your website. Safari’s cookie cap then removes the web-side tracking that might partially compensate — the click-through cookie that would at least connect the browser session to the ad click gets deleted after 7 days. The result is a user who saw your Meta ad, clicked through, considered for two weeks, and purchased — with neither the app-level nor the web-level attribution mechanism surviving long enough to credit the ad.

For WooCommerce stores, this double layer means Meta’s Conversions API (CAPI) is not optional. CAPI sends conversion events server-to-server, bypassing both ATT and Safari’s cookie restrictions. But CAPI only works if you have a server-side layer capturing the events in the first place — and most WooCommerce stores are still running a client-side Meta Pixel as their only integration.

LIFETIME LOCK on Harvest Annual Plan

Push your WordPress event data server-side seamlessly into BigQuery so AI can analyse it.

Let's Do It !

What percentage of businesses struggle with cross-channel attribution?

70% of businesses report difficulty achieving accurate attribution across channels (Search Engine Land, 2025), and Safari’s restrictions are a major contributor. By systematically under-counting the channels that drove the initial click, Safari makes every multi-channel attribution model less reliable.

Cross-channel attribution requires seeing the full customer journey — from first touch to last. When Safari deletes the cookies that connect early touchpoints to eventual conversions, the journey appears to start at whatever the customer did within the last 7 days. Any touchpoint older than that disappears from the model entirely. The attribution tool, whether GA4’s data-driven model, a third-party MTA tool, or a simple UTM analysis, operates with a truncated timeline.

The problem is especially severe for stores running traffic from multiple platforms. A customer might discover your product through a TikTok video, click through from an Instagram ad the following week, and purchase via a Google search two weeks later. On Safari, only the Google search click survives in attribution. TikTok and Instagram get zero credit — not because they didn’t work, but because Safari deleted the evidence before the purchase happened.

Does Google Analytics show the full impact of Safari restrictions?

GA4 itself is affected by Safari’s cookie restrictions — its client-side cookies are also capped at 7 days, meaning GA4’s own attribution reports undercount Safari conversions rather than revealing the problem (CookieStatus, 2024). The tool you’d use to diagnose the data loss is subject to the same data loss.

GA4’s measurement cookie (`_ga`) is set by JavaScript, so Safari applies the 7-day cap to it just like any other client-side cookie. When a Safari visitor returns after 8 days, GA4 assigns them a new client ID. Their previous sessions, their original traffic source, their entire browsing history on your site — all disconnected. GA4 doesn’t show you that a returning customer was lost from attribution; it shows you a “new” visitor who converted from direct traffic.

This creates a dangerous blind spot. Store owners who check GA4 for attribution accuracy are checking a tool that suffers from the same problem they’re trying to diagnose. The direct traffic inflation, the under-reported paid channels, the inflated new-user counts — these show up in GA4 as the truth, not as symptoms of Safari’s cookie restrictions. You can’t see the gap from inside the gap.

Related: Safari ITP Is Killing Your WordPress Attribution: Here Is What 7-Day Cookies Actually Cost You

How does server-side tracking restore Safari attribution?

Server-side tracking sets first-party cookies from your actual server on a genuine subdomain — not via CNAME — which Safari treats as legitimate first-party cookies that are not subject to the 7-day cap (Apple, 2026). A server-set cookie can carry a 400-day expiry that Safari respects, restoring full attribution windows for every Safari visitor.

The distinction is between JavaScript-set cookies and server-set cookies. When your tracking script runs in the browser and creates a cookie, Safari classifies it as a client-side cookie and enforces the 7-day cap. When your actual web server sets a cookie via an HTTP response header on a domain you genuinely control, Safari classifies it as a legitimate first-party cookie and respects the expiry you set — up to 400 days under current standards.

Tools like Transmute Engine implement this for WooCommerce by running a first-party tracking endpoint on the store’s own subdomain. The cookie is set by the server, not by JavaScript; the subdomain genuinely resolves to the store’s tracking infrastructure, not to a third-party service via CNAME. Safari has no reason to restrict it because it is, by every technical definition, a legitimate first-party cookie.

The result is measurable: the same visitor who loses their attribution chain after 7 days on client-side tracking retains it for the full cookie lifetime on server-side. Purchase cycles of 14, 30, or 60 days — common for higher-value WooCommerce products — attribute correctly to the campaign that drove the first click. The revenue was always there. Server-side tracking makes it visible.

LIFETIME LOCK on Harvest Annual Plan

Push your WordPress event data server-side seamlessly into BigQuery so AI can analyse it.

Start NOW !

Key Takeaways

  • Safari’s 7-day cookie cap kills attribution for longer purchase cycles: Any WooCommerce customer who takes more than 7 days from ad click to purchase loses their attribution chain on Safari.
  • Safari 27’s CNAME blocking removes the last workaround: Vendors that disguised tracking domains via DNS are now blocked at the infrastructure level.
  • 27% of global mobile traffic runs on Safari: In Apple-heavy markets like the US and UK, the share exceeds 50% on mobile.
  • GA4 can’t diagnose what it also suffers from: GA4’s own cookies face the same 7-day cap, so its reports undercount Safari conversions rather than revealing the problem.
  • Server-set first-party cookies are the only surviving fix: Cookies set by your actual server on a genuine subdomain bypass both the 7-day cap and CNAME blocking.
How does Safari’s 7-day cookie cap break WooCommerce attribution?

Safari deletes client-side JavaScript cookies after 7 days, which means any visitor who clicks an ad, browses your store, and returns 8 or more days later appears as a new visitor. The conversion is attributed to direct traffic rather than the paid campaign that drove it.

What does Safari 27’s CNAME blocking add on top of the 7-day cap?

CNAME cloaking was the main workaround — identity resolution vendors used DNS records to disguise their tracking domains as your subdomain. Safari 27 detects and blocks this pattern, eliminating the last method for extending cookie lifetimes on Safari beyond 7 days.

What percentage of e-commerce traffic comes from Safari?

Safari holds roughly 27% of global mobile browser share and dominates in high-spending e-commerce markets like the UK, US, and Australia — meaning about a quarter of your traffic is affected by these attribution restrictions.

How much marketing budget is misallocated due to broken attribution?

Businesses with broken attribution misallocate an estimated 30% of their marketing budget — spending more on channels that get false credit and less on the channels that actually drive conversions.

How did iOS 14.5 compound the Safari attribution problem?

iOS 14.5’s App Tracking Transparency reduced Facebook’s attribution accuracy by roughly 50%, and this operates on top of Safari’s cookie restrictions, creating a double layer of data loss for any WooCommerce store running Meta ads to iOS users.

What percentage of businesses struggle with cross-channel attribution?

70% of businesses report difficulty achieving accurate attribution across channels, and Safari’s restrictions are a major contributor, since they systematically under-count the channels that drove the initial click.

Does Google Analytics show the full impact of Safari restrictions?

GA4 itself is affected by Safari’s cookie restrictions — its client-side cookies are also capped at 7 days, meaning GA4’s own attribution reports undercount Safari conversions rather than revealing the problem.

How does server-side tracking restore Safari attribution?

Server-side tracking sets first-party cookies from your actual server on a genuine subdomain — not via CNAME — which Safari treats as legitimate. These server-set cookies are not subject to the 7-day cap, restoring full attribution windows for Safari visitors.

References

  1. CookieStatus (2024). Safari ITP cookie restrictions and expiry behaviour. Source
  2. Apple Developer (2026). WebKit and Safari 27 privacy updates — CNAME blocking. Source
  3. Statista (2026). Global mobile browser market share. Source
  4. Search Engine Land (2025). Cross-channel attribution challenges and budget misallocation. Source
  5. Meta Business (2021). iOS 14.5 App Tracking Transparency impact on advertising attribution. Source