Skip to content

How to capture the GCLID in HubSpot

Google Ads can bring in leads, but a lead is only useful if you can trace it to revenue. The Google Click ID (GCLID) is the link between an ad click and the contact record that follows. This guide shows how to store that identifier in HubSpot and return it to Google Ads as an offline conversion, plus how to choose the right conversion stage so the data is usable.

What the setup needs to do

The job has two halves. First, the GCLID must survive from the ad click to the moment a form is submitted, even if the visitor browses several pages or returns later. Second, that stored value must travel into HubSpot with the contact and then be mapped back into Google Ads. A hidden form field is the hand-off point: a browser-storage capture tool writes the GCLID into it, the form tool submits it, and HubSpot receives it alongside name, email, phone, and other fields. If you use HubSpot's native forms, the value appears on the contact record automatically. If you use a third-party form tool, the sync or automation must include the GCLID field.

Four steps to get the GCLID into HubSpot

  1. Install a capture tool on your website and add a hidden field named for the GCLID to your lead forms. Installation varies by platform (WordPress, Webflow, Squarespace, and others) and can also be done through Google Tag Manager.
  1. When a visitor arrives from a Google Ad, the capture tool reads the GCLID from the URL and stores it in the browser. That storage is what keeps the value available across page views and return visits.
  1. On form submission, the stored GCLID is written into the hidden field and collected with the rest of the lead's details.
  1. The value is passed to HubSpot with each new contact. Native HubSpot forms handle this directly; third-party form tools can pass it through a built-in HubSpot integration or an automation tool such as Zapier or Make.

Checklist: choose the conversion stage before you build the automation

Picking the stage is a decision, not a default. Work through these points before configuring the return path:

  • Count your closed deals per month. Google's smart bidding strategies (Maximise Conversions, Maximise Conversion Value, Target CPA) generally need roughly 50 conversions per month to perform well.
  • If you close fewer than 50 deals a month, track an earlier pipeline event, such as a Deal being created in HubSpot, so Google receives enough signal.
  • If you close well above that threshold, a later stage such as a won deal may be appropriate.
  • Confirm the chosen event exists as a trigger in your automation tool before mapping fields.
  • Decide who owns the mapping and who checks the first few conversions after launch.

Why URL-only capture fails and browser storage does not

Many form tools can read URL parameters, but they read only what is in the URL at the moment of submission. Picture a visitor who clicks an ad, lands on the homepage, then browses to a contact page before filling in the form. By that point the GCLID has dropped out of the URL, so a URL-only reader has nothing to pick up.

Browser storage changes the outcome. When a capture tool saves the value at arrival, it stays available no matter how many pages the visitor views or whether they leave and come back later, and it is written into the hidden field when the form is submitted. That is the general technical trade-off to weigh when choosing between URL-parameter-only capture and a tool that persists the value in the browser.

Worked example: what the captured fields can look like

Suppose a law firm runs a Google Ad and a visitor submits a form. Depending on the UTM parameters on that ad, the captured values could include:

  • Channel = Paid Search
  • Channel Drilldown 1 = Google
  • Channel Drilldown 2 = Personal Injury Campaign
  • Channel Drilldown 3 = Car Accident Lawyer
  • Channel Drilldown 4 = Free Case Review Ad

For a visitor who arrived through a regular Google search instead, the captured values could include Channel = Organic Search, Channel Drilldown 1 = Google, Channel Drilldown 2 = www.google.com, and Channel Drilldown 3 = the search term when available. These fields sit alongside the GCLID and give the contact record context beyond the click identifier.

Field and control map

Use this map to check each hand-off point:

  • Hidden form field: receives the GCLID from the capture tool; must exist on every lead form.
  • Form submission payload: carries the GCLID with name, email, phone, and other fields.
  • HubSpot contact record: stores the GCLID property so it can be read later.
  • Automation trigger: the HubSpot event you chose in the checklist (for example, Deal created).
  • Google Ads action: 'Send Offline Conversion'.
  • Final mapping: HubSpot GCLID field → Google Ads GCLID field.

Frequently asked questions

Does the GCLID survive if a visitor leaves the site and returns later?

Yes, when the capture tool stores it in the browser at arrival. The value is preserved across page views and return visits, and it is written into the hidden field when the form is eventually submitted.

Can I use a third-party form tool instead of HubSpot forms?

Yes. Tools such as Gravity Forms, Jotform, Typeform, and Tally Forms can send the GCLID to HubSpot through a built-in integration or an automation tool like Zapier. The sync that already sends name, email, and phone just needs the GCLID field added.

Should I send the conversion when a deal is won?

Only if you close enough deals to give Google's smart bidding enough signal. Roughly 50 conversions per month is the working threshold; below that, an earlier stage such as Deal created is usually a better choice.

What happens if I skip the hidden field?

The GCLID has nowhere to land on the form, so it will not be collected with the submission and will not reach HubSpot. The hidden field is the hand-off point between capture and the contact record.