Mastering GCLID Tracking in Google Ads: A Complete Information Resource

Today’s Marketing world is pure magic. Consider all the ways you can engage with your potential customers through different channels with different messaging and types of content – it is gold for your lead generation. Gone are the days when a single campaign in a traditional medium would suffice, this could be a disaster for today’s marketing realm and a waste of money. Statistically, the average customer uses 8 different touchpoints before making a purchase.

But why do we talk about touchpoints and leads in a GCLID article? All these wouldn’t matter if you couldn’t measure and record all these touchpoints to optimize your marketing performance and budget. For me, driving money and sales to your business sometimes it can be easier than knowing what made each sale happen.

What is a GCLID or Google Click Identifier?

GCLID stands for Google Click Identifier, a unique string of letters and numbers that Google Ads appends to your destination URL every time someone clicks one of your ads. The whole point of the GCLID is to give Google a key it can use later to look up exactly which campaign, ad group, keyword, ad creative, device, and audience produced that click. When a conversion happens, you (or Google) send the GCLID back, and the conversion is attributed to the right ad. No GCLID, no granular attribution.

If you run Google Ads and you care about anything more granular than “campaign-level” reporting, GCLID is the mechanic that makes it work. It’s also the foundation underneath Enhanced Conversions for Leads, offline conversion imports, and call attribution. if you’re trying to attribute calls back to ads, that workflow leans heavily on GCLID.

What does a GCLID actually look like?

A GCLID is an opaque, base64-style string of roughly 60–100 characters. It looks like this in a URL:

https://yoursite.com/landing?gclid=Cj0KCQjw1OmoBhDXARIsAAAAAA…AAAAAA

Two things are worth noting about the string itself:

• It’s not human-readable. You can’t decode it on your end. Only Google’s systems can resolve it back to a campaign, keyword, or ad.
• The full attribution data: campaign ID, ad group, keyword, device, geo, audience, lives in Google’s own database. The GCLID is just a key. Your job is to capture it and pass it back when something converts.

How GCLID actually works (the full lifecycle)

A GCLID has a four-step lifecycle: it’s generated, it’s appended, it’s captured, and it’s returned. Each step has its own gotchas.

1. Generated. Google Ads creates a unique GCLID for every ad click, the moment that click happens. It’s deterministic per click and globally unique.
2. Appended. Google Ads adds the GCLID to the destination URL as a query parameter — but only if auto-tagging is enabled on your account. (More on this in the setup section below.)
3. Captured. The landing page — or, more reliably, your tag manager, CRM form, or call tracking script — reads the GCLID out of the URL and stores it against the visitor’s session. Session-level capture lets you associate later conversions (a form fill, a phone call, a purchase) with the original click.
4. Returned. When a conversion happens, the GCLID is sent back to Google — either via the conversion tracking pixel on the landing page, an Offline Conversion Import from your CRM, or an API call. Google then matches the returned GCLID to its record of the click and credits the right campaign, ad group, and keyword.

The most common attribution failure is step 3: the visitor lands, the GCLID is in the URL, but nothing on the page stores it. They come back two days later and fill out a form, without the GCLID. Google has no way to connect the two visits, and the conversion gets attributed to “direct” or “organic” instead of paid search.

GCLID example

Here is a simple example: I used the term “monday.com alternative”

Then I clicked on the first result on ClickUp’s Campaign.

Now, ClickUp knows the campaign, the ad group, the ad I clicked, the keyword I used, and the landing page I visited.

If I continue my research and come back to clickup, 10 days later, to register using another keyword and clicking in another campaign (e.g. Branded campaign), this info will be added to my previous behavior building my path.

What GCLID lets you resolve

GCLID itself doesn’t carry data; it’s a pointer. When you send it back to Google with a conversion, you get attribution to all of the following dimensions, depending on the campaign and ad type:

• Source and medium (google / cpc, google / cpv, etc.)
• Campaign and ad group the click came from
• Keyword (for search campaigns) — the exact term the user typed, or the keyword that triggered the ad
• Match type (exact, phrase, broad)
• Ad creative — headline and description variant clicked
• Device (desktop, mobile, tablet)
• Ad network (Search, Display, YouTube, Discovery, Shopping)
• Placement (for Display Network — the site or app the ad ran on)
• Ad position / slot (limited reporting; Google has deprecated some of this)

Crucially: none of this is encoded in the GCLID string itself. It’s all looked up in Google Ads’s database using the GCLID as the key. You can pull these dimensions in the Google Ads UI, in Looker Studio, in the Google Ads API, and inside reports that import GCLID-tagged conversions back from a CRM or call tracking system.

GCLID vs UTM: what’s the difference?

This is one of the most-asked questions on the keyword (it’s in Google’s People-Also-Ask box), and the short answer is:

