The gclid (Google Click Identifier) is the Google Ads click ID. With auto-tagging enabled, Google appends it to every destination URL so a later conversion can be matched to the exact ad click.
How does the gclid work?
When someone clicks your search ad, Google generates a unique value and adds it to your landing page URL:
https://example.com/offer?gclid=Cj0KCQjw8eOLBhC1ARIsAOzx5cG...
The Google tag reads the value and stores it in a first-party cookie. When the visitor later submits a form or buys something, the conversion is reported to Google Ads together with the gclid. Google can then tie it to the campaign, ad group, keyword and time of the click.
Besides the gclid there are more Google parameters: gbraid and wbraid for iOS traffic under App Tracking Transparency, gad_source with information about the ad source, and dclid for Display and Campaign Manager clicks.
Why does the gclid matter?
The gclid is the backbone of conversion tracking in Google Ads. Without it, conversions are matched less reliably and Smart Bidding gets fewer signals. Common reasons gclids go missing:
- Redirects that drop query parameters
- Forms or checkouts on a different domain
- No consent, so the cookie is never set
- Cookie lifetime caps from Safari ITP
Enhanced Conversions let you send hashed email addresses or phone numbers along with the conversion. That helps Google match conversions even when the gclid is missing.
The gclid does not replace UTM parameters. Most advertisers use both: the gclid for Google, UTMs for their own reporting.
gclid with LeadSignal
LeadSignal captures the gclid plus gbraid, wbraid, gad_source and dclid automatically and stores them with the session. For Google Ads, LeadSignal uses the Google tag (gtag) in the browser, including Google Consent Mode v2 and Enhanced Conversions. Server-side forwarding to Google Ads is not available at the moment. In the lead list you see each lead's gclid, source and landing page.
Learn more about the setup on our Google Ads integration page.