Apple's Safari browser removes that code in certain situations. When it does, the conversion still happens, but Google Ads may never connect it to the ad that drove it. The result is under-reported conversions and bidding that learns from less data.
The good news: the problem is narrower than some headlines suggest, and there are practical fixes.
What Safari actually does
Apple's Link Tracking Protection removes known tracking parameters, including click IDs like Google's gclid and Meta's fbclid, from URLs. Apple has documented it applying in three places:
- Safari Private Browsing, where it's on by default
- Links opened from Apple Mail
- Links opened from Messages
In normal Safari browsing, it's off by default. Users can turn it on everywhere by going to Settings > Apps > Safari > Advanced and setting Advanced Tracking and Fingerprinting Protection to All Browsing.
There was a lot of alarm in mid-2025, when early iOS 26 test versions appeared to strip click IDs in normal browsing too. That change didn't make it into the final release. Apple's release notes for iOS 27, released September 14, 2026, also list no change to Link Tracking Protection. But Apple doesn't publish its full list of filtered parameters, and it could expand protection at any time, so it's worth preparing now.
What survives
Not everything is stripped:
- UTM parameters (
utm_source,utm_medium,utm_campaign) are generally kept, so channel reporting in GA4 still works. - GBRAID and WBRAID, Google's privacy-friendly identifiers used for iOS traffic, are reported to survive because they don't identify individual users.
So you'll typically still know a visit came from Google Ads. What you lose is the precise click-to-conversion link that the GCLID provides.
How much does it matter for you?
The impact depends on your audience:
- Share of Safari traffic. Check GA4 under Reports > Tech > Tech details, broken down by browser. Sites with heavy iPhone audiences are most exposed.
- Private Browsing usage. One GTM practitioner estimated in April 2026 that about 20% of Safari sessions use Private Browsing. Treat that as a rough guide, not a measured figure for your site.
- Email and SMS campaigns. Links opened from Apple Mail and Messages are affected, which matters if you send paid traffic through those channels.
- Your conversion setup. Accounts that rely only on the GCLID, without enhanced conversions or offline conversion imports, feel the loss most.
Five ways to protect your data
1. Turn on enhanced conversions. Enhanced conversions send hashed, consented first-party data, such as an email address from a checkout, alongside your conversion. Google can then match conversions even when the GCLID is missing. Google's own guidance is to send all relevant conversion data even when you don't have a GCLID. For most advertisers, this is the single most effective fix.
2. Use the GCLID restore workaround. A community workaround, popularized in 2026, passes the click ID through a second, custom parameter that Safari doesn't recognize:
- In Google Ads, set an account-level final URL suffix of
lnid={gclid}. - In GTM, add the community Restore GCLID template, configured to read the
lnidparameter and rebuild Google's_gcl_awcookie. - Fire it on all page views. It only writes the cookie when
ad_storageconsent is granted.
It's effective today, but it's a workaround, not an official Google feature. Apple could add the new parameter to its filter list, so monitor it.
3. Capture click IDs on your own server. Read click IDs from the landing page URL in your own code or a server-side GTM container, store them with the session or lead, and pass them into your CRM. That makes offline conversion imports far more reliable.
4. Keep UTM tags on every paid link. Google Ads auto-tagging doesn't need UTMs, but they're a valuable fallback for channel reporting in GA4 and other tools when click IDs disappear.
5. Measure the gap. Create a GA4 exploration of paid Google Ads sessions, broken down by browser and operating system, and compare Safari with Chrome over time. A widening gap between ad clicks and attributed conversions on Safari is your early warning that protection has expanded.
Test it yourself
The best way to know what happens to your links is to check:
- Build a test URL for your site with a dummy
gclidvalue and UTM tags. - Open it on an iPhone in a normal Safari tab, in Private Browsing, and from a Messages or Mail link.
- Look at the URL that actually loads, or check your server logs, to see which parameters arrived.
- Repeat after each major iOS update.
The bottom line
Safari's link tracking protection doesn't affect every visitor, but it does chip away at Google Ads conversion tracking, and Apple has shown it's willing to go further. Don't rely on the GCLID alone. Turn on enhanced conversions, consider the restore workaround, keep UTMs as a fallback, and watch the gap between Safari and other browsers. Building resilience now is much easier than diagnosing a sudden drop later.
Enhanced conversions, the GCLID restore workaround and server-side click ID capture all live in your tag setup. Our Google Tag Manager consulting service can put them in place and set up the Safari-versus-Chrome monitoring for you.
Sources: PPC Land: Safari is quietly killing your GCLID, and here is the fix · Improvado: iOS Link Tracking Protection, what gets stripped · AbleCDP: Does Safari strip click IDs?
