Capture the GCLID in Close CRM and Send It Back to Google Ads
When you spend on Google Ads, clicks alone do not tell you whether the channel produces customers. The missing link is usually the Google Click ID: the parameter Google appends to a paid-search landing URL. If that value is stored at arrival, written into your form, and carried into Close CRM with the lead, you can later return it to Google Ads as an offline conversion and let bidding see what happened after the click. This guide explains the capture chain, the conversion-stage decision, and the field mapping needed to keep the identifier intact from first visit to CRM record.
What the capture chain needs to do
A reliable setup has four links. First, a script on your site reads the GCLID from the landing URL and keeps it in the visitor's browser. Second, a hidden field on each form receives that stored value when the visitor submits. Third, your form tool captures the hidden field alongside the lead's name, email, phone number, and other details. Fourth, an integration passes the value into Close CRM with the new lead. The same chain can carry UTM parameters and organic-source details, which gives sales and marketing a fuller picture than the click identifier alone.
Four steps to get the GCLID into Close CRM
- Install the tracking script on your website and add a hidden field named for the GCLID to your forms. Installation depends on your platform — WordPress, Webflow, Squarespace, or Google Tag Manager — and usually means adding a snippet through site settings. The hidden field gives the script a place to write the value.
- When a visitor arrives from a Google Ad, the script reads the GCLID from the URL and stores it in the browser. Because the value persists, it survives page changes, a later return visit, and a form completed on a different page.
- On submission, the form tool captures the hidden field together with the lead's other entries. This is the handoff point where the identifier must not be dropped.
- Send the captured value to Close CRM with the new lead. Use your form tool's native Close integration if it has one, or connect through Zapier or Make.
Choose the conversion stage before you build the return flow
In Google Ads, create a conversion action under Goals > Conversions and choose Offline Conversion. On the data-source screen, select the option to add the data source later. Then decide which sales stage should count as the conversion.
Waiting for a fully closed deal feels accurate, but it can starve smart bidding. Strategies such as Maximise Conversions, Maximise Conversion Value, and Target CPA generally need around 50 conversions per month to optimise well. If your business does not close that many deals monthly, send an earlier pipeline event — for example, when an Opportunity is created in Close — so Google receives enough signal.
Use this checklist to settle the stage:
- Count your average monthly closed deals. If the figure is well below 50, prefer an earlier event.
- Confirm the earlier event is meaningful: it should correlate with real sales progress, not just form fills.
- Check that the chosen event exists as a trigger in your automation tool.
- Record the decision so sales and marketing report against the same definition.
Return the GCLID to Google Ads
With the conversion action in place, build the return flow. In Zapier, create a Zap whose trigger matches the stage you selected — for example, an Opportunity created in Close. Set Google Ads as the action and choose Send Offline Conversion. The final mapping step connects the GCLID stored in Close CRM to the matching field in Google Ads. Test the flow before increasing ad spend so you can confirm that values arrive and conversions register.
Why browser persistence matters
Many form tools can capture URL parameters, but only from the URL present at the moment of submission. If a visitor clicks an ad, lands on the homepage, then navigates to a contact page before filling the form, the GCLID is gone from the URL and the tool captures nothing. Storing the value in the browser at arrival closes that gap: the identifier is available whenever and wherever the form is completed, including on a return visit days later.
Field and control map
The table below shows where each piece of data lives as it moves through the chain. It is a reference for checking that nothing is dropped between the landing page and the CRM record.
Worked example: an accounting firm's paid-search lead
Suppose an accounting firm runs a Google Ad for small-business tax help. A prospect clicks the ad and later completes a consultation form. Alongside the GCLID, the UTM parameters on the ad can populate attribution fields such as Channel = Paid Search, Channel Drilldown 1 = Google, Channel Drilldown 2 = the campaign name (for example, Tax Preparation Campaign), Channel Drilldown 3 = the triggering keyword (for example, Small Business Tax Help), and Channel Drilldown 4 = the ad name (for example, Free Consultation Ad).
If the same prospect had arrived through a standard Google search instead, the organic fields could read Channel = Organic Search, Channel Drilldown 1 = Google, Channel Drilldown 2 = the search engine domain, and Channel Drilldown 3 = the search term when available. In both cases the GCLID is present only for the paid click, which is why the identifier and the attribution fields serve different purposes.
Putting it together
The capture chain works when each link is verified: the script stores the identifier, the hidden field receives it, the form tool captures it, Close CRM stores it with the lead, and the automation returns it to Google Ads at a stage that produces enough conversion volume. Adding UTM and organic-source fields gives you a complete view of where leads originate, not just which ad click preceded them.
| Field or control | Where it lives | What it holds | Check |
|---|---|---|---|
| GCLID hidden field | Website form | The stored Google Click ID written by the tracking script | Field name matches the script configuration |
| Channel | Form submission / CRM record | Paid Search or Organic Search | Populated from UTM or referrer data |
| Channel Drilldown 1 | Form submission / CRM record | Google (the platform) | Consistent naming across campaigns |
| Channel Drilldown 2 | Form submission / CRM record | Campaign name or search engine domain | Matches your campaign taxonomy |
| Channel Drilldown 3 | Form submission / CRM record | Keyword or search term when available | Not assumed for every visit |
| Channel Drilldown 4 | Form submission / CRM record | Ad name | Paid-search visits only |
| Offline conversion action | Google Ads | The conversion event that receives the GCLID | Data source set to add later |
| Send Offline Conversion action | Zapier or Make | Maps the CRM GCLID to the Google Ads field | Tested before scaling spend |
Field labels reflect the attribution categories shown in the captured example. Your own form and CRM field names may differ.
Frequently asked questions
Should I send the offline conversion when the deal closes or earlier?
Earlier is usually safer unless you close roughly 50 or more deals per month. Google's smart bidding strategies need enough conversion volume to optimise, so an event such as an Opportunity being created in Close can provide a steadier signal than a fully closed deal.
Why doesn't my form tool capture the GCLID when the form is on another page?
Built-in URL parameter capture reads only the URL at the moment of submission. If the visitor moved from the landing page to a contact page, the GCLID is no longer in the URL. A script that stores the value in the browser at arrival keeps it available for later form completions.
Can I capture UTM parameters alongside the GCLID?
Yes. The same hidden-field approach can carry UTM parameters into your form tool and CRM, giving you campaign, keyword, and ad-level attribution in addition to the click identifier.
Do I need Zapier to get the GCLID into Close CRM?
Not necessarily. If your form tool has a native Close integration, it can pass the captured value directly. Otherwise, Zapier or Make can connect the form submission to Close CRM.