Skip to content

Capture GCLID in Unbounce Forms and Return It to Google Ads

If you run Google Ads to Unbounce landing pages, you can see clicks and sessions in analytics but not which ad click became a qualified lead or a paying customer. The Google Click ID (GCLID) is the join key that closes that gap. This guide shows how to place the GCLID into a Unbounce hidden field on every submission, move it into your CRM, and optionally send it back to Google Ads as an offline conversion.

Why the GCLID matters for Unbounce campaigns

Analytics platforms count visits and sessions. They generally do not know which of those visits turned into a sales-qualified lead or a closed deal. The GCLID is appended by Google Ads to the landing page URL when auto-tagging is active. If you store that value with the lead record, you can later match the CRM outcome to the original ad click.

Two things usually break this chain. First, the GCLID disappears from the URL as soon as the visitor navigates to another page or returns days later. Second, the form never carries the value into the CRM, so the sales outcome cannot be tied back to the ad. A persistent capture layer plus a hidden form field solves both.

Three setup steps for Unbounce forms

  1. Install the capture script and add a hidden field. Place the capture snippet on your Unbounce landing pages, either through the account-level Script Manager so it applies across pages or on individual pages. Then add a hidden field to each form and label it GCLID. If you want the full walkthrough, see the step-by-step Unbounce installation instructions.
  1. Let the script populate the field. When a visitor arrives from a Google Ads click, the script reads the GCLID from the URL and stores it in the browser. On form completion it writes the stored value into the hidden field.
  1. Confirm the value is captured. After submission, the GCLID appears with the rest of the lead data in the Leads tab of the Unbounce Page Overview and in Unbounce email notifications. From there, built-in integrations or tools such as Zapier or Make can forward it to your CRM or another destination.

Field and control map

Use this map to check that each link in the chain is in place before you test.

Returning the GCLID to Google Ads as an offline conversion

In Google Ads, open Goals, then Conversions, and create a new conversion action. Choose Offline Conversion as the type. On the final screen, when Google Ads asks for a data source, select the option to add the data source later.

Next, decide which sales event should trigger the upload. Many teams wait until a deal is fully closed. That is intuitive but can starve Google's smart bidding strategies, which generally need at least 50 conversions per month to perform well. If your closed-won volume is below that, an earlier qualified-lead or new-deal event often gives the bidding system enough signal while still reflecting sales validation.

In Zapier, create a Zap whose trigger matches the event you selected, for example a new deal created for a contact. Set Google Ads as the action and choose Send Offline Conversion. Then map the GCLID stored in your CRM to the corresponding Zapier field. Before increasing ad spend, test that the flow works; the guide to testing offline conversions in Google Ads walks through how to verify it.

Choosing your offline-conversion trigger

Use this checklist to pick the event that balances signal quality against volume.

Why a persistent capture layer beats URL-only capture

A common shortcut is to read the GCLID from the URL at the moment the form is submitted. That works only while the parameter is still present. If the visitor leaves and comes back a few days later, or browses other pages before converting, the parameter is gone and the submission carries no click identifier.

A capture layer that stores the GCLID in the visitor's browser keeps the value available across page views and return visits. The hidden field is then filled from that stored value at submission time, not from the current URL.

What else travels with the submission

The same capture layer can pass UTM parameters alongside the GCLID. For a project-management software advertiser, a Google Ads click with matching UTMs could produce these values with the form submission:

  • Channel = Paid Search
  • Channel Drilldown 1 = Google
  • Channel Drilldown 2 = Project Management Campaign
  • Channel Drilldown 3 = Best Project Management Software
  • Channel Drilldown 4 = Free Trial Ad

Organic visitors are covered too

Leads who arrive through organic search, organic social, referral, or direct traffic can also carry channel details. For a visitor who found the business through a regular Google search, the captured values could include:

  • Channel = Organic Search
  • Channel Drilldown 1 = Google
  • Channel Drilldown 2 = www.google.com (or whatever search engine domain they used)
  • Channel Drilldown 3 = Best Project Management Software (or whatever keyword they searched for, if available)

Three different reasons a GCLID goes missing

When a submission has no GCLID, the cause is usually one of three distinct problems, and each has a different fix.

No GCLID at arrival. The click did not carry a GCLID in the URL, for example because auto-tagging was off or the visitor arrived through a non-ads channel. Check the landing URL of a live ads click first.

GCLID lost after navigation. The value was present on arrival but the capture layer was not installed on the pages the visitor browsed, or the browser blocked storage. Confirm the script runs site-wide, not only on the landing page.

GCLID captured but not delivered. The hidden field was filled, but the CRM mapping or the Zapier field mapping is wrong. Inspect the Unbounce Leads tab entry before debugging the CRM.

Putting it together

The full chain is: capture the GCLID on arrival, persist it in the browser, write it into a Unbounce hidden field at submission, forward it to the CRM with the lead record, and optionally upload it to Google Ads as an offline conversion at the sales event you choose. Test each link before scaling spend.

Field and control map for the GCLID chain
StageControl or fieldWhat to check
Landing pageCapture scriptRuns on all Unbounce pages, not only the ad landing page
FormHidden field labelled GCLIDPresent on every form that should carry the click ID
SubmissionLeads tab / email notificationGCLID value appears with the lead record
CRMGCLID field on the lead or contactValue mapped from the form submission
ZapierSend Offline Conversion actionGCLID field mapped to the Google Ads action

Control names reflect the workflow described for Unbounce, a CRM, and Zapier; exact labels in your accounts may differ.

Offline-conversion trigger checklist
QuestionIf yesIf no
Do you close at least 50 deals per month?A closed-won trigger can feed smart bidding enough volumeUse an earlier qualified-lead or new-deal event
Is the earlier event a genuine sales qualification?It can serve as a positive signal to Google AdsChoose a different event that reflects real sales intent
Can your CRM store the GCLID on the record?Map it to the Zapier action fieldAdd a field before building the Zap

The 50-conversions-per-month figure is the threshold described for Google's smart bidding strategies in the captured reference; check current Google Ads guidance for your account.

Frequently asked questions

What should the Unbounce hidden field be called?

Label the hidden field GCLID. That gives the capture layer a defined place to write the stored click identifier so it travels with the submission.

Will the GCLID still be captured if the visitor leaves and returns days later?

Yes, when the capture layer stores the value in the browser. The GCLID is written into the hidden field at submission even if the visitor browsed other pages or came back later, instead of relying on the parameter still being in the URL.

Should I send the offline conversion when the deal closes or when the lead is qualified?

Compare your closed-won volume with the roughly 50 conversions per month that smart bidding strategies generally need. If you close fewer deals than that, sending an earlier qualified-lead or new-deal event often gives the bidding system enough signal while still reflecting sales validation.

Why is the GCLID blank on some submissions?

Check three things in order: whether the click URL actually carried a GCLID, whether the capture script ran on every page the visitor browsed, and whether the CRM or Zapier field mapping is correct. Each cause has a different fix.