Tracking Google Ads Without Losing GCLID

What GCLID Actually Does

GCLID stands for Google Click Identifier. It is a unique parameter Google appends to your landing page URL every time someone clicks one of your ads, provided auto-tagging is enabled on your account. A typical URL looks like this:

https://yourlp.com/?gclid=CjwKCAiA9vS6BhA9EiwAJpnXw...

Most advertisers treat GCLID as an attribution parameter. That is accurate, but it undersells what is actually at stake. GCLID is the primary signal feeding Google's Smart Bidding algorithms. When a conversion fires and Google can match it back to a specific GCLID, that match tells Smart Bidding which user profile, keyword, device, time of day, and auction context produced a conversion. This is the data the algorithm uses to adjust bids in real time.

When GCLID gets lost somewhere in your funnel, Smart Bidding does not just lose an attribution data point. It loses the learning signal it needs to optimise toward the right users. Over time, a campaign running on incomplete GCLID data will drift toward worse targeting, higher CPCs, and lower conversion quality. You will see it in performance eventually, but by then you have already been paying for it.

The Ways GCLID Gets Stripped

GCLID does not disappear due to a single obvious failure. It gets stripped quietly, in ways that are easy to miss until you specifically go looking.

Redirect Chains

This is the most common cause for anyone running traffic through a tracker. When you use redirect tracking, the click passes through your tracker's domain before reaching the landing page. If the tracker does not explicitly preserve all query parameters through the redirect, GCLID gets dropped at the redirect step. The user reaches the landing page. Your tracker logs the click. But the GCLID is gone, and Google cannot connect the eventual conversion back to the original ad interaction.

Voluum handles this correctly when you use their direct tracking method for Google campaigns. They specifically recommend against redirect tracking for Google Ads for this reason. The destination URL in your ad should point directly to the landing page, with tracking handled via the JavaScript snippet rather than through a redirect chain. ClickFlare follows the same approach.

If you insist on using redirect tracking with Google Ads, you need to verify that your tracker's redirect explicitly forwards the full query string to the destination. Not all do by default.

Parallel Tracking Misconfiguration

Google's parallel tracking is now the default and required method for Google Ads. Instead of the traditional flow where the user's browser hits your tracking URL first and then gets redirected, parallel tracking sends the user directly to the landing page while measurement happens in the background via a separate request. This is faster for the user and generally better for Quality Score.

The problem arises if your tracking setup was built around the old redirect model. If your campaign tracking template expects to intercept the click and then redirect, parallel tracking will bypass that interception entirely. The click still happens, but your tracker never sees it, and GCLID handling that depended on the redirect step breaks.

For Google Ads campaigns, direct tracking with a landing page script is the correct architecture under parallel tracking. The script reads GCLID from the URL on page load and stores it in a first-party cookie or passes it directly to your tracker via an async request.

Safari Link Tracking Protection

Apple added Link Tracking Protection to Safari in iOS 17 and macOS Sonoma. In Private Browsing and when links are shared via Mail or Messages, Safari strips known tracking parameters from URLs before the page loads. GCLID is on the list.

The practical impact depends on your audience. For consumer campaigns with significant iOS traffic, the share of clicks where GCLID is stripped by Safari can meaningfully affect your conversion signal quality. This is not something you can fix at the tracking layer. It is a platform-level restriction. The mitigation is Enhanced Conversions, which supplements GCLID with first-party hashed data to recover some of the attribution that Safari strips.

Auto-Tagging Disabled

If auto-tagging is turned off in your Google Ads account settings, GCLID will not be appended to any ad click URLs. This is less common as a silent failure because auto-tagging is enabled by default on new accounts, but it does get disabled accidentally during account migrations, when a third-party tool modifies account settings, or when someone troubleshooting a different issue turns it off and forgets to re-enable it.

Check it under: Google Ads > Admin > Account Settings > Auto-tagging. If the checkbox is unchecked, GCLID is not being generated at all, regardless of what your tracker or landing page does.

Configuring Your Tracker Correctly for Google Ads

The tracker sits between your Google ad and your conversion event, and how it is configured determines whether GCLID survives the journey.

The correct setup for Google traffic through a performance tracker:

