How to capture the GCLID in Zoho CRM
If you run Google Ads but can't tell which clicks turn into paying customers, you're bidding on incomplete information. The GCLID — the click identifier Google appends to ad URLs — is the key that lets Zoho CRM records be matched back to the ad click that produced them. This guide walks through capturing that value on your forms, carrying it into Zoho CRM, and sending it back to Google Ads as an offline conversion so bidding can learn from real outcomes.
What you'll need before you start
You need a working Google Ads account with conversion tracking, a website form that creates leads, a Zoho CRM account, and a way to move form submissions into Zoho CRM. That last piece can be a native integration in your form tool, or a connector such as Zapier, Make, or Zoho Flow. You'll also need a place on your form to store the GCLID — a hidden field — and a plan for which sales event should count as the conversion.
The four-step capture flow
The capture path has four hops, and each one has a job:
- Install the capture script on your site and add a hidden field named GCLID to your lead forms. The field is invisible to visitors but gives the script somewhere to write.
- When a visitor arrives from a Google Ad, the script reads the GCLID from the URL and stores it in the visitor's browser. It writes that stored value into the hidden field when the form is filled in.
- On submit, your form tool collects the GCLID alongside the lead's name, email, phone, and other answers.
- The form tool (or a connector) passes the GCLID into Zoho CRM with the new lead record.
The installation step varies by site builder — WordPress, Webflow, Squarespace, and others each have their own settings area — and Google Tag Manager is an alternative route. The important part is that the hidden field exists on every form that should carry the GCLID.
Why browser storage beats URL-only capture
Many form tools can grab URL parameters, but they only see what is in the address bar at the moment of submission. A visitor who clicks an ad, lands on the homepage, then browses to a contact page before submitting will have lost the GCLID from the URL. Browser-side storage closes that gap: the value is saved on arrival and survives page changes, and even a return visit days later. If your current setup only reads the live URL, expect missing GCLIDs on multi-page journeys — that is a capture failure, not a tracking mystery.
Choosing the conversion stage
Before wiring anything to Google Ads, decide which sales event counts as a conversion. Closing the deal first sounds right, but Google's smart bidding strategies — Maximise Conversions, Maximise Conversion Value, Target CPA — need roughly 50 conversions per month to optimise well. If you close fewer than 50 deals a month, an earlier pipeline event such as a Deal being created in Zoho CRM gives the bidding system enough signal. Use this checklist:
- Do you close 50+ deals per month? A closed-won event is viable.
- Fewer than 50? Pick an earlier stage with higher volume.
- Is the chosen event reliably recorded in Zoho CRM? If not, the conversion feed will be incomplete.
- Can the GCLID be joined to that event? The record must carry the GCLID forward.
- Have you tested the feed before increasing spend? Do so first.
Creating the offline conversion in Google Ads
In Google Ads, open Goals in the sidebar, go to Conversions, and create a new conversion of type Offline Conversion. On the final screen asking for a data source, choose Add data source later — the GCLID feed will supply the data. With the conversion defined, the remaining work is the outbound feed.
Sending the GCLID back with Zapier
Create a new Zap. Set the trigger to the Zoho CRM event you chose — for example, a new Deal. Set the action to Google Ads and select Send Offline Conversion. Finally, map the GCLID field from Zoho CRM (or wherever it is stored) to the matching field in the action. Test the Zap end to end before scaling ad spend; a silent mapping error will quietly starve Google Ads of conversion data.
Field and control map
Use this map to check each hop in your own setup:
- Ad URL: contains the GCLID parameter.
- Browser storage: holds the GCLID after arrival.
- Form hidden field: named GCLID; receives the stored value.
- Form submission payload: includes GCLID plus name, email, phone.
- Zoho CRM lead/deal record: stores the GCLID.
- Connector (Zapier/Make/Zoho Flow): trigger on the chosen event, action Send Offline Conversion.
- Google Ads: receives the GCLID against the offline conversion.
If any hop is missing, the chain breaks. The most common gaps are a missing hidden field and a trigger event that never carries the GCLID.
Beyond the GCLID: UTM and organic attribution
The same hidden-field approach can carry UTM parameters, so Zoho CRM records show channel detail as well as the click ID. In a law-firm example, a paid click could produce Channel = Paid Search, Channel Drilldown 1 = Google, Drilldown 2 = the campaign name, Drilldown 3 = the triggering keyword, and Drilldown 4 = the ad clicked. Organic arrivals can be captured too: a visitor from a regular Google search might show Channel = Organic Search, Drilldown 1 = Google, Drilldown 2 = the search engine domain, and Drilldown 3 = the search term when available. That gives a fuller picture of which leads come from paid versus organic sources.
Frequently asked questions
Why does my GCLID go missing when a visitor browses before submitting?
URL-parameter capture only reads the address bar at submission time. Once the visitor navigates away from the ad landing page, the GCLID is no longer in the URL. Storing the value in the browser on arrival and writing it into a hidden field at submission keeps it available across page changes and return visits.
Should I send the conversion when a deal closes or earlier in the pipeline?
Google's smart bidding strategies need roughly 50 conversions per month to optimise effectively. If you close fewer than 50 deals a month, sending an earlier event — such as a Deal being created in Zoho CRM — gives the system more data to learn from.
Which tools can move the GCLID from my form into Zoho CRM?
Your form tool's native Zoho CRM integration if it has one, or a connector such as Zapier, Make, or Zoho Flow. The GCLID travels alongside the lead's name, email, phone, and other form answers.
How do I set up the offline conversion in Google Ads?
In Google Ads, go to Goals → Conversions, create a new conversion, and choose Offline Conversion. When asked for a data source, select Add data source later. Then configure the outbound feed — for example a Zapier Zap with a Zoho CRM trigger and a Google Ads Send Offline Conversion action — and map the GCLID field.