Docs · Safari · Measurement
Safari 27 expands click-ID stripping, flags CDPs as fingerprinting, and reportedly blocks ad endpoints by IP. What survives, what breaks, and why governed UTMs matter more than ever.
Safari 27 shipped as a developer beta in June 2026. Apple’s public release notes talk about CSS and rendering. The measurement-relevant changes were not there — they surfaced from reviews of WebKit’s open-source privacy infrastructure (github.com/WebKit/WebKit), later summarised by independent measurement writers (including PPC Land and others).
Treat the details as beta source analysis, not Apple documentation. Behaviour can still change before the stable ship with iOS 27 / macOS 27. The direction — more enforcement below the page — has been consistent for years.
This piece is for people who own tracking templates and UTM governance. Template vs Final URL suffix still follows the Ideal Configuration; tagging discipline lives in how to optimize UTM tags and naming conventions.
Standard UTM parameters are not on Link Tracking Protection’s strip list.
utm_source, utm_medium, utm_campaign, utm_content
and utm_term still travel with the URL in the scenarios these WebKit beta reviews describe.
Click IDs increasingly are stripped — in Private Browsing and when links open from Mail or Messages — before the destination page loads. Safari 17 already covered major paid IDs; Safari 27 reportedly adds:
| Parameter | Platform |
|---|---|
twclid, cn, cxt | X (Twitter) |
si | YouTube (share / session context) |
xmt | Threads |
Previously covered examples include gclid, fbclid and msclkid.
twclid is X’s primary click identifier — same job gclid does for Google Ads.
si is not a classic paid-click ID, but dropping it still removes source context from YouTube traffic in affected Safari sessions.
That asymmetry is the practical takeaway. Platform-native attribution that needs a click ID to survive from ad click to conversion gets weaker every release. Channel reporting built on a governed UTM taxonomy does not. Get Tracking Standards and your UTM monitoring right now — don’t treat click IDs as optional forever, but don’t bet the house on them alone either.
Stripping happens in Private Browsing and for links opened from Mail or Messages. As of Safari 26, click IDs still passed through in ordinary, non-private sessions. Apple’s pattern: expand the parameter list first, widen enforcement later. Users can already opt into stronger rules for all browsing via Advanced Tracking and Fingerprinting Protection → All Browsing in Safari settings.
Plan for broader enforcement. Don’t bet the roadmap on “regular Safari stays loose forever.”
Advanced Fingerprinting Protection (AFP) is often summarised as “Safari blocks these scripts.” The source analysis says otherwise: classified scripts get a permission set. Apple can revoke individually:
Worst case for marketers: the pixel still fires, the platform accepts an event, no console error — but the payload has nothing that joins to a click. The tag looks healthy; attribution is gone.
Important nuance: LTP not stripping UTMs from the URL is separate from AFP denying a classified script permission to read the query string. Your landing URL can still carry UTMs for GA4 and server-side pipelines even when a third-party tag on the page cannot see them.
The LinkedIn Insight Tag (snap.licdn.com) is reported on the fingerprinting list with query and referrer access revoked —
exactly that silent-failure pattern.
The same classification list reportedly includes Tealium and Segment (plus DPG Media and Blueonic in the same beta analyses).
When a CDP is classified, tags deployed through that container inherit the restrictions. A conversion pixel that would be fine loaded directly becomes limited because of the vehicle it arrived in. If you fire conversions via Tealium or Segment client-side, validate in a Safari 27 beta before stable ships — don’t wait for a quiet week of “LinkedIn looks fine in Chrome.”
Earlier protections mostly lived at the application layer — restrict what a script can read, block a request by hostname. Safari 27 reportedly moves part of enforcement to the network transport layer: check the destination IP against known ad-network subnets before the connection completes.
Example from the analysis: bat.bing.com (Bing UET) resolves onto Microsoft ad infrastructure.
If that subnet is listed, the connection dies before data leaves the browser — no matter which domain hosted the script.
That is why “another parameter on a strip list” undersells the release. It undermines a whole class of workarounds:
You can change a path. You cannot renumber Microsoft’s or LinkedIn’s ad server ranges.
One more finding, with caution: the analysis reports a category of domains hardcoded as unconditionally blockable regardless of user privacy settings. The mechanism is visible in code; the list contents live in an unpublished Apple file. Treat the mechanism as observed and the scope as unverified.
Safari’s privacy lists are not compiled into the browser binary. Click-ID filters, script classifications, and IP ranges live in a system library that can update without a Safari version bump. Devices can receive new rules silently.
Operational consequence: “Apple announced nothing about tracking this release” is not proof that nothing changed. Watch Safari-segmented conversion rates against Chrome — not Apple’s marketing notes.
Earlier layers targeted what scripts could read or store. Safari 27 targets where data can go.
gclid-only Safari attribution — argue for enhanced conversions
and server-side delivery, not a URL restructure.
bat.bing.com / Insight Tag endpoints for Safari to intercept.
LinkedIn CAPI (or equivalent) instead of relying on the Insight Tag alone; Microsoft Ads API paths instead of UET-only.
Safari 27 specifics above come primarily from WebKit source review of a developer beta, as reported across independent measurement coverage — not from Apple’s Safari 27 release notes. Verify against your own stack in beta before irreversible architecture bets. Trust the direction even when individual list entries shift.
Not via Link Tracking Protection — the five standard utm_* keys are not on that strip list.
A script classified under AFP may still be denied permission to read the query string.
Reportedly twclid, cn, cxt (X), si (YouTube), xmt (Threads),
on top of earlier coverage that includes gclid, fbclid and msclkid.
LTP applies in Private Browsing and to Mail/Messages links. As of Safari 26, ordinary sessions still passed click IDs. Users can opt in for all browsing via Advanced Tracking and Fingerprinting Protection.
Not against IP-level blocking. The proxy changes where the script loads from, not where the data must go.
It removes the surface those protections act on. The browser talks to you; your servers talk to the ad platforms.
Not because of Safari 27. Keep {lpurl} (or your redirect) in the template and UTMs in the Final URL suffix.
Invest in UTM quality, enhanced conversions, and server-side conversion APIs — not a new query-string fashion.