GCLID (Auto-Tagging)

GCLID, short for Google Click Identifier, is a unique alphanumeric parameter that Google Ads automatically appends to a destination URL each time someone clicks one of your ads. It captures the click's specific attributes so Google can connect ad spend to outcomes in Google Analytics 4, in offline conversion imports, and in CRM systems.

How auto-tagging works

Auto-tagging is the mechanism that activates GCLID. When it is enabled in your Google Ads account settings, every ad click generates a new, distinct GCLID value. The parameter attaches to the landing page URL, producing a result such as https://example.com/contact?gclid=TeSter123ABC. Google Analytics 4 reads the value on page load and stores it with the session record, so any conversion that follows can be attributed to the correct campaign, ad group, keyword, match type, and device.

Each click produces its own GCLID. The same user clicking the same ad twice receives two different identifiers. This click-level granularity is what makes GCLID useful for bid optimization and reporting accuracy.

GCLID vs. UTM parameters: where the line runs

UTM parameters (such as utm_source, utm_campaign, or utm_medium) are written and maintained manually by the marketer. They work across any analytics platform and tag traffic at the campaign level. UTM parameters do not provide access to the click-level signals that Google Ads resolves via the GCLID — such as keyword, match type, or bid strategy. The GCLID is a unique identifier; those attributes are not encoded in the URL itself but mapped server-side by Google Ads. When both appear in the same URL, GA4 gives precedence to GCLID for Google Ads attribution. The two serve different purposes: UTM parameters suit cross-channel measurement; GCLID powers Google Ads-specific reporting and optimization.

The conversion ID is a separate concept. It identifies a conversion action type configured in Google Ads (for example, a form submission or a phone call event), not the individual click that preceded it. Mixing up the two leads to misdirected troubleshooting when conversion tracking gaps appear.

On iOS and app-based ad interactions where users have not consented to device-level tracking, Google Ads may use GBRAID or WBRAID as privacy-preserving alternatives. These parameters use aggregated rather than click-level attribution; a GCLID does not appear in those cases.

Application example

Example scenario (no actual customer data): A B2B services company runs a Google Search campaign. Their contact form includes a hidden field that captures the GCLID from the landing page URL at the moment a visitor arrives. When a sales representative closes a deal two weeks later, the GCLID stored in the CRM is exported and uploaded into Google Ads via the Offline Conversions import tool. Google Ads can now attribute that signed contract to the specific keyword, ad group, and campaign that generated the original click, giving the bidding algorithms revenue data rather than just form completions.

Privacy and Consent Mode

Google Ads appends the GCLID to the destination URL whenever auto-tagging is enabled — this happens at click time, regardless of the visitor's consent status. What consent controls is whether the value may be stored as a cookie and used for attribution. When a visitor declines consent, the GCLID cannot be stored or evaluated, and the click data for that session is unavailable for standard attribution. Google's Consent Mode addresses this by using modeled conversion data for non-consenting sessions, but modeled data carries less precision than a recorded GCLID match. Configuring Consent Mode correctly is therefore relevant to measurement accuracy as well as regulatory compliance.

For marketers linking Google Analytics 4 to their Google Ads account, activated auto-tagging is a prerequisite for the integration: without it, no GCLID is passed and the connection cannot function. When auto-tagging is enabled, the GCLID connection is what enables automatic import of post-click session data (such as engagement rate and pages per session) into the Ads interface, without any manual UTM configuration.

Why this matters for your reporting

Without GCLID, Google Ads can only attribute conversions that a tag fires for on-site, in the same session. The GCLID extends that window to offline outcomes such as signed contracts, phone-confirmed orders, and CRM-registered deals, by carrying the click identity into your own database and back into Google Ads. Feeding real revenue signals to Google's bidding algorithms changes what the system optimizes for in ways that on-site tag data alone cannot provide.

For a practical look at how to use conversion data to improve Google Ads campaign results, the article on Google Ads campaign optimization covers the setup and performance side.