Skip to main content

Google Ads says you got 140 leads last month. Sales says eleven were real. Smart Bidding believes the ad account, so it keeps buying more of the other 129.

Both platforms optimize toward whatever you call a conversion, and a form fill is a weak proxy for revenue. Spam, job seekers and tire-kickers all submit forms. Once a qualified-lead event and a closed-deal event with a dollar value flow back from Zoho, you make those primary and demote the form fill to secondary. On lead-gen accounts I've seen this one change matter more than any keyword or audience tuning, because it fixes what the system is aiming at. The general mechanics are in our offline conversion tracking guide.

What click IDs and UTMs do you need to store in Zoho at form submit?

Everything the platforms will later need to match the lead to a click, written to dedicated Zoho fields at submission. You can't recover a gclid three weeks later; without it, the lead can only match on hashed email or phone.

Zoho field (single line)Where it comes fromUsed by
GCLIDgclid URL parameterGoogle Ads click conversion import
GBRAID / WBRAIDgbraid / wbraid URL parameters (iOS and app-related clicks)Google Ads, when no gclid exists
FBC_fbc cookie, or built from fbclid as fb.1.<ms timestamp>.<fbclid>Meta Conversions API (not hashed)
FBP_fbp cookie set by the Meta pixelMeta Conversions API (not hashed)
UTM Source / Medium / Campaign / Term / ContentURL parameters on landingReporting and sanity checks
Lead Event IDGenerated in the browser at submitDeduplicating the browser and server Lead event
Ad Opt-OutYour "Do Not Sell or Share" control or Global Privacy ControlSuppressing or restricting uploads

How the values get there depends on the form:

  1. Zoho Forms. Zoho's help docs describe UTM Tracking (under the form's Share options), where you can add gclid as a custom parameter and place one advanced tracking code in your site footer. Map the captured values to custom Leads fields in the Zoho CRM integration.
  2. Zoho CRM web-to-lead forms. With the Google Ads integration enabled, Zoho adds a hidden zc_gad field and a zcga.js script that reads the gclid from a cookie. Everything else (fbc, fbp, gbraid) needs your own hidden fields.
  3. Third-party forms (Webflow, WordPress, Unbounce, custom). Add hidden inputs, fill them from the URL and cookies, and include them in the API call that creates the lead. Zoho's docs say to pass the gclid as $gclid for the built-in integration.

Which Zoho lead statuses and deal stages should become conversions?

Pick two or three stages that sales actually maintains, that happen often enough to train on, and fast enough to fit the upload windows. A stage nobody updates teaches the platform that good campaigns produce nothing.

Zoho triggerGoogle Ads conversion actionMeta eventValue
Lead created from a web formKeep the tag-based form conversion (secondary)Lead (browser + server, deduplicated)None, or a small fixed value
Lead Status set to your qualified status, or lead convertedQualified lead (offline import, primary)Custom event such as QualifiedLeadExpected value: average deal size × close rate from qualified
Deal stage set to Proposal/Price QuoteProposal sent (optional, secondary)Custom event such as ProposalSentExpected value at that stage
Deal stage set to Closed WonClosed deal (offline import, primary)PurchaseActual deal Amount, in USD

Proxy values matter. If qualified leads close 20% of the time at $8,000 on average, each is worth about $1,600, and sending that lets value-based bidding work before deals close. If deals take four months, Closed Won falls outside Google's click window, so the qualified stage carries the optimization.

Does Zoho CRM's built-in Google Ads integration handle this?

Partly, and only for Google. Zoho's help docs describe a Google Ads integration (set up from Setup, Marketplace, Google, Google Ads) that pushes three fixed conversions: a lead or contact created, a lead converted (qualification), and a deal won, with the deal Amount sent as the value on the won conversion. The same docs list its limits:

  • Data is pushed to Google Ads once every 24 hours, at a scheduled hour.
  • Up to 5 client accounts; no multiple MCCs or cross-account conversion tracking.
  • The Campaigns module must be on, and its conversion names in Google Ads can't be renamed.
  • Conversions fail past 90 days from the click, or on a gclid mismatch, and failure logs last 7 days.

