Skip to content

Capture the GCLID in Leadpages Forms and Send It to Your CRM and Google Ads

If a visitor arrives from a Google ad, browses several pages, and only later completes a Leadpages form, the click identifier may no longer be in the page address. A browser-stored attribution value solves that gap: it is saved on arrival, inserted into a hidden form field at submission, and then carried into the CRM where it can support offline conversion reporting.

Why the click ID matters

Analytics can show that paid traffic reached a page, but that alone does not reveal which clicks became leads or customers. The Google click identifier, commonly called the GCLID, provides the link needed to connect a form submission back to the originating ad click. Once that value reaches the CRM, it can also be returned to Google Ads when a later sales event occurs.

Step 1: Install the snippet and create the hidden field

Install the attribution snippet on the landing-page site. Placing it through the Leadpages Analytics settings applies it across pages rather than requiring separate installation on each page. Then create a hidden field on each relevant form and name it GCLID. The field is the destination into which the stored value will be written.

Step 2: Let the stored value populate the form

On arrival, the tool reads the GCLID from the landing URL and stores it in the visitor's browser. If the visitor explores other pages, leaves, or returns later, the stored value remains available. When the Leadpages form is completed, the tool populates the hidden GCLID field automatically, so the visitor does not need to enter or see it.

Step 3: Review and forward the submission

At submission, Leadpages records the hidden value with the visible fields such as name, email and phone number. It can be reviewed in the Leads area and included in notification emails. Native Leadpages integrations, or automation tools such as Zapier or Make, can then pass the lead and attribution data to a CRM or another connected system.

Send the value back as an offline conversion

First create an imported conversion action in Google Ads: open Goals, then Conversions, choose a new conversion, select Imported, choose CRMs, files or other data sources, and select Add data source later when prompted. Next choose the sales event that should send the value back. Waiting for a fully closed deal may produce too few events for smart bidding; the supplied guidance notes that strategies such as Maximise Conversions, Maximise Conversion Value and Target CPA typically need at least 50 conversions per month. An earlier qualified event, such as creation of a new CRM deal, may provide a more useful volume of signals. Finally, configure an automation whose trigger matches that event, choose Google Ads Send Offline Conversion as the action, and map the stored GCLID to the required field. Test the complete path before increasing advertising spend.

What else the hidden fields can carry

URL-only capture fails when the identifier disappears before submission. Browser storage avoids that weakness by retaining the value across pages and return visits. The same setup can also retain UTM-derived attribution fields. For a paid-search example, those fields may identify Paid Search, Google, the campaign, the keyword theme and the ad. For organic arrivals, the tool can instead record channels such as Organic Search, Organic Social, Referral or Direct Traffic, together with the referring search domain and available search term.

Pre-launch checklist

Use this checklist before relying on the data: the snippet is installed on every landing page; each form has a correctly named GCLID hidden field; a test submission shows the value in Leadpages; the CRM receives the same value; the Google Ads conversion action exists; the automation trigger matches the intended sales stage; and a test offline conversion appears in Google Ads. If a trial offer is presented, verify its duration and current signup terms directly with the provider before relying on them.