Leads, CRMs and follow-up

How do I connect Facebook lead ads to Zoho CRM?

Connect Zoho CRM from the Instant forms screen in Meta Business Suite, then check one thing: the native integration does not store Meta's lead ID, so add it.

Published

Open Meta Business Suite, go to All tools, then Instant forms, select the CRM setup tab and search for Zoho. Click Connect from website and finish the steps on the Zoho side. New leads then reach Zoho CRM automatically, with no file to download, but one detail needs attention from day one: the Zoho integration does not store Meta’s lead ID.

Connect Zoho from the Instant forms screen

  1. In Meta Business Suite, open All tools, then Instant forms.
  2. Select the CRM setup tab and search for Zoho.
  3. Click Connect from website and complete the steps on the Zoho side.
  4. Publish or refresh the form, then send one real lead through before the campaign goes live.
  5. Open the record in Zoho and confirm that the answers arrived and that no duplicate contact was created.

Three conditions decide whether this works. Only an admin of the Facebook Page who has leads access permission can connect a CRM. If someone with full control of the business portfolio has customized leads access, the CRM has to be assigned there before any lead arrives, or nothing shows up. And an entry marked “through Zapier” connects through Zapier instead, so the badge tells you which engine runs underneath.

One more thing about ownership: a connection started in Business Suite can be edited and disconnected there, while an integration set up from Zoho’s own website is managed on the Zoho side.

The catch: Meta’s lead ID

Meta publishes a table of where the lead ID ends up for each route, and the Zoho CRM Social integration is listed as not storing it. That matters more than it looks. The lead ID is the best match key when you later send pipeline stages back to Meta, and without it you are relying on email or phone matching instead.

RouteStores Meta’s lead ID?
Webhook or Graph APIYes, in the id field (leadgen_id in the webhook)
Zapier or LeadsBridgeYes, in the id field, if you map it
MakeYes, in the Lead ID field, if you map it
Salesforce Lead CaptureYes, in the Lead ID field
HubSpot Lead SyncNo
Zoho CRM Social integrationNo
Manual fileFirst column, id, with a label you may need to strip

If your reporting stops at cost per lead and nobody sends stages back to Meta, the missing ID changes little. If you plan to use qualified lead optimization, install a route that keeps it, because retrofitting means rebuilding the pipeline later.

Two ways to keep the lead ID

The first is middleware. Zapier, LeadsBridge and Make all read the Instant Form and can map the lead ID, the ad ID and the form ID into Zoho fields on the same record. Meta’s own Zapier walkthrough says plainly that storing the lead ID is required if you want to set up a Conversions API for CRM integration later, and it starts from the same CRM setup tab you used above.

Map these on day one, in a test first:

  • The lead identifier, in a searchable field rather than a note.
  • The ad identifier, plus ad set and campaign identifiers if you report above ad level.
  • The form name or identifier, so you know which offer produced the lead.
  • The creation time from Meta, not the moment the automation ran.
  • Every answer, in its own field rather than in one text block.

The second is a webhook on the Graph API. Meta posts a notification per new lead carrying the lead ID, the ad ID, the form ID, the Page ID and the time, and a separate read fetches the answers. This route needs a Meta app, App Review, Business Verification and a token whose owner holds leads access, so it is a project rather than an afternoon. It is the right choice when the lead must be scored, deduplicated against existing customers or routed by ad before Zoho sees it. The comparison of all six routes, with their limits, is in Facebook lead ads CRM integration.

Set field names and tracking parameters on the form

Two form settings save the integration work later, and both are easier before the form is published, because changing them afterwards may mean duplicating the form.

Under Settings, Field names, rename the columns to match the field IDs you use in Zoho, so Facebook leads land in the same fields as leads from every other channel. Under Settings, Tracking parameters, add name and value pairs such as utm_source = Facebook. People never see them, and they travel into downloads, into integrated CRMs and into webhook payloads.

The rule for every identifier is the same: store it as text. A numeric field turns a long identifier into a rounded one, and a rounded ID matches nothing.

Send Zoho stages back to Meta

Getting leads into Zoho is half of the loop. The other half sends each lead’s progress back to Meta, and since April 2026 Meta requires a Conversions API for CRM integration for the qualified leads performance goal on new campaigns, with existing campaigns affected from August 2026. Zoho is one of the partners Meta lists for it, alongside HubSpot, Salesforce, LeadsBridge, Make, Stape and Zapier.

The payload rules that catch people:

  1. Send one event per stage change, starting with the raw lead. A hundred leads that become seventy qualified, thirty opportunities and fifteen sales produce 215 events.
  2. Keep event_time after the lead was created and no more than 7 days before you send it.
  3. Keep batches small. One bad event discards the whole batch.
  4. Upload at least daily, and send every change rather than a snapshot of the latest stage.
  5. Validate with at least seven days of data and at least two funnel stages, three if you can.

The event name is your own stage name and the match key is the Meta lead ID where you have it, with a hashed email, a hashed phone number or a click ID as the alternative. That is the practical reason to fix the missing ID before you build anything else.

Why a download folder is not a route

Leads stay downloadable in Meta for up to 90 days. Pull the same March leads in July and you get zero rows, while the Results column keeps showing the count. Manual exports also carry extras that never appear in Results: organic leads, which exist only when the form’s sharing setting is Open, and test submissions. Leads Center exports stop at contact fields, stage, source and owner, with a maximum of 10,000 leads per file.

Keep a manual download as a backup for the day an integration breaks, as Meta itself suggests, and not as the integration.

A checklist before the campaign goes live

  1. Zoho connected from the CRM setup tab, or the middleware automation tested with a real submission.
  2. Leads access assigned to the CRM, if the portfolio has customized it.
  3. Lead ID, ad ID and form ID stored as text fields on the record.
  4. Field names matching Zoho fields, and tracking parameters added to the form.
  5. One person named to check the first day of leads arrived.
  6. The test repeated after any change to the form, because a new form is a new source.

When leads arrive and then sit untouched, the problem has moved past the integration. Leads, CRMs and follow-up covers what should happen in the first hour, and troubleshooting lead routing issues covers the case where some leads never reach the record. If you also run landing pages next to Instant Forms, the ad ID problem is the same and how to track the Facebook ad ID in your CRM shows the landing page version of it.

Questions on this topic

All questions on this topic →

FAQ

Does Zoho CRM have a native Facebook lead ads integration?+

Yes. Zoho appears in Meta's directory of CRM systems with a lead ads integration, and you connect it from the CRM setup tab of the Instant forms screen in Business Suite. Meta says new leads then arrive automatically and in real time.

Why does the Zoho integration not store the lead ID?+

Meta's own table of where the lead ID lands lists the Zoho CRM Social integration as not storing it. The lead still arrives with its answers, but the identifier that Meta uses to match a stage back to a lead is missing unless you map it yourself through another route.

Can Zoho send pipeline stages back to Meta?+

Yes, and Zoho is on Meta's list of Conversions API for CRM partners. Each stage change becomes one event, and the match key is the Meta lead ID where you have it, or a hashed email, a hashed phone number or a click ID.

What happens to Facebook leads after 90 days?+

Meta keeps Instant Form leads downloadable for up to 90 days from submission, then removes them. An integration that runs unattended is unaffected, but a manual export pulled in July returns nothing from March.

Should I connect from Business Suite or from the Zoho side?+

Either works, but they behave differently. An integration set up from the CRM's own website cannot be edited or disconnected in Business Suite, so you manage it on the Zoho side. A connection started in Business Suite stays visible there.

Ready to find out what
converts, for real?

Free to start.

Start free →