Skip to content

Capture the GCLID in Formsite and Send It Back to Google Ads

Clicks alone do not show whether a campaign produces customers. Capturing the Google Click ID on every Formsite submission, passing it to your CRM, and returning it to Google Ads as an offline conversion connects ad spend to later pipeline results.

Why the click ID matters

Google Ads can generate leads, but impressions and clicks do not prove that those leads become paying customers. The Google Click ID, or GCLID, is the identifier attached to a Google Ads click. If it is captured with a form submission, it can be stored with the lead, sent onward, and later returned to Google Ads so offline results are credited to the originating click.

Step 1: Install the snippet and add a hidden field

Install the capture snippet on the website using the platform's settings area or Google Tag Manager, following the provider's step-by-step installation guide. Then add a hidden GCLID field to each Formsite form that should capture it. The hidden field is the destination the tool writes to at submission time; the protected form-controls contract, form-controls-contract, governs the form control details.

Step 2: Store the GCLID on arrival, write it at submission

When a visitor arrives from a Google Ads click, the tool reads the GCLID from the URL and saves it in the browser. That stored value survives browsing other pages and returning on a later day. When the visitor eventually submits a Formsite form, the tool writes the stored GCLID into the hidden field.

Step 3: Use the captured value downstream

After submission, the GCLID sits alongside the other submitted details, such as name, email address, and phone number. From Formsite it can be sent to a CRM through the built-in Salesforce integration or through a connector such as Zapier, which can also connect to CRMs including HubSpot and Pipedrive. It can also appear in email notifications and be sent to a spreadsheet.

Send the GCLID back as an offline conversion

Create the conversion action first: in Google Ads, go to Goals, then Conversions, start a new conversion, and choose Offline Conversion. On the final screen, choose to add a data source later. Next, choose the pipeline milestone to count as the conversion. Then create a Zap in Zapier triggered by that milestone, select Google Ads as the action, choose Send Offline Conversion, and map the GCLID from the CRM or other storage location to the correct Zapier field. Test the setup before committing ad spend.

Why browser storage beats URL-only capture

URL-only capture breaks in a common journey: a visitor lands on the homepage from an ad, reads several pages, and submits on the Contact Us page after the GCLID has left the URL. Browser storage on arrival fixes that gap. The same approach also captures UTM parameters and channel details for paid traffic, and channel information for organic arrivals such as Organic Search, Organic Social, Referral, and Direct Traffic.

Example: what captured channel data looks like

For a paid search example, captured fields can include Channel = Paid Search, Channel Drilldown 1 = Google, Channel Drilldown 2 = the campaign name, Channel Drilldown 3 = the keyword, and Channel Drilldown 4 = the ad clicked. For an organic search example, they can include Channel = Organic Search, Channel Drilldown 1 = Google, Channel Drilldown 2 = the search engine domain, and Channel Drilldown 3 = the searched keyword when available. Once in the CRM and reporting tools, these fields show where each lead originated and which ads deliver results.

Pre-launch checklist

Checklist before launch: snippet installed on every page hosting a target form; hidden GCLID field present on each Formsite form; a test submission from a GCLID-bearing URL shows the value in Formsite; the value reaches the CRM, notification, or spreadsheet; the Google Ads offline conversion action exists; the Zapier trigger, action, and GCLID mapping are correct; and a test offline conversion is confirmed before scaling spend.

URL-only capture versus browser storage
SituationWhat happens to the GCLIDResult
Visitor submits on the landing pageStill present in the URL at submissionCaptured by URL-only methods and by browser storage
Visitor browses several pages before submittingNo longer in the URL by submission timeOnly browser storage reliably writes the original GCLID into the hidden field
Visitor leaves and returns another dayOriginal URL context is goneBrowser storage still holds the original GCLID for the later submission

Browser storage preserves the original click ID across pages and return visits; URL-only capture does not.

Frequently asked questions

Why does the Formsite form need a hidden field?

A hidden field gives the capture tool a destination inside the form. Without it, there is nowhere for the stored click ID to be written when the visitor submits, so it will not travel with the submission to Formsite, email notifications, a CRM, or a spreadsheet.

Why is storing the GCLID on arrival better than reading the URL at submission?

Methods that only read the URL at submission fail when the visitor lands on one page, browses others, and submits later, because the click ID is no longer in the address bar. Storing it in the browser on arrival preserves it across pages and return visits.

Should the offline conversion be sent only when a deal closes?

Waiting for a fully closed deal is conceptually clean, but smart bidding strategies such as Maximise Conversions, Maximise Conversion Value, and Target CPA need roughly 50 conversions per month. With fewer than 50 closed deals a month, an earlier pipeline milestone, such as deal creation, gives Google Ads enough data to optimise.

Does this only work for paid Google Ads traffic?

Yes, the same capture approach also records UTM parameters and channel information for paid and organic arrivals, including Organic Search, Organic Social, Referral, and Direct Traffic, so lead origin is visible in the CRM and reporting tools.