Capture the GCLID in Typeform and send it back to Google Ads
A Google Ads click identifier is only useful if it survives the journey from the landing page to the form submission. This guide explains how to store that identifier in the visitor's browser, place it into a Typeform hidden field, pass it to a CRM, and return it to Google Ads as an offline conversion.
Why the identifier needs to be stored
Clicks alone do not show whether advertising produces customers or revenue. Capturing the click identifier on each lead lets you connect a form submission to the ad click that produced it, then use that connection for reporting and bidding decisions.
The workflow has three parts:
- Store the identifier when the visitor arrives from a Google Ads click.
- Write the stored value into a hidden Typeform field at submission.
- Pass the value to a CRM or other system, then return it to Google Ads as an offline conversion.
Three-step setup
Setup checklist:
- Add the attribution code to the website using the custom-code or settings area provided by your site builder.
- Create a hidden field in Typeform.
- Set that field's default value to [gclid].
- Submit a test form after arriving from a tagged ad link and confirm the identifier appears in the submission.
When a visitor arrives from a Google Ads click, the attribution code reads the identifier from the URL and stores it in the browser. If the visitor browses other pages, leaves, or returns later, the stored value remains available. When the visitor completes a Typeform on the site, the code writes the stored value into the hidden field, so it is submitted alongside the name, email and other answers.
Same-page capture versus stored capture
A common failure is reading the identifier only from the landing-page URL. That works only when the form is completed on that same page. A visitor who lands on the home page, browses, and then submits a contact form on a different page will no longer have the identifier in the URL, so nothing is captured.
Browser storage solves that distinction: the value is captured at arrival, retained during browsing and return visits, and inserted wherever the form is eventually completed.
Send the identifier back as an offline conversion
Once Typeform receives the submission, the identifier can move onward through Typeform's built-in integrations or through an integration tool such as Zapier. The destination can be a CRM or another system used for sales and reporting.
To return the value to Google Ads, first create an offline conversion:
- Sign in to Google Ads and open Goals, then Conversions.
- Start a new conversion and choose Offline Conversion.
- When asked for a data source, choose Add data source later.
Next, choose the business event that should count as a conversion. Waiting for a fully closed deal is appropriate when closed volume is sufficient. Google's guidance cited in the workflow is at least 50 conversions per month for smart bidding to optimise effectively. With fewer than 50 closed deals per month, an earlier event such as deal creation can provide more data.
Then create a Zap in Zapier:
- Set the trigger to the chosen event, such as deal created for a contact.
- Select Google Ads as the action.
- Select Send Offline Conversion.
- Map the stored identifier from the CRM or storage system to the matching Zapier field.
Test the flow before increasing ad spend.
UTM and organic attribution in the same submission
Attribution data can cover more than the click identifier. UTM parameters can add channel, campaign, ad group, ad and keyword context to a submission.
Example for a commercial cleaning company using paid search:
- Channel: Paid Search
- Channel Drilldown 1: Google
- Channel Drilldown 2: Office Cleaning Campaign
- Channel Drilldown 3: Commercial Cleaning Sydney
- Channel Drilldown 4: Free Quote Ad
That detail shows which campaign, ad and keyword produced the lead. The same approach can describe unpaid sources. For an organic Google search, the fields might show Organic Search, Google, the search-engine domain, and the searched keyword when available. Similar detail can be passed for organic social, referral and direct visits, so reporting is not limited to paid clicks.
Final check
Before going live, verify each link in the chain: the identifier is stored on arrival, written into the hidden field, present in the Typeform submission, present in the CRM record, and accepted by Google Ads as an offline conversion. Treat any product name, trial length, pricing or offer wording as unverified until the site owner has documented it, and publish those details only after they have been checked against the current terms.
Frequently asked questions
Why does a GCLID sometimes disappear before a form is submitted?
No. If the identifier is read only from the landing URL, it disappears once the visitor moves to another page. Storing it in the browser first preserves it across pages and return visits, so it can still be written into the form later.
Which event should trigger an offline conversion?
Use a closed-deal event when you close enough deals for smart bidding to learn from. When monthly volume is low, an earlier event such as deal creation gives the system more conversion data to work with.
Can attribution data be captured for non-paid traffic too?
Yes. The same stored attribution approach can also pass channel and drilldown details for organic search, organic social, referral and direct visits, giving a fuller picture of lead sources beyond paid clicks.