Track Zoho Forms submissions as Google Ads conversions with server-side tracking
You can connect a Zoho Forms submission to the Google Ads click that started the visit, then send that result back to Google Ads either immediately or after a later CRM milestone. The key is preserving the click identifiers through the form, rather than relying on a browser page view to record the conversion.
Why browser tracking loses conversions
Browser tracking depends on scripts running in the visitor's browser. That creates several failure points: ad blockers can prevent the tag from loading, Safari's Intelligent Tracking Prevention can clear tracking cookies after a couple of days, and a person may click on a phone but submit later on a laptop. Thank-you page tracking has the same weakness because it still needs the browser to report the visit.
Server-side tracking changes the path. The conversion is sent directly to Google's servers, where browser blockers and privacy settings cannot intervene in the same way. The supplied article cites Google data indicating a typical 23% average increase in recorded conversions and a 10% reduction in cost per conversion from more reliable data, and also notes that common browser methods can miss up to 30% of conversions. Treat those figures as context for why accuracy matters, not as a guaranteed result for every account.
Choose the timing: lead or customer
Decide what counts as success before building the flow.
- Fire at submission: optimise for lead volume. A purpose-built connector can detect the Zoho Forms submission, collect name, email, phone and other entered details, hash personal data with SHA-256 as required by Google, and send the conversion with click context such as GCLID, GBRAID, WBRAID and User Agent.
- Fire at a CRM milestone: optimise for downstream value. Capture the identifiers with the form, store them on the CRM lead or contact record, and send the conversion when a deal is created, an opportunity is closed won, or the lead becomes a paying customer.
The second route is usually better when lead quality varies widely. The first is simpler when every valid submission has similar value.
Preserve click identifiers through the form
Install the attribution snippet in the website head, in the same position used for a Google Analytics installation. Then add four hidden values to each lead form: GCLID, WBRAID, GBRAID, and User Agent.
Because Zoho Forms does not provide a dedicated hidden-field element for this setup, add a Single Line field for each value, open its Properties, go to Visibility, and select Hide field. Then open Settings > Field Aliases and assign each field the alias expected by the capture tool. The exact alias list must come from that tool's help documentation.
After the ad click, the capture tool stores the identifiers in the browser. When the visitor submits the form, it writes those values into the hidden fields so they are saved alongside the name, email, phone number and other answers.
Carry the identifiers into the CRM
Send the submitted record to the CRM with the identifiers intact. With Zoho CRM, the flow stays inside the Zoho ecosystem. With another CRM such as Salesforce, HubSpot, Pipedrive, or ActiveCampaign, Zoho Flow can provide the integration path described in the workflow.
Keep the identifiers on the lead or contact record rather than in a spreadsheet or separate note. Later automation needs to read them reliably when the chosen milestone occurs.
Send the milestone conversion back to Google Ads
When the lead reaches the selected milestone, use an automation tool such as Zapier or Make to send the stored data back to Google Ads. Map the captured GCLID, GBRAID, WBRAID, User Agent, and lead details to the corresponding Google Ads fields.
If conversion value is available from the deal or opportunity, include it. That allows Google Ads reporting to distinguish a high-value renovation-style job from a lower-value patio-style job, rather than treating every conversion as equal. The same principle applies in any industry where customer value differs by campaign.
Use the data for bidding and budget decisions
Server-side events also reduce messy browser data. A conversion should be triggered by a successful form submission or CRM milestone, not merely by a page refresh, slow page load, or dropped connection. That makes Google Ads counts easier to reconcile with actual lead numbers in the CRM.
Use the cleaner data for three practical checks:
- Conversions by keyword: identify terms that generate enquiries, not just impressions and clicks, then shift budget toward profitable terms.
- Conversion value by campaign: compare revenue contribution across campaigns when CRM deal values are passed back.
- Conversions by geography: check whether leads cluster in target service areas, then use location bid adjustments to increase bids where paying customers originate and reduce bids where clicks rarely convert.
A builder example illustrates the value distinction: a patio construction campaign and a home renovation campaign may both produce a lead, but the renovation lead may be far more profitable. Geography matters similarly for local services such as veterinary care, pet grooming, dog training, and boarding, where postcodes outside the service area can waste spend.
Pre-launch checklist
Before relying on the setup, run a controlled test with a real ad click, submit a test form, confirm all four identifiers appear in the CRM record, trigger the milestone, and verify that one conversion reaches Google Ads with the correct value and attribution. Repeat the test on a second device and after a delay to confirm the identifiers survive the journey.
If the identifiers are missing, check the snippet placement, hidden-field visibility, field aliases, CRM field mapping, and automation trigger in that order. Those are the points where the click context can be lost.
| Decision | Use when | What Google Ads optimises for |
|---|---|---|
| Fire at form submission | Every valid lead has similar value and speed matters | Lead volume |
| Fire at CRM milestone | Only some leads become valuable customers | Deal creation, closed-won outcome, or paying customer |
Timing choice from the supplied workflow; results depend on data quality and account setup.
Frequently asked questions
Why can thank-you page or browser-event tracking miss Zoho Forms conversions?
Browser-based methods such as thank-you page visits or Google Tag Manager events can miss conversions when ad blockers stop scripts, Safari privacy limits shorten tracking windows, or a click and later conversion happen on different devices. Server-side sending moves the event directly to Google's servers, so browser interference is less likely to block it.
Should the conversion fire at form submission or later in the CRM?
Choose the moment that matches the value you want Google Ads to optimise for. Send at form submission for lead volume, or wait for a CRM milestone such as a created deal, closed-won opportunity, or paying customer when downstream value matters more.
Which identifiers need to travel with the form submission?
The capture fields named in the workflow are GCLID, WBRAID, GBRAID, and User Agent. They are stored in the browser after the ad click, written into hidden form fields at submission, carried into the CRM with the lead details, and then mapped back when the conversion is sent.
How are hidden fields created in Zoho Forms?
Zoho Forms has no dedicated hidden-field element in this workflow, so a Single Line field is used for each value, hidden through Visibility, and given the expected alias in Settings > Field Aliases.
Which reports become more useful with reliable conversion data?
Conversions by keyword shows which terms produce results rather than only clicks. Conversion value by campaign compares revenue contribution when deal value is passed from the CRM. Conversions by geography shows where leads cluster, which can inform location bid adjustments.