Zoho CRM integration
Zoho CRM is on the map, not in the product yet.
Read-only contact and deal attribution for businesses that run on Zoho.
How it works
Zoho CRM connects through OAuth 2.0 with granular module scopes, specifically read access to Contacts and Deals, against Zoho's API v8. The integration reads those modules and attributes contacts and deals to the organic landing pages behind them, so a business run on Zoho gets the same content-to-pipeline story as one on Salesforce or HubSpot. Nothing is written back.
In the loop, Zoho CRM is the measure step for the Zoho-run business. Pages are credited with the contacts and deals they produce, the opportunity engine weighs topics by those outcomes, and the reporting speaks in pipeline rather than proxy metrics.
Best forBusinesses running on Zoho CRM who want organic content measured against real contacts and deals.
Setup, step by step
- Click Connect on the Zoho CRM card and pick your account's region in the connector, since Zoho accounts live on region-specific domains.
- Sign in to Zoho and approve the read scopes for Contacts and Deals.
- Confirm the lead source fields that mark organic arrivals in your modules.
- Review the first attribution report tying recent contacts and deals to landing pages.
- Check the connection status panel, which confirms the region and scopes in use.
Best practices
Pick the right region first
Zoho runs separate data centers with region-specific account domains, and OAuth must go to yours. The region picker at the start of our flow exists for exactly this; choose where your account actually lives.
Grant only what the consent screen shows
The request is scoped to reading Contacts and Deals, and the consent screen lists precisely that. If a request ever seemed to want more, decline it; narrow scopes are the deal here.
Keep lead source values consistent
Attribution matches on your lead source data, and consistent values beat creative ones. A short, agreed list of source values in your CRM keeps the organic trail machine-readable.
Reconnect after account migrations
Moving your Zoho account between plans or data centers can invalidate the grant. If reports go quiet after an account change, a reconnect through the same flow restores the read in minutes.
Known issues
What practitioners actually report, from official docs, issue trackers, and community forums.
Multi-datacenter OAuth complicates connecting
Zoho accounts live on region-specific accounts domains, and an OAuth request aimed at the wrong region fails in ways that look like a broken login.
How we handle itThe connect flow starts with a region picker and routes the OAuth request to your data center, so the region question is answered once, up front, instead of surfacing as a mystery error.
zoho.com
Reads are bounded by the granted module scopes
API v8 enforces module-level scopes, so a grant missing a module read leaves that module invisible and attribution incomplete.
How we handle itWe request exactly the Contacts and Deals read scopes and verify both with a test read at connect, so a partial grant is caught during setup rather than discovered as missing data later.
zoho.com
Questions teams ask
- Can SearchHandled write to our Zoho CRM?
No. The OAuth grant covers reading Contacts and Deals only, and Zoho enforces those scopes on its side. Records, fields, and workflows stay untouched.
- Why does the connector ask for our region?
Zoho operates separate data centers with their own account domains, and the OAuth flow must target yours. Picking the region up front is what makes the sign-in work on the first try.
- What if we do not use Zoho CRM?
GA4 conversion tracking is the fallback measure, and the Salesforce, HubSpot, Pipedrive, Close, and Attio integrations cover the other CRMs we support.
Not connectable yet
Start with the plan, not the connector.
Build a Growth Map from your site to see the work itself. Approved pages can leave through the export or the webhook today, and telling us Zoho CRM matters moves it up the rollout.