• UTM parameters are something you set manually on your URLs to label traffic from any source – newsletters, partner sites, organic social, billboards. They’re human-readable (utm_source=newsletter, utm_campaign=spring_sale) and they’re platform-agnostic – every analytics tool (GA4, Mixpanel, Amplitude, etc.) reads them.
• GCLID is something Google sets automatically on Google Ads clicks. It’s opaque, it’s only readable by Google’s systems, and it ties to Google’s own ad-server database – meaning it can resolve back to ad-level data that UTMs cannot (keyword, match type, device, audience).

In practice, you use both. UTMs label traffic across all your sources; GCLID layers in Google-Ads-specific attribution on top of paid search and YouTube. Most call tracking and analytics setups capture both.

How to set up GCLID tracking in Google Ads in 3 steps

Step 1/ Turn on auto-tagging

Auto-tagging is the single setting that makes GCLID work. Without it, Google Ads won’t append GCLIDs to your destination URLs, and you’ll only have UTM-level attribution at best.

1. Sign in to your Google Ads account.
2. Go to Admin → Account settings.
3. Expand the Auto-tagging section.
4. Check “Tag the URL that people click through from my ad,” then Save.

Auto-tagging is off by default for some legacy accounts. If you’ve inherited a Google Ads account, check this first — it’s the most common reason GCLID-based reporting is missing from setups that otherwise look fine.

• Expand the “Auto-tagging” section, check the box and save your changes.

Step 2/ Make sure your URLs are compatible

A few practical things to check before you turn auto-tagging on in a live account:

• Use the Final URL field rather than manually appending tracking parameters to ad URLs. Manual parameters can collide with the auto-tagged GCLID.
• Check your URL rewrite rules — some CDNs and WAFs (particularly aggressive Cloudflare configurations) strip unknown query parameters. The GCLID is unknown to them. If it’s being stripped, conversions break.
• Check your analytics filters — some GA4 setups exclude unknown query parameters. Make sure ?gclid is in the allowed list.

Step 3/ Capture the GCLID on your landing page

This is where most setups fall apart. Auto-tagging appends the GCLID; capturing it is your responsibility.

Three places worth capturing it:

• Form hidden field. Add a hidden input named “gclid” to every form, populated by a small script that reads the GCLID out of the URL on page load. When the form submits, the GCLID rides into your CRM.
• Cookie or localStorage. Store the GCLID for the full session (and ideally for 90 days, the lifetime Google honors for offline conversion imports). This lets you capture conversions that happen on a different page than the landing page.
• Call tracking dynamic number insertion (DNI). If a visitor calls instead of filling a form, your call tracking platform’s DNI script reads the GCLID from the URL, swaps the displayed phone number, and ties the inbound call back to that GCLID. This is the only way to get call attribution at GCLID granularity. 

Most CRMs and call tracking platforms have prebuilt scripts for this. In Nimbata, the same DNI script that swaps the number also captures GCLID, GBRAID, WBRAID, GA4 client_id, and all UTM parameters in one shot. See Nimbata’s Google Ads integration for the setup.

Step 4/ Send the GCLID back when a conversion happens

Three patterns, depending on where the conversion lives:

• Website conversion (form fill, signup, purchase). The Google Ads conversion tag on your thank-you page sends the GCLID automatically from the same browser session — no extra work.
• Offline conversion (lead becomes a customer days later). You export the lead + GCLID + conversion timestamp from your CRM, then import it back into Google Ads via Offline Conversion Import. Google matches the GCLID to the original click and credits the right campaign. The GCLID is valid for 90 days for this purpose.
• Call conversion (visitor calls and converts). A call tracking platform captures the GCLID at the moment of the call, pairs it with the call outcome (qualified lead, booked appointment, sale), and pushes the conversion back to Google Ads. This is where most marketers leak revenue: phone calls account for 30–60% of high-ticket B2B conversions, and without GCLID-tied call tracking, those calls show up as “direct” or “unattributed.”

How Google Click Identifier (GCLID) can help you:

1. Accurate Attribution: GCLID allows for accurate attribution of clicks and conversions to specific campaigns, ad groups, keywords, and ads. This level of granularity helps marketers understand which elements of their campaigns are driving results and enables data-driven decision-making.
2. Enhanced Performance Analysis: By tracking GCLID data, marketers can analyze the performance of their campaigns at various levels, including campaign, ad group, keyword, and ad content. This analysis provides insights into which components are performing well and which may require optimization, leading to improved campaign performance.
3. Conversion Tracking: GCLID enables marketers to connect user actions, such as form submissions, purchases, or other desired actions, back to the specific ad click that initiated the conversion. This information helps measure the effectiveness of ad campaigns in driving desired outcomes.
4. Improved ROI: By tying specific clicks and conversions to ad spend, they can determine the effectiveness and profitability of their advertising efforts, allowing for better budget allocation and optimization.
5. Data-Driven Optimization: By analyzing the performance of different campaign components and identifying patterns and trends, marketers can optimize their targeting, ad content, bidding strategies, and other factors to maximize campaign success and achieve better results.
6. Offline Conversion Tracking: GCLID can be utilized to track offline conversions, which occur when a customer takes a desired action, such as making a purchase, completing a form, or requesting more information, through channels outside of the online environment.
   By incorporating GCLID into offline conversion tracking systems, businesses can connect offline customer interactions or purchases back to the specific online ad click that influenced the conversion. This attribution helps marketers understand the full impact and effectiveness of their online campaigns in driving offline results.

