GCLID (Google Click Identifier) is a unique tracking string that Google Ads adds to your landing page address on every ad click. It lets a later conversion, such as a form fill, a purchase or a phone call, be credited to the exact campaign, ad group and keyword that produced the click.
What is a GCLID?
GCLID stands for Google Click Identifier. It is a long string of letters and numbers that Google Ads appends to your destination URL each time someone clicks one of your ads:
https://yoursite.com/landing?gclid=Cj0KCQjw1OmoBhDXARIsAAAAAA…AAAAAA
Two things to know about the string:
- You cannot read it. Only Google’s systems can turn it back into a campaign, keyword or ad.
- It is a key, not the data. The campaign, ad group, keyword, device and audience live in Google’s database. Your job is to capture the key and hand it back when something converts.
GCLID is what makes reporting below campaign level possible. It also sits underneath Enhanced Conversions for Leads, offline conversion imports and call attribution. If you are trying to attribute calls back to ads, that workflow depends on it.
How GCLID works
- Generated. Google Ads creates a GCLID for every ad click.
- Appended. Google adds it to the destination URL, but only if auto-tagging is on.
- Captured. Your tag manager, form or call tracking script reads it from the URL and stores it for the visit.
- Returned. When a conversion happens, the GCLID is sent back to Google, which matches it to the click.
Most failures happen at step 3. The visitor lands with a GCLID in the address, nothing stores it, and they come back two days later to fill in a form without it. Google cannot connect the two visits.
Here is what it looks like in practice. A search for “monday.com alternative” shows a sponsored result:

Clicking it opens the landing page with a gclid in the address:

From that one value the advertiser can look up the campaign, ad group, ad, keyword and landing page.
GCLID vs UTM: what is the difference?
| UTM | GCLID | |
|---|---|---|
| Who sets it | You, by hand or with a URL builder | Google Ads, automatically |
| Readable | Yes (utm_source=newsletter) | No (a string only Google can read) |
| Works across platforms | Yes, every analytics tool reads UTMs | No, only Google can resolve it |
| Detail | Whatever you label | Ad, keyword, match type, device |
| Best for | Labeling all your traffic | Tying Google Ads conversions back to ads |
Use both. Google Ads needs the GCLID to match a conversion to a click. UTMs are what everything else reads: your CRM, your call tracking reports and any tool that is not Google.
When Google Ads and GA4 are linked, GA4 reads the GCLID as well and fills in the campaign and keyword by itself, which is why its numbers can differ slightly from a report built on UTMs alone. Our guide covers GCLID vs UTM tracking in full.
How to set up GCLID tracking in Google Ads in 4 steps
Step 1: Turn on auto-tagging
Auto-tagging is the setting that makes GCLID work. In Google Ads, go to Admin, then Account settings, open Auto-tagging, check “Tag the URL that people click through from my ad” and save.