The docs don't mention gbraid/wbraid, enhanced conversions for leads or Meta, and the Marketplace listing carries an edition restriction, so check your plan. It's a fine start for a Google-only account on a short sales cycle. For custom stages, proxy values, iOS clicks, hashed-email matching or Meta, you need your own pipeline, which is what our CRM and offline conversion tracking service builds.

How do you send Zoho conversions to Google Ads with your own pipeline?

Trigger on the stage change in Zoho, hand the record to a server endpoint, and upload a click conversion carrying the gclid (or gbraid/wbraid) plus hashed email and phone. That's enhanced conversions for leads, and it lets leads without a stored click ID still match.

  1. Create the conversion actions as imports from clicks, one per stage. Accept the customer data terms in conversion settings; Google says enhanced conversions for leads won't work without them.
  2. Add a Zoho workflow rule on Leads (status update) and Deals (stage update). Zoho caps a webhook at 10 CRM fields, tight once you add click IDs, so a Deluge function calling invokeurl is usually cleaner.
  3. Post to your endpoint (a cloud function or server-side GTM container), which normalizes, hashes and calls Google.
  4. Upload with the right fields. The click ID you have, conversion_date_time as yyyy-mm-dd HH:mm:ss+|-HH:mm (when the stage changed), value, currency, an order_id and the consent field, both of which Google's API docs recommend.
  5. Upload daily, including leads you can't tie to an ad; Google's checklist says enhanced conversions for leads depends on it.

The tag-side half is in our enhanced conversions setup guide.

How do you send Zoho lead stages to Meta's Conversions API?

Send each stage change as a server event to your Meta dataset, with hashed email and phone plus the stored fbc and fbp, from the same endpoint that handles Google. Meta's CRM integration for the Conversion Leads goal is, per its developer docs, only for Lead Ads (Instant Forms): it keys on the 15–17 digit Meta lead ID and expects at least 200 leads a month, daily uploads and a target stage within 28 days. For website leads, send regular Conversions API events:

{
  "data": [{
    "event_name": "QualifiedLead",
    "event_time": 1760018400,
    "action_source": "system_generated",
    "event_id": "zoho_lead_4770000001234_qualified",
    "user_data": {
      "em": ["<sha256 of normalized email>"],
      "ph": ["<sha256 of E.164 digits>"],
      "external_id": ["<sha256 of Zoho record ID>"],
      "fbc": "fb.1.1759400000000.<fbclid>",
      "fbp": "fb.1.1759400000000.1234567890"
    },
    "custom_data": { "value": 1600, "currency": "USD" }
  }]
}

Pick an action_source that honestly describes the stage change; Meta's reference includes phone_call, system_generated and other. Don't label it website, which requires a source URL you won't have. Confirm in Events Manager that the event is selectable for your campaign's optimization before switching. How pixel and server events fit together is in Meta Pixel vs Conversions API.

What are the timing windows, and how do you avoid duplicate conversions?

Short enough that real-time triggers beat nightly batches. Current numbers from each vendor's docs:

Platform ruleLimitWhat it means for Zoho
Google click conversion import (gclid)Uploaded within 90 days of the last clickClosed Won after 90 days is lost; lean on the qualified stage
Google enhanced conversions for leadsUploaded within 63 days of the last clickTighter still; upload daily
Meta Conversions API event_timeNo more than 7 days in the past, or the whole request is rejectedFire on the stage change, and never batch-backfill old deals
Meta deduplicationMatching event_name + event_id within 48 hoursApplies to the browser/server Lead pair
Zoho built-in integrationOne push every 24 hoursFine for Google, adds a day of lag

Duplicates come from three places. The browser and server Lead: generate one event ID at submit, send it with the pixel, store it in Zoho, reuse it server-side. A stage set, unset and set again: build the ID from record and stage (zoho_deal_<id>_closedwon) and reuse it as Google's order_id; Google's docs say re-uploaded events are removed as duplicates. And running Zoho's built-in integration alongside your own pipeline, which counts every deal twice. Pick one per conversion.

How do you handle CCPA/CPRA opt-outs and hashed customer data?