gbraid and wbraid: GCLID’s iOS replacements

In iOS 14+ Apple’s App Tracking Transparency (ATT) framework limits the cross-app tracking that GCLID historically relied on. To preserve attribution in that environment, Google introduced two parallel identifiers:

• gbraid: used when an app-to-web click can’t carry a GCLID (typical for iOS users with ATT denied).
• wbraid: used when a web-to-web click on iOS Safari can’t preserve cookies the way it could pre-ITP.

Practically: in a modern setup you capture all three (GCLID, gbraid, wbraid) and pass whichever one is present back with the conversion. Google’s Offline Conversion Import API accepts all three. Most modern call tracking platforms (Nimbata included) capture them automatically, but if you’re still on a 2022-era setup that only captures GCLID, you’re losing attribution on every iOS user who calls.

GCLID and Consent Mode v2 (EU + UK advertisers, read this)

As of March 2024 Google requires Consent Mode v2 for any EU/EEA or UK Google Ads campaign that uses audience features or personalized advertising. Consent Mode v2 changes how GCLID flows when a user denies analytics or ad-storage cookies:

• If consent is granted → GCLID flows normally, conversions are attributed at full granularity.
• If consent is denied → Google receives an “unconsented” signal and uses modeled conversions instead of GCLID-matched ones. Conversion volume drops modestly, but campaign-level reporting still works.
• If Consent Mode v2 isn’t implemented at all → audience features may stop working entirely, and modeled conversions aren’t available as a fallback.

If you advertise into the EU and your conversion volume has been odd since spring 2024, this is the first thing to check. Your consent management platform (CMP) needs to be Google-certified and the gtag/GTM consent signals need to be wired correctly.

How GCLID powers call attribution (the part most articles skip)

Phone calls are the conversion type GCLID was least designed fo, but the workaround has become standard practice and is the angle most generic GCLID articles miss.

The pattern looks like this:

1. A visitor clicks a Google Ad. Auto-tagging appends the GCLID to the landing page URL.
2. Your call tracking platform’s DNI script reads the GCLID from the URL, swaps the displayed phone number to a tracking number unique to that visitor’s session, and stores the GCLID against the session.
3. The visitor calls the displayed number. The call routes to your sales team.
4. Your call tracking platform pairs the inbound call with the visitor’s stored GCLID. Now you have a call + GCLID pair.
5. Either: (a) you trigger an immediate Google Ads conversion using that GCLID at the moment the call connects, or (b) you wait until the call is qualified (the call tracking platform’s call scoring or AI summary tells you it was a real lead, not a wrong number) and then send the qualified conversion back. Check this article for how to trigger call conversions based on lead scoring.
6. Google Ads credits the right campaign, ad group, and keyword for the call.

Option (b) is what separates a serious call attribution stack from a basic one. Sending every inbound call as a conversion teaches Smart Bidding to optimize for more calls, not more qualified calls. Sending only qualified calls, based on call duration, AI conversation analysis, or CRM stage, teaches Smart Bidding to optimize for revenue. See how Nimbata stacks up against the other tools that do this in our CallRail vs Nimbata comparison.

Limitations and gotchas

• Google Ads only. GCLID is Google’s identifier. It doesn’t work for Meta, LinkedIn, TikTok, Microsoft Ads, or any other platform – each of those has its own click ID (FBCLID, LI_FAT_ID, ttclid, MSCLKID).
• Cookie-dependent (with caveats). Classic GCLID flows assume cookies. With Consent Mode v2 + Enhanced Conversions, modeled conversions can fill some of the gap when consent is denied, but raw GCLID-matched attribution still requires consent.
• 90-day validity for offline import. If you import a conversion more than 90 days after the original click, Google rejects it. Set up your CRM exports to fire on a fast enough cadence, daily is ideal.
• Easy to lose in URL handling. Aggressive URL rewriters, link shorteners, JavaScript redirects, and over-zealous CDN rules all strip GCLIDs. Test by clicking your own ads from incognito and inspecting the URL at every step.

Doesn’t survive cross-device journeys. If a visitor clicks an ad on mobile and converts on desktop, GCLID alone can’t connect the two. You need a logged-in user identity or Google Signals for cross-device – and even then it’s modeled, not exact.

Frequently Asked Questions about GCLID Tracking in Google Ads

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.