Safari 26 Strips Your gclid: How to Save Attribution
Safari Link Tracking Protection now removes gclid, fbclid from URLs. Impact on Google Ads attribution and server-side solutions.
What Safari 26 Changes for Your Tracking
Safari’s Link Tracking Protection feature now removes tracking parameters from URLs before the page loads. The gclid (Google Ads), fbclid (Meta), ttclid (TikTok), and other click identifiers are automatically stripped. The browser considers these parameters as cross-site tracking vectors.
In practice, a user who clicks on your Google Ads ad from Safari arrives on your site without the gclid in the URL. Google Ads can no longer link that click to a potential conversion. Attribution collapses for all Safari traffic.
The Scale of the Impact
Safari represents approximately 20% of web traffic in Europe, and up to 30% on mobile. This means a significant share of your Google Ads and Meta conversions may no longer be attributed correctly.
UTM parameters (utm_source, utm_medium, utm_campaign) are not affected for now. Attribution in GA4 via UTMs therefore remains functional. But platform-side attribution — the one that feeds your bidding algorithms — is directly impacted.
Safari 26’s Advanced Fingerprinting Protection adds another layer by limiting client-side fingerprinting techniques, further reducing the ability of measurement tools to identify users.
Available Technical Solutions
The first line of defense is server-side capture of click identifiers. With a server-side GTM container, the gclid can be captured at the server level before Safari strips it, then stored in a first-party cookie. This approach is the most reliable because it operates upstream of the browser.
The second solution is Enhanced Conversions. By sending hashed user data (email, phone, address) with your conversions, you allow Google to match the click and the conversion without depending on the gclid. This method works even when the parameter has been stripped.
The third option is offline conversion imports. If your sales process includes a CRM step (call, meeting, signature), you can send conversions directly via the Google Ads API with the gclid stored server-side at the time of the initial click.
What to Implement Now
The immediate priority is to audit your Safari traffic share and estimate the volume of conversions potentially impacted. Cross-reference your GA4 browser reports with your Google Ads conversion data.
Then, deploying Enhanced Conversions is the most accessible quick win. Configuration in GTM takes a few hours and does not require server infrastructure. For maximum coverage, combine it with server-side tracking that captures gclid values before they are stripped.
Beyond Safari
This evolution is not isolated. Firefox already blocks third-party cookies. Brave has been stripping tracking parameters for years. The trend is clear: client-side ad tracking is gradually disappearing. Companies that invest now in server-side and enriched conversions are gaining a lasting head start.