How to Send CRM Sales to Meta with the Conversions API (HubSpot, Pipedrive, Kommo, Zapier)
For most lead-generation businesses, Meta Ads optimizes for the wrong thing. It sees form submissions. It doesn't see which of those people answered the phone, came to a meeting, or paid. So it keeps finding more people who fill in forms — not more people who buy.
Sending your CRM stages to Meta through the Conversions API fixes that. This article covers what you need, how the matching works, and the practical ways to connect your CRM.
What changes when Meta sees CRM data
- Optimization: you can optimize campaigns for meetings booked or deals paid instead of raw leads.
- Reporting: Ads Manager shows purchases and revenue per campaign and per ad, so you can calculate real ROAS — not "cost per form."
- Quality control: sending negative outcomes (spam, no answer, disqualified) shows which campaigns bring junk.
How Meta connects a CRM deal to an ad click
Meta doesn't know your CRM's deal ID. It matches events to people using identifiers. The more you send, the better the match:
- Email and phone (hashed with SHA-256 before sending) — the most important ones.
- Click ID — the
fbclidfrom the ad link, sent asfbc. It ties the deal to the exact click. - Browser ID — the
_fbpcookie. - Name, city, country and your own
external_id— extra signals. - Lead ID — if the lead came from a Meta Instant Form, its
lead_idlinks the deal directly to that form submission.
The catch: the click ID exists only in the browser at the moment of the visit. If your form doesn't save it, it's gone. That's why CRM integrations work best together with a small website script that stores fbclid and cookies in hidden form fields and passes them to the CRM.
The one rule that breaks most DIY setups: 7 days
Meta accepts an event only if its event_time is no more than 7 days in the past at the moment you send it. If even one event in a batch is older, the whole request is rejected.
So you can't export last month's sales from the CRM and upload them. You need to send each event when the deal reaches the stage — with the time the stage changed. A deal that closes 40 days after the click is fine; what matters is that you report it within 7 days of the closing.
Which stages to send
| CRM stage | Event |
|---|---|
| New lead | Lead (skip if the pixel already sends it from the form) |
| Meeting / consultation booked | Schedule |
| Contract / invoice sent | InitiateCheckout (optional) |
| Paid | Purchase + value + currency |
| Spam / no answer / disqualified | Custom events, for reporting |
Keep event names different from what the pixel sends, unless you deliberately deduplicate with a shared event_id. More on that in Conversions API vs Meta Pixel.
Ways to connect your CRM
Built-in CRM features
Some CRMs have their own Meta sync on certain plans — HubSpot, for example, can sync lifecycle stages as ad conversion events. If yours does and it supports the stages and fields you need, start there. Check whether it sends click IDs and deal values, and whether it handles the 7-day rule.
Zapier or Make
Both have Meta Conversions API modules. You build a scenario: "when a deal moves to stage X → send event Y." It works, but you'll handle hashing, field formats, deduplication and errors yourself, and every new stage is another scenario to maintain. Fine for one simple pipeline.
A dedicated integration
LeadMe was built for exactly this job. You connect your CRM — AmoCRM (Kommo), Bitrix24, HubSpot, Pipedrive, Google Sheets — or any other system through a webhook, Make or Zapier, then tick which stages become which events. LeadMe:
- normalizes and hashes email and phone;
- keeps the ad click IDs captured by its website script or WordPress plugin;
- sends
lead_idfor leads from Meta Instant Forms; - sends each event as soon as the stage changes, inside the 7-day window;
- sends the same CRM data to TikTok, Google Ads and other platforms if you advertise there too.
It also shows a "sales by ad creative" report, so you can see which ads brought paying customers, not just leads.
Custom code
Your developer listens to CRM webhooks and calls the Conversions API. Maximum control, but plan for maintenance: API version updates, retries, token rotation.
Checklist before you switch campaign optimization
- Events from the CRM arrive in Events Manager with source Server.
- Event Match Quality is "OK" or better.
- You have enough volume: Meta's learning works best with dozens of conversions per week per ad set. If
Purchaseis rare, optimize forSchedulefirst. Purchaseevents carry the deal value, so ROAS appears in Ads Manager.
Quick answers
Is this the same as Meta's "offline conversions"?
It's the modern version. Meta now recommends the Conversions API for offline and CRM events; the older Offline Conversions API is the legacy route.
My CRM is not on any integration list. Can I still do it?
Yes, if it can send a webhook or export to Google Sheets. Almost every CRM can do one of the two.
What if the customer used a different email than their Facebook account?
That's why you send several identifiers. Phone number and click ID often match when email doesn't.
Related: What Is Meta Conversions API · Set up Conversions API without a developer · Conversions API for WhatsApp