Zoho Conversion Leads

Connect Zoho CRM to Meta Conversion Leads through SignalSight — set up your CRM Pixel, map the Meta Lead ID, create a tracker, and stream funnel events back to Meta for higher-quality lead optimization.

In This Page

SignalSight Conversion Lead streams lead-stage updates from Zoho CRM to Meta in real time. When a lead moves through your sales process — from first contact to qualified, won, or lost — those events flow back to Meta so your campaigns optimize toward the outcomes that actually matter, not just form fills.

Before you start

You need a SignalSight account and admin access to your Meta Business Manager. If you haven't signed up yet, follow the Account Creation guide first.

What You Will Build

The integration has three parts: a Zoho CRM source that reads lead data from your CRM, a Meta Conversions API destination that sends CRM events back to Meta, and a tracker that connects them. SignalSight handles the server-side pipeline — no custom backend code required.

  • A Meta CRM Pixel dedicated to CRM events (separate from your web Pixel).
  • A Meta Lead ID field mapped in Zoho so every CRM event can be matched to the original Facebook lead.
  • A SignalSight tracker with Zoho as source and Meta CAPI as destination.

Meta Prerequisites

Before connecting Zoho, gather your Meta credentials. You will need a Pixel ID and an access token for the CRM Pixel you create in the next section.

Create a Meta CRM Pixel

Conversion Leads requires a Pixel configured for CRM data — not the same Pixel you use for website events. Admin access in Events Manager is required.

  1. In Events Manager, click Connect Data Sources and select CRM, then Connect.
  2. Create a new Pixel (recommended) so CRM events stay separate from your web Pixel and are easier to troubleshoot. Alternatively, convert an existing Pixel — this won't affect web events already flowing to it, but give CRM events distinct names to avoid confusion.
  3. Confirm the Pixel icon updates to reflect the CRM data source type.

Note

The integration is Pixel-based. Once setup is complete, do not switch to a different Pixel — all CRM events must continue flowing to the same one.

Map the Meta Lead ID in Zoho

The lead_id is a mandatory field in the Conversion Leads integration. It is the unique 15–16 digit identifier Meta assigns to every lead generated through Instant Forms or Lead Ads. SignalSight uses it to match CRM stage updates back to the original Facebook lead.

Where you find the lead_id depends on how you download leads from Meta. Common locations include the id column in a CSV export, the Lead ID field in the Leads Center, or a custom field if your integration already stores it. Map this value to a dedicated field in Zoho before you proceed — without it, events cannot be uploaded back to Meta.

Note

During Zoho source setup in SignalSight, you will map your Zoho field (for example, a custom Leadgen ID or Skype ID field) to the Meta Lead ID. Choose whichever field already stores the Facebook lead identifier in your CRM.

Create a Tracker

Open the SignalSight dashboard and click Tracker Creation Wizard under Signal in the left menu. The wizard walks you through source creation, destination setup, and tracker naming in three steps.

Step 1 — Zoho Source

Select Zoho CRM as your source type and give it a descriptive name. Click Zoho Login to authenticate — a popup opens where you sign in to the Zoho account you want to connect.

  1. Grant the requested CRM permissions when prompted.
  2. Map your Zoho fields to the SignalSight fields on the left. At minimum, map the field that holds the Meta Lead ID.
  3. Save the source and click Next to continue.

Step 2 — Meta CAPI Destination

Create a Meta Conversions API destination. You have two options:

  • Manual entry — enter your CRM Pixel ID and access token directly, then save.
  • Connect Facebook CAPI — sign in with your Meta account and select the Pixel from the list. SignalSight pulls the credentials automatically.

Step 3 — Name and Complete

Give your tracker a name, review the source and destination summary, and finish the wizard. Your tracker detail screen shows the connected Zoho source and Meta CAPI destination — CRM events will start flowing once leads move through your mapped stages.

Add Zoho to an Existing Tracker

If you already have a tracker with a Meta destination, you can add a Zoho source without creating a new tracker from scratch.

  1. Go to Trackers in the left menu and open the tracker you want to extend.
  2. Click Add New Source on the tracker detail screen.
  3. Choose an existing Zoho source from the list, or select Create New to set up a fresh Zoho CRM connection.
  4. Complete the authentication and field mapping steps, then save.

The tracker now sends events from both your original source and Zoho CRM to the connected Meta destination.

What Happens Next

Once CRM events start flowing, Meta enters a validation period before you can optimize campaigns. The three guides below cover everything that comes after tracker setup:

Frequently Asked Questions

Can I use the same Pixel for web events and CRM events?

Meta supports converting an existing web Pixel to also accept CRM events, but we recommend creating a dedicated CRM Pixel. Separating the two makes troubleshooting easier and prevents CRM events from overlapping with website events in Events Manager.

What happens if the Meta Lead ID is missing from a Zoho record?

Events without a valid lead_id cannot be matched back to Meta and will be rejected during the validation phase. Make sure every lead that originated from Meta has the lead_id stored in Zoho before CRM stage updates are sent.

Do I need to write code to connect Zoho CRM?

No. SignalSight handles the integration through OAuth authentication and field mapping in the dashboard. You authenticate your Zoho account, map the required fields, and events flow automatically as leads progress through your CRM.

Can I add Zoho to a tracker that already has other sources?

Yes. Open the tracker detail screen and use Add New Source to connect Zoho alongside any existing sources. All connected sources feed into the same Meta destination.