Safari has a quiet rule that can make a returning buyer look brand new: if your tracking subdomain resolves to a different network than your main site, WebKit may treat it as cloaked tracking and cut server-set cookies to seven days.
Why a returning Safari shopper looks new
Picture the scenario from the analysis. A shopper clicks an ad on Safari, browses products, leaves, and comes back eight days later to buy. The analytics platform records a new user instead of tying the visits together.
“The visitor didn’t change devices or clear their cookies. An identifier in Safari simply expired.”
That line comes from Mariusz Brucki, an analytics engineer and founder of Measurelake, writing on the blog of server-side tagging host TAGGRS.
Server-side tracking doesn’t guarantee cookie lifetime
Moving to server-side tagging changes the path data travels, but recognising an anonymous visitor often still depends on an identifier kept in the browser. GA4, for example, commonly uses a client ID held in a first-party cookie.
Safari already caps JavaScript-set cookies under Intelligent Tracking Prevention. Since Safari 16.4 in March 2023, the same seven-day cap can also hit cookies set through HTTP responses when WebKit detects CNAME or IP address cloaking. The test compares the network address behind the tracking response with the main site’s network.
- One address is IPv4 and the other is IPv6.
- Two IPv4 addresses share fewer than 16 leading bits.
- Two IPv6 addresses share fewer than 64 leading bits.
A main site running behind Cloudflare while its tracking subdomain resolves to a separate provider is a common tripwire. The domain names look same-site, but the network addresses do not.
The fix: serve tracking from a path, not a subdomain
Same-site and same-origin are not interchangeable. A subdomain shares the registrable domain but remains a separate host. A path on the primary host shares scheme, host and port.
That is why the proposed workaround is to serve tracking from something like /metrics on the main domain. A reverse proxy or Cloudflare Worker receives those requests and forwards them to the existing server container. Crucially, every Set-Cookie header must be forwarded correctly.
This does not make cookies permanent. Persistent cookies still face a general maximum of roughly 400 days, and users can delete storage, change consent or browse privately. It may also reduce hostname-based blocking, but obvious paths such as /analytics, /track or /collect can still attract filters.
Google’s tag gateway follows the same logic by serving tags from a path on the advertiser’s domain. Launch partner Cloudflare reported an 11% signal uplift, and Fastly cited 14% after the Google Cloud integration reached general availability in June 2026. Those are vendor figures, not independent measurement.
What it means for paid media
When a browser identifier expires after seven days, an earlier campaign visit and a later conversion may no longer share a usable identifier. Returning Safari visitors can be counted as new, and weaker conversion data can reach Smart Bidding. Remarketing audience inputs can also suffer.
Two clarifications matter. A longer-lived cookie does not turn a seven-day attribution window into a 30-day window; it only preserves a browser signal inside the platform’s existing window. Audience duration, consent and minimum list sizes still apply.
Read the vendor lens
TAGGRS sells this same-origin route through a Cloudflare Worker, and the post closes with a prompt to start a free account. Brucki’s author profile also identifies him as founder of Measurelake. None of that invalidates the Safari mechanism, but the post offers no data on how widespread the problem is.
For a considered purchase that takes two weeks, a seven-day cap can fragment journeys. For a product bought within a day, it is a non-issue. Test your own Safari return windows before changing your tracking architecture.
Source: PPC Land
