Advertising
How to store the GCLID and pass it to your CRM (without losing offline conversions)
Copy for AI
Store the GCLID in a hidden form field, then in a fixed CRM field.
That’s how you tell Google Ads which leads became customers, through an offline conversion import.
The verdict: to store the GCLID in your CRM, capture it the moment the form is sent. A GCLID you didn’t save on day one can’t be rebuilt weeks later, when the deal closes.
The whole chain hinges on that one technical detail.
If the ID is missing, you can export the tidiest deal values and Google will still refuse them.
Below: what the GCLID is, why offline conversions break without it, and how to store it step by step.
Why this matters for B2B
This isn’t a side issue.
If your paid campaigns exist to buy pipeline rather than clicks, the loop from won deal back to campaign is your most important measurement point. The GCLID is the thread that closes that loop:
What exactly is the GCLID?
GCLID stands for Google Click Identifier: a unique code for every paid click.
Google appends it to the URL each time someone clicks your ad, provided auto-tagging is switched on in your account.
According to Google’s auto-tagging help, auto-tagging is on by default for new accounts.
Older accounts can check it under Account settings.
What it looks like
You’ll recognise it as a long parameter behind your landing page URL, along the lines of ?gclid=Cj0KCQ....
Every click gets its own GCLID.
Two clicks by the same person get two different codes.
What it holds
The code contains no personal data. But it holds the key to all the campaign data behind that click:
- Campaign and ad group: where the click came from
- Keyword: the search that triggered the ad
- Device and moment: how and when they clicked
Google keeps that link on its own side. So you only store the GCLID itself.
Send it back later with a conversion attached, and Google puts the won deal on the right campaign.
The GCLID is the proof that one paid click led to one enquiry.
To see where that click comes from, read how search ads work.
Why offline conversion imports fail without a GCLID
Because Google matches every imported deal to a click, and the GCLID is the match key.
In B2B, the road from click to customer rarely fits into one session.
Someone clicks your ad, fills in a form, and only signs weeks later.
That deal closes in your CRM or in a sales call, far outside Google Ads.
So Google never sees that revenue on its own.
What the import needs
The offline conversion import solves that.
You send your won deals back to Google: “this click became a customer worth X euros”.
But Google only accepts rows that carry the required fields:
| Field | Required? | Note |
|---|---|---|
| Google Click ID (GCLID) | Yes | The match key; without it, the row fails |
| Conversion Name | Yes | Must match the action name exactly, capitals included |
| Conversion Time | Yes | Date and time, with a time zone |
| Conversion Value | No | Blank means the action’s default value |
| Conversion Currency | No | Three-letter code, such as EUR |
Without the GCLID, Google can’t tell which click earned that revenue. The row is rejected.
Where most teams come unstuck
They set up conversion tracking on the website neatly.
But they forget to capture the GCLID when the form is submitted.
Weeks later, when the deal closes, that ID is nowhere to be found.
So storing the GCLID isn’t an optional extra.
It’s the precondition for offline conversions.
Next step: our guide to importing offline conversions in Google Ads.
How do you capture and store the GCLID?
Capture it on landing, keep it in the browser, and send it along with the form.
In practice that runs in four steps.
Step 1: Read the GCLID from the URL
When someone arrives via an ad, the GCLID sits in the address bar.
A small script or Google Tag Manager reads that parameter as soon as the page loads.
Step 2: Keep it in the browser
Store the GCLID in a cookie or in local storage.
That way it survives if the visitor browses a few other pages first.
Google’s own sample script keeps it for 90 days.
Watch out: Google adds that you have to follow local cookie consent rules. In Belgium, that means your banner and Consent Mode v2 setup decide what you may store.
Step 3: Write it into a hidden form field
Add a hidden field to your lead form, for example gclid, filled with the stored value.
The visitor sees nothing. But on submit, the GCLID travels along.
Here’s what that looks like in a form builder:
Step 4: Map the field to a fixed CRM field
Create a separate, fixed field for the GCLID in your CRM, next to email and company name.
Not a loose note: a structured field you can export later.
Every serious CRM supports custom fields on a contact or deal, as HubSpot’s free CRM does:
HubSpot’s free CRM page, October 2026. Any CRM with custom fields can hold the GCLID.
Comparing systems? Our list of the best B2B CRM tools covers the main options.
Our experience: we’ve set this chain up in HubSpot, Pipedrive, Teamleader and Salesforce.
The recurring problems are the same everywhere: data out of sync and deals nobody updates.
Where the chain usually breaks
The pitfall is almost always in steps three and four.
- Empty hidden field: the script never filled it
- Truncated value: the CRM field is too short
- Lowercased value: the CRM changes the capitals
Each one produces GCLIDs you only discover when the import fails.
The same discipline you apply to UTM parameters applies here: the field has to be filled for every single lead.
What else do you keep alongside the GCLID?
Two extra pieces of data: the conversion time and the deal value.
The GCLID alone identifies the click. Capture the rest right away.
The time of the conversion
That’s the moment the deal was won.
Google uses it to place the conversion in the right period, and to check the window.
Google’s GCLID import guide requires a click-to-conversion cycle of less than 90 days, or 14 days for some data sources.
Time zone: add one to every timestamp, or set it once at the top of the file.
Google recommends a time zone ID, such as Europe/Brussels, because it handles daylight saving time.
The value of the deal
Only with real revenue can Google learn which campaigns bring valuable leads, not just leads.
For example, say a campaign produces plenty of cheap enquiries but never a deal.
It looks fine in your standard report. In reality it’s a money pit.
With deal value in your import, that illusion flips.
That’s the difference between steering on the volume of Google ads and steering on pipeline.
Smart bidding then learns from deals, not form fills.
Not sure what a lead is worth? The lead value calculator gives you a starting value.
Rule of thumb: three clean fields, ready to export, is all a successful import needs.
Test the chain before you go live
Run one real test lead through the whole chain before you rely on it.
The cheapest mistake to prevent is a chain that adds up on paper but runs through empty fields in reality.
Run the test in five checks
- Click or fake a click: click a live ad, or paste a test value as
?gclid=behind your landing page URL. - Submit your own form: use a real-looking test lead.
- Open the lead in your CRM: the GCLID field must be filled.
- Compare the full value: no truncation, same capitals.
- Import that one lead: see whether Google accepts it.
Check the conversion action name
The name in your file must match the conversion action in Google Ads exactly. Here’s where you find it:
The contact form conversion action in our own Google Ads account, October 2026. Copy the name exactly, capitals included.
A one-letter difference in that name makes the whole row fail.
Case sensitivity
Google says it plainly: “The GCLID is case sensitive.”
A CRM field that lowercases it breaks the match.
Only once the complete loop works, from click to accepted import, can you build on it.
Add it to your routine for tracking errors. One test saves months of silent leaks.
Frequently asked questions about storing the GCLID
Does the GCLID contain personal data?
No. The GCLID is a random-looking code that points to campaign data on Google’s side, not to the identity of the visitor.
You do link it in your CRM to a lead with contact details. So handle the whole thing within your privacy policy, but the ID itself isn’t personal data.
How long does a GCLID stay valid for import?
Google requires a click-to-conversion cycle of less than 90 days for most GCLID imports.
In B2B with long sales cycles, that’s the real risk: a deal that closes after many months falls outside that window. So import regularly, and consider importing an earlier milestone (such as a qualified lead) that happens within 90 days.
Starting from scratch? Google now recommends starting with enhanced conversions for leads instead, and suggests existing GCLID importers upgrade to it. Our guide to enhanced conversions for leads explains the setup.
Does this also work with third-party forms or an external tool?
Yes, as long as that tool can pass a hidden field to your CRM.
The core stays the same: read the GCLID from the URL, keep it in the browser, write it into a hidden field and map that field to your CRM. If that hand-off isn’t possible, the form is unsuitable for offline conversion tracking.
What if some leads have no GCLID?
That’s normal: not every lead arrives via a paid click. Organic visitors, direct traffic and referrals have no GCLID.
In the import, you only send the leads that have one.
Ready to tie your deals back to your campaigns?
Storing the GCLID isn’t a sexy job.
But your whole paid measurement model turns on it.
Without that ID, your reports stop at leads. With it, you steer budget on pipeline instead of click noise.
We help Benelux companies connect paid campaigns to their CRM and won deals.
Want a google ads specialist to review your GCLID chain? Contact us and we’ll test it with one lead first.
Free website scan
Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.
We only use your details for your scan. No spam, unsubscribe anytime.