Capture the Google Click ID in Formstack and return it to Google Ads
A Formstack submission only shows what a visitor typed. Without the Google Click ID, the CRM record cannot be tied back to the exact ad click that produced it. This guide explains how to store that identifier on arrival, place it into a hidden form field, forward it with the lead, and later return it to Google Ads as an offline conversion.
Why the click ID matters
Google Ads can generate enquiries, but clicks alone do not prove which campaigns create paying customers. The Google Click ID, usually shortened to GCLID, is the click-level identifier that makes that connection possible. If it is not saved with the lead, later revenue cannot be matched reliably to the originating ad.
Step 1: Install the snippet and add hidden fields
Install the attribution snippet on the website using the platform's settings area or a tag manager, following the method appropriate to that site builder. Then add a hidden field for the GCLID to each Formstack form that should carry attribution data. The hidden field is the receiving slot; visitors do not need to see or complete it.
Step 2: Store the ID on arrival, then populate the field
When a visitor arrives from a Google ad, the tool reads the GCLID from the landing URL and stores it in the browser. That stored value remains available while the person browses other pages, and can still be available if they return later. At submission, the tool copies the stored value into the form's hidden field.
Why storing on arrival matters
This persistence is the key distinction from a method that only reads the URL at the moment of submission. A typical journey may start on a homepage, continue through several pages, and end on a contact form long after the original URL parameter has disappeared. Storing the value on first arrival preserves the connection across that journey.
Step 3: Forward the ID with the lead
On submission, the GCLID sits alongside the name, email, phone number and other answers in Formstack. From there it can be included in notifications, sent to a spreadsheet, or passed to a CRM through Formstack integrations or a connector such as Zapier. CRM examples named in the workflow include HubSpot, Pipedrive and Salesforce.
Set up the offline conversion in Google Ads
Create the conversion action first. In Google Ads, open Goals, then Conversions, start a new conversion, choose Offline Conversion, and select the option to add a data source later. Next, choose the pipeline milestone that should count as a conversion. A fully closed deal is one option, but businesses closing fewer than about 50 deals a month may need an earlier milestone, such as deal creation, so smart bidding has enough conversion volume.
Connect the CRM milestone to Google Ads with Zapier
In Zapier, create a Zap whose trigger matches the chosen milestone, for example a new deal for a contact. Set Google Ads as the action and choose Send Offline Conversion. Finally, map the stored GCLID from the CRM or other storage location to the matching Zapier field. Test the flow before relying on it for bidding decisions.
Capture UTM and organic attribution too
Alongside the GCLID, UTM parameters can be carried into hidden fields. For a paid-search visit, the captured values may describe the channel as Paid Search, the source as Google, and successive drill-downs for campaign, keyword and ad. For an organic visit, the same structure may instead show Organic Search, Google, the referring domain and the search query. That gives a fuller lead-source picture than paid clicks alone.
Pre-launch checklist
Use this checklist before launch: the snippet loads on landing pages, every relevant Formstack form has the hidden fields, a test visit from a tagged URL populates the fields, the submission shows the values in Formstack, the CRM record receives them, and a test offline conversion appears in Google Ads. If any step fails, check whether the visitor arrived through a tagged URL, whether the correct form was used, and whether the CRM-to-Zapier field mapping points to the stored GCLID.
Frequently asked questions
Why use a hidden field for the GCLID?
A hidden field gives the attribution tool a destination for the stored click ID. When the form is submitted, that value travels with the visible answers instead of being lost when the landing-page URL is no longer present.
Should the offline conversion be sent at deal close or earlier?
Waiting for a fully closed deal can leave too few monthly conversions for smart bidding strategies that need roughly 50 per month. Choosing an earlier pipeline milestone, such as deal creation, can provide enough volume for optimisation.
Can organic visits be attributed too?
Yes. The same hidden-field approach can also record channel and drill-down values for visits arriving through organic search, organic social, referral, direct traffic and other non-paid routes.