Google turns it on by default for new accounts, but it can be switched off. Check it first on any account you inherit.
Step 2: Make sure your URLs keep it
- Use the Final URL field, not tracking parameters added by hand, which can clash with the GCLID.
- Check that redirects and security rules do not drop query parameters.
- Check that nothing in your analytics setup excludes the gclid parameter.
Step 3: Capture the GCLID
Auto-tagging adds the GCLID. Storing it is your job. There are three places to do it:
- A hidden form field, filled by a small script, so the GCLID reaches your CRM with the lead.
- A cookie or local storage, so it survives across pages and return visits within the 90 days Google accepts.
- Dynamic number insertion, so a visitor who calls is matched too. In Nimbata the same script that swaps the number also captures GCLID, GBRAID, WBRAID and UTM parameters. See Nimbata’s Google Ads integration.
Step 4: Send it back when a conversion happens
- Website conversion: the Google Ads tag on your thank-you page sends it automatically.
- Offline conversion: export the lead, its GCLID and the conversion time from your CRM and import it into Google Ads.
- Call conversion: your call tracking tool pairs the call with the stored GCLID and sends the conversion.
gbraid and wbraid: the click IDs for iOS traffic
Apple’s App Tracking Transparency rules, introduced with iOS 14.5, limit how a click can be tied to a person across apps and websites. For that traffic Google uses two other identifiers alongside the GCLID:
| Parameter | When Google sends it |
|---|---|
| gclid | The standard click ID on ad clicks, when auto-tagging is on |
| wbraid | When someone clicks an ad inside an iOS app and lands on your website |
| gbraid | When someone clicks an ad on the web and is taken to your iOS app |
They are not replacements for the GCLID. Capture all three and send back whichever is present. If more than one is present, Google uses the gclid first, then the wbraid, then the gbraid. See our guide to GBRAID and WBRAID.
GCLID and consent
In the EU, EEA and UK, Google requires Consent Mode v2 for campaigns that use audience features or personalized advertising. It changes what happens to the GCLID:
- Consent granted: the GCLID flows as normal.
- Consent denied: Google uses modeled conversions in place of GCLID-matched ones.
- Consent Mode not set up: audience features may stop working, and there is no modeled fallback.
How GCLID powers call attribution
- A visitor clicks an ad, and auto-tagging adds the GCLID.
- The call tracking script reads it, shows the visitor a tracking number of their own and stores the GCLID for the visit.
- The visitor calls that number.
- The call is paired with the stored GCLID.
- A conversion is sent to Google Ads, either when the call connects or, better, once the call is judged a real lead.
Sending every call teaches Smart Bidding to find more calls. Sending only qualified calls teaches it to find more customers. See our PPC call tracking guide, or how PPC call tracking software does it for you.
Troubleshooting: check it works, and what to do when it is missing
Three ways to test it:
- Click one of your own ads in a private window. The page address should end with a gclid parameter.
- Add a test value by hand. Open your landing page with
?gclid=test123on the end, then send a test form or call. The value should arrive with the lead. - Follow the redirects. If the address changes on the way, check the gclid is still there on the final page.
| Symptom | Likely cause | Fix |
|---|---|---|
| No gclid on any ad click | Auto-tagging is off | Turn it on in Admin, Account settings |
| gclid appears, then disappears | A redirect drops query parameters | Keep them in the redirect, or point the ad at the final address |
| On the landing page but not on the lead | The form or call script is not capturing it | Add a hidden field, or use a tool that stores it for the visit |
| Missing for some visitors only | They declined cookies, or an ad blocker removed it | Consent Mode and enhanced conversions recover part of this |
| Missing on iPhone traffic | Google sent a wbraid or gbraid | Capture all three parameters |
Limitations
- Google Ads only. Other platforms have their own click IDs.
- It depends on consent. Without it, matching falls back to modeled conversions.
- It expires. Imports are accepted up to 90 days after the click, or 63 days for enhanced conversions for leads.
- It is easy to lose in redirects and link shorteners.
- It does not cross devices. A click on mobile and a conversion on desktop cannot be joined by the GCLID alone.
Related guides:
Frequently asked questions about GCLID
What is a GCLID?
GCLID stands for Google Click Identifier. It’s a unique tracking string Google Ads appends to your destination URL on every ad click, used to attribute the click - and any subsequent conversion - back to the exact campaign, ad group, keyword, and ad creative.
What's the difference between GCLID and UTM?
GCLID (Google Click Identifier) and UTM (Urchin Tracking Module) parameters are both tracking mechanisms used in digital marketing, but they serve different purposes and are associated with different platforms.
GCLID is specific to Google Ads and is automatically generated for click and conversion tracking within that platform. On the other hand, UTM parameters are used across various marketing platforms to track and measure campaign effectiveness, allowing for a more granular analysis of traffic sources, mediums, and campaign performance.
How do I enable GCLID tracking?
In Google Ads, go to Admin → Account settings → Auto-tagging and turn it on. Then capture the GCLID on your landing pages (form hidden fields, cookies, or a call tracking script) and pass it back when a conversion happens.
Can Nimbata help me capture GCLID for calls?
Yes. Nimbata’s call tracking script reads the GCLID (plus gbraid, wbraid, UTMs, and GA4 client ID) from the URL, swaps in a unique tracking phone number, and pairs every inbound call with its source. When the call is qualified, Nimbata sends a conversion with the original GCLID back to Google Ads - closing the loop between ad click and revenue-generating call.
How do I find my GCLID?
Click one of your ads and look at the page address: the GCLID is the value after gclid=. To see it on a lead, capture it in a hidden form field or use a tracking tool that stores it for the visit.
Does GCLID work with offline conversions?
Yes. Store the GCLID with the lead, then send it back to Google Ads when the lead becomes a sale. Google accepts imports up to 90 days after the click.
Takeaway
GCLID is the plumbing under everything serious you do in Google Ads: Enhanced Conversions, Offline Conversion Import, audience matching, Smart Bidding optimization. Auto-tagging is one click; capturing and persisting the GCLID is where most setups break.
If your conversions are happening on the phone instead of in a form, GCLID still works, but only with a call tracking platform that captures it at the visitor’s session and pairs it with the inbound call. That’s the difference between Smart Bidding optimizing for “more calls” and Smart Bidding optimizing for “more qualified calls” and the difference between an ROAS that looks fine and an ROAS that’s actually true.