1. Use direct tracking, not redirect tracking, for your Google campaigns. Set your final URL in Google Ads to point directly to your landing page. Use the Tracking Template field in Google Ads for your tracker's click logging URL, which runs in the background under parallel tracking without intercepting the user's navigation.
2. Pass GCLID explicitly through your tracker's token system. In Voluum, this means including {gclid} as a custom variable in your traffic source configuration. In ClickFlare, GCLID is captured via the Google Ads API integration and associated at the click level. Confirm your specific tracker's documentation for the correct token name.
3. Store GCLID in a first-party cookie on your landing page. Your LP script should read gclid from the URL parameters on page load and store it in a cookie with a 90-day expiry. This ensures GCLID is available for the conversion event even if the user navigates away and returns before converting.
4. Include GCLID in your postback or conversion upload. When the conversion fires, GCLID needs to be sent back to Google alongside the conversion event. If you are using Google's offline conversion import, GCLID is the primary matching key. If you are using server-side tagging or a conversion API integration, GCLID should be included in the event payload.

GBRAID and WBRAID: The iOS Replacements

For clicks from iOS devices where ATT opt-out prevents GCLID from being generated or passed, Google introduced two alternative identifiers: GBRAID (for app-to-web conversions from iOS) and WBRAID (for web-to-web conversions from iOS). These serve the same attribution function as GCLID but operate under Apple's SKAdNetwork and Private Click Measurement frameworks.

If you are seeing clicks where neither GCLID nor GBRAID/WBRAID are present, those clicks are coming from users where Google has no attribution pathway available. There is nothing to configure. The signal is gone at the source.

Voluum supports passing GBRAID and WBRAID via external ID tokens in their Google Ads traffic source template, so you can capture and log these identifiers alongside GCLID for clicks where they are available. Your postback URL should include all three as separate parameters, with your tracker recording whichever is present for a given click.

For the iOS attribution gap that none of these identifiers can cover, Enhanced Conversions with hashed email and phone data is the only practical recovery mechanism.

Verifying Your GCLID Setup

Do not assume GCLID is passing correctly because your conversion tracking shows numbers. Verify it explicitly before scaling spend.

The simplest test: append ?gclid=testvalue123 to your landing page URL directly in a browser and load the page. If GCLID disappears from the URL before the page finishes loading, something in your LP setup is stripping it. Check for JavaScript redirects, CMS URL normalisation, or redirect rules in your server configuration.

For end-to-end verification, click your own ad and check the URL that loads in the browser address bar. You should see gclid= followed by a long alphanumeric string. If you see the LP load without it, the parameter was stripped during navigation. Check your tracking template configuration in Google Ads, and verify that parallel tracking is correctly handling the background measurement request.

In your tracker, pull a report filtered to Google traffic and check whether GCLID is populated on click records. A meaningful percentage of clicks with missing GCLID values is a signal of a configuration problem, not normal behaviour. Some iOS gaps are expected. A 40% missing rate across all devices is not.

On the conversion side, check Google Ads > Tools > Conversions and look at the  "Conversion source" breakdown. Conversions reported as "Modeled" are estimates where Google could not match a GCLID. High modelled conversion percentages indicate your GCLID capture or forwarding is incomplete.

Enhanced Conversions: The Safety Net

Google Enhanced Conversions works alongside GCLID, not instead of it. The way it functions: when a user converts, you capture their email address or phone number from the form or checkout, hash it with SHA-256, and send it to Google alongside the conversion event. Google attempts to match the hashed identifier to a logged-in Google account, and where it succeeds, it can attribute the conversion even when GCLID was stripped or expired.

This is valuable specifically for the gaps GCLID cannot cover: Safari stripping, iOS opt-outs, cross-device journeys where the converting device is different from the one that clicked the ad, and conversions that happen more than 90 days after the click (after which GCLID expires regardless).

The key distinction is that Enhanced Conversions supplements GCLID coverage. It does not replace it. A campaign running on Enhanced Conversions alone, with no GCLID passing at all, is relying entirely on probabilistic matching. That is less accurate than deterministic GCLID matching and gives Smart Bidding a weaker signal. The right architecture runs both: GCLID where it is available, Enhanced Conversions filling the gaps where it is not.

For the implementation details across Google, Meta, and TikTok, how conversion APIs work covers the full picture.

Conclusion

Google Ads attribution is only as good as your GCLID chain. Every step where GCLID can get stripped, at the redirect, on the landing page, in the conversion postback, is a step where Smart Bidding loses signal and your reported data becomes less trustworthy. The fixes are not complicated, but they require explicit verification rather than assuming the default setup handles it.

For Google campaigns specifically: use direct tracking, confirm auto-tagging is enabled, verify GCLID persists on your landing page, and make sure your conversion events send GCLID back to Google. Treat GBRAID and WBRAID as supplementary signals for iOS traffic. Use Enhanced Conversions as the fallback layer for the attribution that deterministic GCLID matching cannot reach.

ClickPattern captures GCLID, GBRAID, and WBRAID automatically on every Google click and includes them in postback data for conversion attribution. If you want to see how the full setup works across your Google and other traffic sources, book a demo and we will walk through your specific configuration.