lead generation • conversions api
Conversions API for CRM: Lead Stages Meta Can Learn From
Meta's Conversions API for CRM lets your CRM send each lead's progress, such as qualified, booked and won, back to Meta, so your campaigns can learn from real outcomes instead of form fills. To use it well you need the Meta lead ID or good customer details on every lead, stages your team updates daily, and one quality stage that happens within 28 days and converts between 1% and 40% of leads.
01 • the idea
What is the Conversions API for CRM?
It is Meta's method for sending lead stage events from your CRM to Meta. A lead stage is a step in your sales process, like 'contacted' or 'won'. Meta matches each event to the original lead and uses it to understand which leads were good.
Event flow • crm to meta
- 01
Ad
Someone clicks your Meta ad.
- 02
Website or form
They fill in a form. The pixel can record a Lead.
- 03
CRM
The lead is saved and moves through your sales stages.
- 04
Conversions API
Your server sends each stage to Meta.
- 05
Meta
Ads learn which clicks became real customers.
Meta's page says integrating your CRM with the Conversion Leads goal 'may yield higher quality leads that are more likely to convert'. It is worth doing for the reporting alone, even before you optimise for it.
02 • requirements
What does Meta need before CRM events work well?
- Leads from Facebook or Instagram lead ads (instant forms) for the Conversion Leads goal
- The 15–17 digit Meta lead ID stored in your CRM (recommended), or customer details such as email, phone or click ID
- At least 200 leads a month (GoHighLevel's help article says 250)
- Data uploaded at least once a day
- A target stage reached within 28 days of the lead
- A target stage conversion rate between 1% and 40%
Not using instant forms?
You can still send CRM stages for leads from your website. They improve your reporting and give Meta more signal, but the Conversion Leads optimisation goal itself is for instant-form lead ads.
03 • which stages
Which lead stages should I send to Meta?
| Stage | Send? | Notes |
|---|---|---|
| New lead | Yes | Usually already sent as Lead |
| Contacted | Optional | Useful if many leads never answer |
| Qualified | Yes | Often a good quality signal |
| Booked (call, visit, tour) | Yes | Often the best quality signal |
| Won | Yes, with value | Your business result |
| Lost / disqualified | Usually no | Keep in the CRM for your own reports |
Keep stage names stable. If you rename stages every month, Meta sees new events every month and learns little. Choosing the quality stage is covered in Meta Conversion Leads optimisation.
04 • how to connect
How do I connect my CRM to Meta's Conversions API?
- 1In Meta Events Manager, connect a CRM data source to your dataset.
- 2In your CRM, store the Meta lead ID on every instant-form lead, plus email and phone.
- 3Set up the sending method: a built-in CRM action (GoHighLevel has one), a partner connector, or server code for a custom CRM.
- 4Send an event each time a lead changes stage, within 7 days of the change. Meta's server event documentation rejects events more than 7 days old.
- 5Test with a test lead and check the events arrive in Events Manager.
For GoHighLevel specifically, see GoHighLevel Meta Conversions API setup. For a custom CRM, see GoHighLevel vs a custom CRM.
05 • inside an event
What does a CRM stage event actually contain?
A CRM stage event is a small message from your CRM to Meta. It says what happened, when, and who it happened to, in a format Meta can match.
| Part | Example | Notes |
|---|---|---|
| Event name | Qualified, Booked, Won | Keep names stable over time |
| Event time | The moment the stage changed | No more than 7 days before sending |
| Lead ID | A 15–17 digit Meta lead ID | Best match for instant-form leads |
| Customer details | Hashed email and phone | Used when no lead ID is available |
| Event ID | Unique per lead and stage | Prevents double counting |
| Value (won stage) | 8500 USD | Lets Meta weigh bigger sales |
Meta's developer page describes the integration and links to its implementation guide for the exact field names. If you use GoHighLevel or a connector, most of these fields are filled in for you; with a custom CRM they are set in code.
06 • key terms
Which terms do I need to know?
Short, plain definitions of the terms used on this page.
| Term | What it means |
|---|---|
| Conversions API (CAPI) | Meta's way for your server or CRM to send events directly to Meta |
| CRM | The system where you store leads and track their sales stages |
| Lead stage | A step in your sales process, such as qualified, booked or won |
| Meta lead ID | The 15–17 digit ID Meta gives each instant-form lead |
| Instant form | A lead form that opens inside Facebook or Instagram |
| Conversion Leads | Meta's optimisation that targets people likely to reach a later CRM stage |
07 • what goes wrong
What are the common mistakes with CRM events?
- Stages updated weekly or monthly, so events arrive too late.
- Leads entered by hand without the Meta lead ID, so Meta cannot match them.
- Every lead pushed to 'won' at the end of the month to tidy the pipeline, which teaches Meta nonsense.
- Non-ad leads (referrals, walk-ins) sent to Meta as if they came from ads.
- Health or sensitive details included in event names or fields.
Want to know whether your CRM can send these events today? Ask for the free tracking check.
Free tracking checksee what meta actually receives
Free tracking check
I review which events your Meta ads actually receive and what is missing, then send you a short written summary. No calls required, and no promise of results: just a clear picture of your tracking.
questions
Frequently asked questions
01. Do I need instant forms to send CRM events?
+
No, but Meta's Conversion Leads optimisation goal works only with instant-form lead ads. Website leads can still send CRM events for reporting and signal.
02. How many leads do I need?
+
Meta's developer page says at least 200 a month for Conversion Leads; GoHighLevel's article says 250.
03. How often should CRM events be sent?
+
At least daily. Meta rejects events more than 7 days after they happened.
04. What is the Meta lead ID?
+
A 15–17 digit ID Meta gives each instant-form lead. Storing it lets Meta match later stages to the exact lead.
05. Can I send sales values?
+
Yes. Send the won stage or a Purchase event with the value and currency.
Sources
Checked on 21 October 2026. Pages change, so read the current version before you act.
- 1.Meta for Developers: Conversions API for CRM integration (Conversion Leads)
- 2.Meta for Developers: Conversions API server event parameters (event_time, action_source)
- 3.HighLevel Support: Facebook Conversions API Lead Event Walkthrough (updated 1 June 2026)
- 4.Meta for Developers: Conversions API best practices (Event Match Quality, redundant setup)
Read next
PrimeBuild is not affiliated with any company, platform or website named on this page. Names and links are given only so you can check them yourself.