Capture the GCLID in Zoho Forms for CRM and Google Ads
Google Ads reports clicks well, but connecting those clicks to submitted leads requires carrying the Google Click ID through the visit. This guide explains how to store that identifier, submit it with a Zoho form, pass it to a CRM, and return it to Google Ads as an offline conversion.
Why the GCLID matters
Default campaign reporting can show impressions and clicks without showing which submissions they produced. The missing link is the Google Click ID, commonly called the GCLID. If that value travels with the form submission, it can be stored against the lead in a CRM and later matched back to the originating ad click.
Set up the site and hidden field
First, install the attribution snippet on the website using the custom-code setting provided by the site builder. Supported builders named in the workflow include Webflow, Squarespace, Wix and WordPress, although the exact setting varies by platform. Next, add a hidden field to the Zoho form and set its Field Alias to gclid. That alias is the destination where the stored click identifier is placed.
Carry the identifier through to submission
When a visitor arrives from a Google ad, the identifier is read from the landing URL and kept in the browser. It therefore survives navigation to other pages and a later return visit. At submission, the stored value is inserted into the hidden field and sent alongside visible answers such as name and email. Zoho Forms can pass the submission to Zoho CRM natively, while Zapier or a similar connector can forward it to another CRM, spreadsheet or reporting tool.
Return the value as an offline conversion
Create the receiving conversion in Google Ads first: open Goals, choose Conversions, start a new conversion, select Offline Conversion, and choose Add data source later on the data-source screen. Then decide which business milestone should count. A won deal may be too late or too infrequent; smart bidding features such as Maximise Conversions, Maximise Conversion Value and Target CPA generally need more than 50 conversions per month. If won deals are rarer than that, an earlier event such as deal creation may give Google Ads enough signal. Build the automation around that milestone, select Google Ads and Send Offline Conversion in Zapier, and map the stored GCLID to the matching field. Test the flow before relying on it for bidding decisions.
What else the captured context can show
Reading the URL only on the form page fails when someone lands on the homepage, browses product or service pages, and submits later from a contact page. Browser storage solves that gap. The same setup can also carry UTM-derived channel detail for paid visits and channel detail for organic search, organic social, referral and direct visits. For example, an architecture firm could see whether a design-call request came from a paid Google campaign for residential extensions, a specific keyword and ad, or from an organic search for a residential architect in Sydney. Those fields help separate campaign performance from SEO and social performance once the lead reaches the CRM.
Pre-launch checklist
Before launch, confirm the snippet loads on every page where a form may be reached, the hidden field alias is exactly gclid, a test submission contains a value after an ad-style landing visit, the CRM receives that value, and the offline-conversion automation maps it correctly. Also test a multi-page journey and a return visit, because those are the cases a same-page URL check would miss.
| Journey | URL-only capture | Browser-stored capture |
|---|---|---|
| Visitor submits on landing page | Identifier is present in URL | Stored identifier is written to hidden field |
| Visitor browses other pages first | Identifier may no longer be in URL | Original identifier remains stored |
| Visitor leaves and returns later | Original landing context may be lost | Stored identifier remains available for submission |
Comparison based on the described behaviour; confirm current product behaviour before publication.
| Paid example field | Architecture-firm value |
|---|---|
| Channel | Paid Search |
| Channel Drilldown 1 | |
| Channel Drilldown 2 | Residential Extensions Campaign |
| Channel Drilldown 3 | Architect Northern Beaches |
| Channel Drilldown 4 | Free Design Call Ad |
Illustrative values from the source example, not guaranteed output values.
| Organic example field | Architecture-firm value |
|---|---|
| Channel | Organic Search |
| Channel Drilldown 1 | |
| Channel Drilldown 2 | www.google.com |
| Channel Drilldown 3 | Residential architect Sydney |
Illustrative values from the source example, not guaranteed output values.
Frequently asked questions
What field setting is needed in Zoho Forms?
Add a hidden field to the Zoho form and set its Field Alias to gclid. Place the attribution snippet on the site so the click identifier from the landing URL is stored in the browser and written into that field at submission.
Why store the GCLID in the browser instead of reading the URL at submission?
A URL-only approach can miss the identifier when the visitor browses other pages or returns later. Storing it in the browser preserves the original landing click until the form is submitted.
How is the captured GCLID returned to Google Ads?
Create an Offline Conversion in Google Ads under Goals > Conversions, choose Add data source later, then use an automation such as Zapier triggered by the chosen CRM milestone to send the stored GCLID to Google Ads.
Should the offline conversion fire on a won deal or an earlier event?
Waiting for a won deal can leave fewer than 50 monthly conversions for smart bidding to learn from. Tracking an earlier milestone, such as deal creation, can provide more timely volume when closed deals are infrequent.