GCLID: the data you only capture once

A new campaign goes live on Google Ads. The first clicks arrive, the forms start being filled out, the cost per lead shows up in the dashboard, and everything seems to be working. Two weeks later, someone in sales asks which campaign brought in the contract that just closed. And there is no answer, because the data that would link that click to that contract was never stored.

That data is the GCLID. It is visible in the URL of any paid click, lasts as long as a session, and, if nobody captures it at that moment, disappears forever. It is a hidden form field, a few minutes of setup, and it is what separates the operation that measures closed deals from the one that measures filled-out forms.

What the GCLID is

GCLID stands for Google Click Identifier. When someone clicks an ad and the account has auto-tagging enabled, Google adds a parameter to the destination URL, something like ?gclid=Cj0KCQjw... followed by a long string of characters. That code identifies that specific click: which campaign, which ad, which keyword, on which device.

There is a distinction worth making that confuses many people. The UTM is what you declare about the campaign. You write it, you standardize it, you get it wrong when you type facebook in one campaign and fb in another. The GCLID is what Google records about the click, and it is generated automatically, with no chance of a typo.

Another important difference: the GCLID only appears on paid Google Ads clicks with auto-tagging on. It does not appear in organic traffic, in shared links, or in email. This is different from Meta's fbclid, which the platform also attaches to links from organic posts and Messenger. In practice, if there is a GCLID on that lead, it was a paid click. No exceptions.

Why it only exists once

Here is the point that makes this subject urgent and not merely important.

The GCLID lives in the URL of the session in which the person arrived. If the form does not have a hidden field recording this value along with name, email, and phone at the time of submission, it disappears when the tab closes. There is no way to recover it later from the lead's email, there is no Google Ads report that returns the code associated with a contact, there is no plan B.

And even those who capture it correctly are working against the clock: the Google Ads Help Center states that the GCLID is kept for only 90 days. After that period, the conversion upload is rejected with a warning that the click is too old.

For an operation with a short sales cycle, this goes unnoticed. For consultative sales, with proposals and negotiation, 90 days is a deadline that is easily reached. That is why it makes sense to send intermediate funnel milestones, such as a qualified lead or a meeting held, and not wait for the contract signature.

What Google Ads learns when the data does not exist

Without the GCLID stored, Google Ads sees only one thing: the form was submitted. It does not know whether that contact became a meeting, a proposal, or a customer. And since Smart Bidding optimizes for what it can measure, it starts chasing the highest possible volume of forms.

The problem is that the keyword that generates the most forms is rarely the one that generates the most revenue. Generic terms tend to convert cheaply and qualify poorly. Specific terms tend to cost more and close better. When the algorithm only sees the form, it invests in the first group and reduces the second, and the account looks healthy while the pipeline does not keep up.

This damage does not show up in any campaign report. It shows up in the revenue conversation at the end of the quarter, when the cost per lead is great and the revenue did not come along with it.

What changed in 2026

For years, the GCLID was the sole key of offline attribution: you stored the code, sent it back to Google when the lead changed stage in the funnel, and that was it.

That design has changed. Google began recommending Enhanced Conversions for Leads, which use the GCLID and the customer's own hashed data, such as email and phone, as matching keys. The practical advantage is redundancy: when the GCLID is lost along the way, the hashed email still allows the conversion to be tied to the original click. According to the Google Ads documentation itself, advertisers who used first-party data together with the GCLID saw a median 10% increase in measured conversions compared with traditional offline import.

Along with this came an infrastructure change: on June 15, 2026, uploads of offline conversions and Enhanced Conversions for Leads were migrated to the Data Manager API and blocked in the Google Ads API. Those who had an integration built before that had to change the upload path.

One detail that goes unnoticed and costs conversions: the windows are different. The GCLID alone has 90 days. Enhanced Conversions for Leads, which carry hashed personal data, have 63 days. Those who assume 90 for everything silently lose the tail of longer-cycle sales, with no error showing up in the dashboard.

The thesis that remains, and that probably survives the next API rename, is this: attribution moved away from the isolated click identifier and toward identity matching. The GCLID is still the piece that ties the click to the lead, only now it works with company.

Where the data gets lost along the way

Even in operations that did the setup, the GCLID disappears for mundane reasons:

• Auto-tagging turned off in the account. Without it, the parameter is simply not generated, and no later configuration fixes that.
• A redirect in the middle of the path. A poorly configured redirect between the ad and the final page discards the whole query string, and the parameter dies before reaching the form.
• A form builder that ignores the query string on mobile. It happens more often than you would imagine, and usually goes unnoticed because it works on desktop.
• Refusal of cookies. Part of the traffic will refuse, and that share will never have the data.

None of these cases generates an alert. The dashboard keeps showing site conversions normally, and the failure only appears when someone tries to upload the offline conversion and discovers that half the base does not have the code.

What needs to exist before launching the campaign

The setup itself is quick, and that is precisely why it is worth doing before the first click, not after the first month:

• Auto-tagging enabled in the Google Ads account.
• A hidden field in the form reading the URL parameter and storing it along with the lead's data.
• A stable place for this value to live, whether the CRM, the automation tool, or the data platform.
• A funnel milestone that fits within the retention window, so the upload is not rejected for being late.
• Sending the conversion when the lead reaches that milestone, and not only when the contract is signed.

It is worth checking this today if your operation has been running campaigns for some time. Every lead that came in without the code is a lead that cannot be attributed, and that loss is not recoverable.

Where Laiki comes in

Laiki stores the GCLID together with the lead, in the same record where the source, the events, and the funnel stage are. From there, you can segment who has the parameter filled in and track how much of the base actually arrived with the code.

When the lead reaches the stage that matters to the business, the platform sends that conversion back to Google Ads automatically, with no manual spreadsheet export and without anyone having to remember to send it within the deadline. The algorithm starts optimizing for what became business, not for what became a form.