Zoho
Overview
Section titled “Overview”Signals reads leads and their status changes from Zoho on a schedule and sends the fields you mapped on to your ad platforms.
Both Zoho CRM Standard and Zoho Bigin are supported, and you choose between them during authentication. They are separate products with separate data, so the choice is not cosmetic.
The Leads module is supported. It holds both the contact details destinations match on and the status that carries the outcome.
Supported destinations
Section titled “Supported destinations”Destinations supported by Zoho
| Category | Supported |
|---|---|
| Offline Conversions | |
| Lead Conversions | |
| Custom Audience |
Prerequisites
Section titled “Prerequisites”- A Zoho account holding the records you intend to sync, in the module you intend to read: Leads. The fields you intend to map must already exist.
- Administrator access to your Zoho CRM organization, on an edition that includes API access (Standard or above). You need it to authorize Datahash and grant read access to your modules and records.
- A single-select picklist on the Leads module holding each lead’s stage, such as New, Contacted, Qualified, Won or Lost. Each value maps to a conversion event, so a lead left on a stale stage reports the wrong one.
Authentication
Section titled “Authentication”In Studio, open Sources, find the CRM category, and click the Zoho CRM tile. This connector uses single sign-on. You never enter Zoho credentials into Datahash.
- Choose the product: Zoho CRM Standard or Zoho Bigin.
- Click Sign in with Zoho.
- Choose the Zoho organization. Zoho groups these as Production, Sandbox and Developer, so check you are not about to read a sandbox.
- Accept the requested permissions, which cover read access to your CRM records along with modules, fields, users and organization settings.
If the consent screen refuses the request, the account almost certainly lacks the Zoho Admin role. Have an administrator complete this step rather than broadening a normal user’s permissions.
Configuration
Section titled “Configuration”Instance Setup
Section titled “Instance Setup”Select the Integration Type based on where the data needs to be sent. The options are Offline Events, Audience, Meta CAPI CRM, Google Leads, TikTok Leads, Snapchat Leads and LinkedIn Leads. The choice decides which fields you are asked to map and which destinations the connection can feed, so settle it first. Then choose the Leads module and give the instance a name.
Field mapping
Section titled “Field mapping”Map your Zoho fields onto the schema Signals expects. Each field is a dropdown of your own fields, so nothing has to be renamed in the CRM. What you are asked to map depends on the integration type.
| Group | Fields |
|---|---|
| Configuration | Event name, event time, last modified date, lead lifecycle stage. |
| Personal information | Email, phone, first name, last name, city, state, country, postcode, gender, date of birth, Facebook click ID, Google click ID, OpenAI identifier, source URL. |
| Product | Total value, currency, product type, name, category, ID, brand, price, quantity, transaction ID, number of items. |
Test connection
Section titled “Test connection”Click Test Connection before finishing. It checks both that the credentials still work and that the mapped fields actually contain data, so a mapping pointed at an empty field fails here rather than silently later.
Manage instance
Section titled “Manage instance”One instance is configured for one integration type. To feed a different integration type, configure it on a new instance from the Manage existing instance table. To change an existing one, open it from the Manage existing instance table, click the edit option in the menu to the top right, update the fields and click Finish.
Data & identifiers
Section titled “Data & identifiers”Only the fields you map are read. Personal identifiers are normalized and SHA-256 hashed before they are sent to any destination.
Email, phone, name and location are what destinations match on. Value, currency and product fields describe the conversion rather than the person, so they do not affect match rates.
Best practices
Section titled “Best practices”- If you map a platform lead ID such as the Meta Lead ID, keep that field as text. A numeric field truncates long IDs, which is the most common cause of lead conversions never matching.
- Confirm you selected the production organization and not a sandbox. Both appear in the same list and the names are often similar.
- Ensure the module holds personal information such as email address and phone number. Destinations weight these highest, so records without them match at a much lower rate.
- Maintaining consistent formatting in Zoho helps match rates: email addresses in lowercase, phone numbers in E.164 format, and no trailing spaces.
Troubleshooting & FAQ
Section titled “Troubleshooting & FAQ”I connected Zoho Standard CRM but my records are in Bigin. Zoho CRM and Bigin are separate products. We support both Zoho CRM and Zoho Bigin. Reconnect with the other one selected.
Match rates are low. Map more identifiers and fix formatting at source. A hash only matches if both sides normalized the value the same way.