gclid (Google Click Identifier) is the parameter Google Ads adds to your landing page URL when someone clicks an ad, so a conversion that happens later can be tied back to that click. It’s Google’s counterpart to Meta’s fbclid: created by the ad platform, read by your landing page, sent back to the platform with the conversion.
How gclid gets into the URL
Google’s auto-tagging appends it to the URL people click through, so a final URL of www.example.com arrives as www.example.com/?gclid=123xyz. Auto-tagging is on by default for new accounts, and Google lists it as required if you want to track offline conversions.
The same help page has two details that matter as soon as you store the value:
- One gclid isn’t always one click. Google says the GCLID is sometimes created at impression time, and when the same person clicks the same ad again, the same GCLID is used. Don’t treat it as a unique key per click.
- Redirects have to carry it. If your link goes through a redirect, the gclid must reach the final landing page, or the conversion can’t be tracked.
Format
Google doesn’t publish a format for the value: its own example is the placeholder 123xyz. The one rule it does state is that the GCLID is case-sensitive. Store it as text, exactly as it arrived. No lowercasing, no trimming, and no CRM field that “normalises” what you paste into it.
Where you see it
| Place | What happens there |
|---|---|
| Landing page URL | auto-tagging appends gclid= to the URL of the click |
| Google Analytics cookie | with a Google Analytics tag installed, the GCLID is stored in a cookie on your own domain |
| Your form | Google’s offline-import setup adds a hidden form field for the GCLID, kept in a cookie or local storage until the form is sent |
| Your CRM | the field you upload from when the lead turns into a sale |
| Google Ads | the offline conversion import, which matches the conversion to the click |
How long Google accepts a gclid
What limits a gclid in practice is the conversion window of the conversion action you import into. Google lets you set it anywhere from 1 to 90 days, depending on the source of conversions, and uses 30 days if you don’t change it. A conversion that falls outside the window doesn’t count, however good the lead was.
For lead gen, set the window to match how long your leads really take to close. If your sales cycle runs past 90 days, no setting will cover it: import an earlier stage, such as a qualified lead, that does fall inside the window. For advertisers starting from scratch, Google now recommends enhanced conversions for leads, which match on hashed customer data, over a plain GCLID import (same offline conversions page).
On Meta, the click ID worth building on is the one you own. DropCPL logs every Meta ad click on your landing page’s own domain and joins each lead to its ad and its spend. Start free →
gclid vs fbclid
| gclid | fbclid | |
|---|---|---|
| Added by | Google Ads auto-tagging | Meta, when someone clicks an ad |
| Case-sensitive | yes | yes |
| Goes back to the platform via | an offline conversion import | the fbc parameter of a Conversions API event |
| Cookie the platform describes | a Google Analytics cookie on your domain | _fbc, with a recommended 90-day expiry |
Meta’s side comes from its fbp and fbc reference, which builds fbc as version.subdomainIndex.creationTime.fbclid. If you need to turn an fbclid into that value, the fbclid parser does it for you.
Where your own click ID fits
Platform IDs are return addresses: you keep them so you can send a conversion back to the platform that issued them. They make poor primary keys. A gclid can be shared by repeat clicks, exists only for Google traffic and disappears if a redirect drops it. The key you join leads on should be a click ID you generate yourself, one per click, recorded on your server.
DropCPL works with Meta only and doesn’t connect to Google Ads. On Meta traffic it records its own click_id next to the ad_id, campaign_id and fbclid, in a first-party cookie set on the landing page’s domain in the same response that renders the landing page.
Related terms
- fbclid: Meta’s equivalent
- gbraid and wbraid: what Google sends instead on some iOS clicks
- msclkid and ttclid: the Microsoft and TikTok versions
- Tracking identifiers: click ID, UTM and first-party cookie compared