Safari Removes gclid & fbclid from URLs

Safari removes tracking parameters from links to strengthen privacy. Today, in Private/Incognito browsing, these identifiers are already stripped before they reach your site. With the upcoming mainstream Safari release, the same behavior is expected across all browsing modes — Safari removes click identifiers even for regular sessions, which impacts attribution and analytics by default.

Which identifiers are affected

Safari removes common advertising click IDs embedded in URLs. Examples by platform include:

• Google Ads / Google Analytics: gclid, gbraid, wbraid, legacy dclid
• Microsoft Advertising (Bing): msclkid
• Meta (Facebook / Instagram): fbclid
• Twitter / X Ads: twclid

The core impact remains: Safari removes recognized URL-level click identifiers that ad platforms use for measurement.

Why these parameters matter for marketers

Click identifiers connect ad clicks to on-site behavior (sessions, conversions, revenue, remarketing eligibility). They power precise attribution, feed automated bidding models, and reduce noise in cross-channel reporting. When Safari removes these parameters, client-side tags may never see the original click ID.

• Fewer conversions attributed to the correct channel or campaign
• Weaker automated bidding and budget allocation signals
• Smaller or incomplete remarketing audiences
• Wider deltas between ad platform reports and your analytics

What to do now (action plan)

• Evaluate Server-Side tracking with GTM Server
  If GTM is Client-side only, consider moving key conversions and events for Google Ads, GA4, and other ecosystems to a Server-Side setup to reduce reliance on URL tokens and implement robust fallbacks.
• Set up a backup parameter in Google Ads
  Add a custom final URL parameter and set its value to ={gclid}. This attempts to deliver the click ID twice — once via gclid and once via your custom backup parameter — so you still capture a value if Safari removes the original.
• Adjust the GTM Server “Query Replacer” (or equivalent)
  Update your Server-Side parsing to read the standard gclid first and fall back to the backup parameter. Apply the same pattern for other IDs (e.g., msclkid, fbclid) so downstream events remain enriched even when Safari removes the original identifier.