Record the opt-out on the Zoho record and check it before anything leaves your server. CCPA/CPRA lets California consumers opt out of sharing for cross-context behavioral advertising, other states have similar rights, and a hashed email is still personal information.

  • At submit, read your "Do Not Sell or Share" choice and navigator.globalPrivacyControl into an Ad Opt-Out field in Zoho.
  • Google: the simplest defensible rule is to skip opted-out records.
  • Meta: skip them, or send data_processing_options: ["LDU"] with country and state set to 0 for Limited Data Use.
  • Hash at send time with SHA-256 after normalizing: trimmed, lowercased email; phone in E.164. Click IDs, fbc and fbp stay unhashed.

This isn't legal advice; have counsel review your privacy policy wording.

Why does first-party server-side tracking fix what the default setup misses?

Because the weak link in a Zoho setup is capture, not upload, and capture runs on the browser JavaScript that Safari and blockers degrade.

  • Click IDs survive longer. Safari caps JavaScript-set cookies at seven days, so a lead who clicks, leaves and returns on day ten to fill the form arrives with no click ID. A server-side GTM container on your own subdomain sets that cookie from the server as first-party, which lasts longer (if the tagging server's IP doesn't match your site's, Safari caps it too).
  • One event ID, two paths. The container emits browser and server Lead events with a shared event_id and writes it to Zoho, so deduplication is designed in.
  • Better matching for leads with no click ID. The endpoint receiving Zoho's Deluge call hashes first-party email and phone correctly every time, rescuing matches when the gclid or fbc is missing.
  • One place for opt-outs. Every Google and Meta call passes your server, so the opt-out check happens once and can be audited.

Frequently asked questions

Do I need Zoho CRM Enterprise to send offline conversions?

A custom pipeline needs workflow rules plus webhooks or Deluge functions, and Zoho's webhook call limits vary by edition. The built-in Google Ads integration has its own edition restriction, so check your plan.

Can I import Zoho conversions into Google Ads without a gclid?

Yes, with enhanced conversions for leads, which matches on hashed email or phone. Still include the gclid whenever you have it.

What happens if a deal closes after 90 days?

Google won't import it against the click. Optimize on a stage that reliably happens inside the window, such as qualified or proposal sent, and treat Closed Won as a reporting signal.

Should my qualified-lead conversion replace the form-fill conversion?

Yes, once qualified volume is steady. Switching on a handful of qualified leads a month can starve the bidding model.

Can Meta optimize website campaigns on Zoho deal stages?

The Conversion Leads goal only works with Instant Forms. For website leads, send stages as Conversions API events and confirm in Events Manager that the event can be selected for optimization.

Is it safe to send customer emails to Google and Meta?

Only hashed, only for people who haven't opted out, and only if your privacy policy discloses it.

If your ads still optimize on form fills while Zoho knows which leads closed, we can rebuild the loop on first-party server-side tracking: click-ID capture, stage mapping, Google and Meta uploads, opt-outs. About 98% accuracy is typical, and we guarantee 95% or better. Tell us about your setup and we'll show you where the gaps are.

  • zoho crm
  • offline conversions
  • google ads
  • meta conversions api
  • enhanced conversions for leads
SETUP GUIDES

Guides for this topic

How accurate is your conversion tracking?

PLATFORM-REPORTEDconversionsdivided byBACKENDreal orders or leadsequalsaccuracy
TRY IT · YOUR NUMBERS
68%Broken. Something is missing entirely. Worth a free audit.
Reading guides because something is broken?Book 30 minutes with Ariful. We'll find it on the call and send a written fix list within 24 hours.
Get my free audit →
Ariful Islam
WRITTEN BYAriful IslamFounder of Tracking Consulting and a computer engineer (Diploma, BSc, MSc in CSE). 300+ clients and 1,000+ tracking projects since 2019.
About Ariful →
FREE · 30-MIN CALL · WRITTEN AUDIT IN 24H

Want us to check your accuracy for you?

We look at your setup together on the call. Within 24 hours you get a written audit and a prioritized fix list you can hand to any developer. Not a fit? We'll say so.