What a GCLID is
GCLID stands for Google Click Identifier. When someone clicks an ad, Google appends a parameter beginning gclid= to the landing page URL, carrying a code unique to that single click. The code itself is meaningless to you — it is a reference number, not readable data — but Google holds the campaign, ad group, keyword, device, location and time behind it.
The value of that reference is matching. When a conversion is reported back to Google carrying the same identifier, Google can attach the sale to the exact click that produced it without guessing. That is why it underpins conversion reporting, Google Ads to Analytics linking, and any upload of outcomes from a CRM.
Why the GCLID matters
It is the difference between measured attribution and inferred attribution. Referrer data and UTM tags tell you traffic came from Google; the identifier tells you which auction, which keyword and which ad. For accounts where a handful of keywords carry the profit and the rest quietly drain it, that distinction decides where money goes next.
It also travels further than a website session. Because the identifier can be stored in a CRM record alongside the enquiry, a deal closed weeks later on the phone can still be sent back to Google Ads and credited properly. For businesses with long sales conversations — education consultancies, property, B2B services — that is often the only honest way to judge which campaigns actually produce customers rather than enquiries.
Where the GCLID goes wrong
It disappears easily. It exists only in the URL of the landing page, so any redirect that strips query parameters removes it, and so does a form that posts to a new page without carrying it through. Sites with an aggressive cache or a redirect from one URL shape to another are the usual culprits.
It is also privacy-limited by design. On traffic where cookies cannot be stored, or where the user journey crosses an app boundary, Google may send a different identifier instead, so a system built to expect only gclid will find blanks. And it is single-use context: an identifier from one click tells you nothing about a visitor’s later visits, so it is not a customer ID and should never be treated as one.
What to do about it
Leave auto-tagging switched on so the identifier is added consistently, and check that your redirects preserve query strings — a quick test is to add a dummy parameter to a landing page URL and see whether it survives the load. Store the identifier in a hidden form field so it reaches the CRM with the enquiry, and make the field wide enough that nothing is truncated.
Then decide what you want it for. If the aim is simply to see which campaigns convert on site, correct conversion tracking is enough. If the aim is to know which campaigns produce revenue, keep the identifier in your records and plan to send outcomes back. Either way, pair it with auto-tagging rather than hand-built tracking parameters.