What Is GCLID? Storing the Google Ads Click ID in Your CRM
What is the Google Ads GCLID and how does it work? Auto-tagging, passing GCLID to forms and your CRM, GBRAID/WBRAID, UTM differences and fixing lost click IDs.
GCLID (Google Click Identifier) is the unique click ID that Google Ads adds to the landing page URL as a gclid parameter on every ad click. With the Google Ads GCLID, a conversion is tied to the right campaign, ad group and keyword. If you store the ID in your CRM, you can also report sales closed over the phone or at a clinic back to the ad.
In this post I explain how GCLID is created, how the auto-tagging setting works and how to carry the ID from the landing page to your CRM. Then I cover the GBRAID and WBRAID parameters on iOS traffic, the difference from UTMs and the places where GCLID gets lost most often.
How does GCLID work?
GCLID is generated by Google Ads when a user clicks a Google ad, and it is appended to the end of the final URL as a gclid= parameter. Once the site reads and stores this value, every later conversion can be linked to the same click.
According to Google’s definition, GCLID identifies the campaign and other attributes of the click for ad tracking and campaign attribution.[1] The same page also states that GCLID is required for Google Ads website conversion tracking.[1] In other words, GCLID is not an analytics add-on; it is the foundation of conversion measurement.
In an example click, a user clicks an ad pointing to www.example.com and the page opens as www.example.com/?gclid=123xyz.[2] Inside Google’s systems, this value is matched with the click’s campaign, ad and keyword information. The value itself does not contain a readable campaign name.
The layer that stores GCLID on the site is usually the Google tag. If you use Google Tag Manager, the Conversion Linker tag does this job and writes the click information to first-party cookies on the site’s own domain.[5] Google also notes that GCLID is sometimes created at the time of an impression rather than a click. In that case, if the same user clicks the same ad again, the same GCLID is used.[2]
If the site has a Google Analytics tag and auto-tagging is on, Google says GCLID is also stored in a Google Analytics cookie on the site’s domain.[2] Cost and campaign data sharing between Google Ads and GA4 relies on this link. In the click view report in Google Ads, multiple clicks by the same user on the same ad are counted as multiple clicks in the same GCLID row.[2]
This detail helps when you interpret CRM records. If you see the same GCLID on two different lead records, it is not always an error. The same person may have clicked the same ad several times and submitted two separate forms. Merging such records in the CRM and moving the sales stage forward on a single record gives you cleaner data than deleting them.
How do you turn on auto-tagging in Google Ads?
Short answer
How do you turn on auto-tagging in Google Ads?
Auto-tagging is turned on in your Google Ads account under Account settings in the Admin menu. In the Auto-tagging section, you check the box to tag the URL that people click through from your ad and save. According to Google, this setting is on by default for new accounts, but you should always check it on older accounts.
- Click the Admin icon in your Google Ads account
- Open the Account settings page
- Go to the Auto-tagging section
- Check the box to tag the URL that people click through from your ad
- Save and confirm the gclid parameter in the URL with a test click
Auto-tagging is the account setting that makes Google Ads add GCLID to the final URL automatically on every click. According to Google, the setting is on by default for new accounts.[2] It is also activated automatically when you create a new conversion action. If you use cross-account conversion tracking, you need to turn it on manually in each child account.[2]
Google lists the jobs that need auto-tagging: tracking website conversions on all browsers, importing data from external sources such as a CRM, and sharing data between Google Ads and Google Analytics.[2] The setting is also required for businesses that want to track offline conversions.[2]
There is one caveat. According to Google, a small percentage of websites don’t allow arbitrary URL parameters and serve an error page when auto-tagging is on.[2] That is why it matters to click your own ad after turning the setting on and confirm that the page loads correctly.
What is the difference between GCLID and UTM parameters?
The core difference is that GCLID is an ID Google Ads generates automatically for every click, while UTMs are readable campaign labels you write by hand. The two solve different problems and do not replace each other.
GCLID (auto-tagging)
- A unique ID for every click
- Added automatically by Google Ads
- Only Google systems can decode the value
- Required for conversion tracking and offline imports
- Matches at keyword and ad level
UTM parameters (manual tagging)
- A shared label at campaign level
- Written by hand by the advertiser
- Source, medium and campaign name are readable
- Also used in analytics tools outside Google
- Does not distinguish individual clicks
Google states that in GA4 auto-tagging takes priority over manual tagging and that there is no option to override this.[2] So if a click carries both GCLID and UTMs, GA4 takes the Google Ads source information from GCLID. I still add UTMs, because the CRM and other tools need readable source information. But I don’t treat UTMs as a substitute for GCLID.
Meta has a similar click ID: fbclid. I covered it and server-side matching in my Meta Conversions API post.
How do you pass GCLID from a form to your CRM?
Short answer
How do you pass GCLID to a CRM?
To pass GCLID to your CRM, you read the ID from the URL on the landing page and store it in the browser. Then you add a hidden field to every lead form and write the stored value into that field when the form is submitted. Finally, you create a separate GCLID field on the CRM lead record and keep the incoming value there.
- Read the gclid parameter from the URL on the landing page
- Store the value in a cookie or localStorage with an expiry date
- Add a hidden gclid field to every lead form
- Write the stored value into the hidden field when the form is submitted
- Create a separate GCLID field on the CRM lead record and save the value there
Google’s offline conversion guide splits this work into three parts: adding a field that carries GCLID to every lead form, running a script on all pages that captures and stores GCLID, and keeping GCLID with the lead information in your lead management system.[3] The sample script Google suggests stores the ID in the browser so that it stays valid for 90 days.[3]
The script must run on every page of the site, not only on the landing page. Google strongly recommends this to avoid missing conversions.[3] A user lands on a service page from an ad, browses a few pages and fills in the form on a different page. If the ID is read only on the landing page, it gets lost on that journey.
The simple example below shows the logic. In production you need to adapt it to your consent management platform (CMP) and your own form structure:
<!-- Hidden field on every lead form -->
<input type="hidden" name="gclid" id="gclid_field" value="">
<script>
(function () {
var p = new URLSearchParams(window.location.search);
var ids = ['gclid', 'gbraid', 'wbraid'];
var ttl = 90 * 24 * 60 * 60 * 1000; // 90 days
ids.forEach(function (k) {
var v = p.get(k);
if (v) localStorage.setItem(k, JSON.stringify({ v: v, exp: Date.now() + ttl }));
});
window.addEventListener('load', function () {
var rec = JSON.parse(localStorage.getItem('gclid') || 'null');
var field = document.getElementById('gclid_field');
if (field && rec && Date.now() < rec.exp) field.value = rec.v;
});
})();
</script>
The example also stores GBRAID and WBRAID, because GCLID does not always arrive on iOS traffic. You can extend the form’s hidden fields for these values as well. Do not transform the value when you write it: according to Google, GCLID is case sensitive.[3]
- Create the CRM fields
Add separate text fields for GCLID, GBRAID and WBRAID to the lead object. These should not be fields the sales team can edit.
- Map the form
Map the hidden fields in your form tool to the new CRM fields. If the form sits inside a third-party iframe, you need to pass the value into the iframe with a URL parameter.
- Store the submission time
Save the lead creation time with its time zone. In offline imports, the conversion time must be after the click and must include a time zone.
- Define the stages
Tie the stages you will send back, such as qualified lead, appointment or sale, to clear statuses in the CRM. Each stage becomes a separate conversion action in Google Ads.
- Test the first import
After creating the new conversion action, wait a few hours, then run a first upload with a small number of records and check the error report.
According to the Google Ads API documentation, the conversion time must be after the click time and must include a time zone in the yyyy-mm-dd HH:mm:ss+|-HH:mm format.[4] Google recommends waiting 4-6 hours after creating a new conversion action before uploading. Conversions uploaded in the first 4-6 hours may take 2 days to appear in reports.[3]
I walked through the full offline import, including conversion actions, the Data Manager connection and stage selection, step by step in my health tourism offline conversions post. For setting up conversion tags on the website, see my Google Ads conversion tracking guide.
When do GBRAID and WBRAID arrive instead of GCLID?
GBRAID and WBRAID are click parameters added to the URL instead of, or together with, GCLID when users move between the web and apps on iOS devices. The Google Ads API documentation separates them by direction.[4]
- GBRAID: The parameter present in the URL when a user clicks an ad on the web and is directed to your iOS app.[4]
- WBRAID: The parameter present in the URL when a user clicks an ad in an iOS app and is directed to your web page.[4]
In practice, WBRAID directly affects most businesses with a website. When a user sees your ad in an iOS app and comes to the site, the URL may not contain GCLID. If your form only listens for the gclid field, that lead lands in the CRM without an ID.
When a conversion carries more than one ID, the Google Ads API uses gclid first, then wbraid, then gbraid, and recommends sending every ID you captured.[4] According to the documentation, if wbraid or gbraid is sent without gclid, user identifiers (such as a hashed email) are ignored.[4] That is why storing all three parameters in separate fields is the safest approach.
Why does GCLID get lost and how do you check it?
GCLID usually gets lost at a technical step between the click and the form: a redirect drops the parameter, the server strips unknown parameters, or the tag that stores the ID never fires. Once you find where it is lost, the fix is often a single setting.
Google stresses that if your site uses redirects, you must make sure GCLID is passed to the final landing page.[2] These are the loss points I see in practice:
- Redirect chain. An
http→https,wwwor language redirect drops the query parameter. - Settings that clean parameters. Cache plugins, CDN rules or “clean URL” settings delete unknown parameters.
- Reading on a single page. The script runs only on the landing page, while the form is on another page.
- Form inside an iframe. A third-party form tool can’t access the page’s cookie or localStorage.
- Tags that don’t fire without consent. When cookie consent is not given, the tag that stores the ID does not fire.
- Wrong field mapping. The hidden field arrives filled, but it is not written to any field in the CRM.
The last two points matter in Turkey in particular. GCLID on its own is not a name or an email address. But once it is combined with a person’s record in the CRM, it can fall within the scope of personal data. Google also reminds you to observe local cookie consent rules when storing GCLID.[3] I covered the consent setup in my Consent Mode v2 post.
The fastest way to check the whole chain is to click your own ad and trace the ID at every step:
If you are thinking about moving to server-side measurement, you can find ways to store the click ID with less exposure to browser restrictions in my server-side tracking post.
Conclusion
GCLID is the link between a Google Ads click and a real business outcome. Auto-tagging creates the ID. But carrying it from the landing page to the form, and from the form to the CRM, is the job of your own setup. If the ID is written to the right field at submission time, you get a solid base for offline conversions, lead quality analysis and value-based bidding.
To start, click your own ad and follow the gclid value in the URL all the way to the CRM record. The first step where it disappears is the place you need to fix. You can see how I combine measurement with campaign management on my performance marketing page, and my background on the about page.
Key terms
- Auto-tagging
- Auto-tagging is a Google Ads account setting that automatically adds the GCLID parameter to the final URL on every ad click. Website conversion tracking, offline conversion imports and the Google Analytics integration all rely on this setting.
- GBRAID
- GBRAID is a click parameter present in the URL when a user clicks a Google ad on the web and is directed to an iOS app. In the Google Ads API it is one of the click identifiers accepted alongside GCLID and WBRAID when uploading offline click conversions.
- WBRAID
- WBRAID is a click parameter present in the URL when a user clicks a Google ad in an iOS app and is directed to a web page. When a conversion carries more than one identifier, the Google Ads API uses WBRAID after GCLID and before GBRAID.
Frequently asked questions
What is GCLID used for?
GCLID is a unique identifier that describes a Google Ads click together with its campaign, ad group and keyword information. Google Ads uses it to link website conversions to the right click. If you store the same ID in your CRM, sales that happen later can also be sent back to the ad as offline conversions.
How do I turn on GCLID in Google Ads?
GCLID is turned on with the auto-tagging setting in your Google Ads account. In the Admin menu, under Account settings, the Auto-tagging section must have the box for tagging the URL that people click through from your ad checked. According to Google, this setting is on by default for new accounts.
What is the difference between GCLID and UTM parameters?
GCLID is an identifier that Google Ads generates automatically for every click and that only Google's systems can decode. UTM parameters are readable labels for source, medium and campaign name that you write yourself. GCLID is required for conversion tracking and offline imports, while UTMs provide readable source data in other analytics tools.
What should I do if GCLID does not appear in the URL?
First check that auto-tagging is turned on in Google Ads. Then open the ad's final URL and see whether any redirect strips the parameter. On iOS traffic, GBRAID or WBRAID may arrive instead of GCLID, so your forms and CRM should store those parameters too.
How long should GCLID be stored?
The sample script Google suggests stores GCLID in the browser so that it stays valid for 90 days. In the CRM, keep the ID with the lead record in a separate field that is not deleted during your sales cycle. Set the retention period in line with your privacy notice under KVKK or any other data protection law that applies to you.
Sources
The full topic: Google Ads guide ↗ · Tracking guide ↗