Meta Conversions API for CRM, in plain words: teach Meta which leads were real
Meta can optimise lead ads for leads that become customers, not just form fills. What the Conversions API for CRM is, what Meta requires before it works, and which stages to send.
By default, a lead campaign on Meta learns one thing: who submits forms. If many of those people never answer the phone, Meta keeps finding more of them, because nobody told it otherwise.
The Conversions API for CRM is how you tell it.
What it is
The Conversions API for CRM lets you send events from your CRM back to Meta: this lead was qualified, this one booked, this one bought. It is a separate setup from the Conversions API you may use for your website, with different required fields, because the data comes from your lead list rather than from web pages.
Once Meta has these events, you can choose the Conversion leads performance goal for your lead campaigns. Meta then optimises delivery towards people who are likely to reach the stage you choose, instead of people who are likely to fill the form. Meta says this "may yield higher quality leads that are more likely to convert."
What Meta requires
Meta's documentation lists these conditions for the Conversion leads goal:
- Instant forms only. It works with Facebook and Instagram lead ads that use instant forms.
- Keep the lead ID. Store Meta's 15 to 17 digit lead ID with each lead in your CRM, and send it with each event. If you do not have it, you can send customer details such as phone number or email instead.
- Enough volume. At least 200 leads per month.
- Daily uploads. Send data at least once per day.
- A stage that happens in time. The stage you optimise for should happen within 28 days of the lead.
- A stage that is neither too rare nor too common. Its conversion rate should be between 1% and 40%.
That last rule catches a lot of businesses. If you only send "sale" and 0.5% of leads buy, there is not enough signal. If you send "contacted" and 90% of leads reach it, there is nothing to learn. Pick a middle stage, such as qualified or booked.
Which stages to send
Send every stage you track, in order, as it happens. A typical local business might send:
- Valid: passed basic checks (working number, not a duplicate, in your area).
- Qualified: spoke to the person and they have a real need.
- Booked: an appointment or site visit is fixed.
- Showed: they came.
- Converted: they bought.
Sending leads that failed is useful too. Telling Meta that a lead was junk is as informative as telling it a lead was good.
Common mistakes
- Losing the lead ID when leads are copied from Meta into a spreadsheet and then into a CRM by hand.
- Updating stages in batches once a month, so events arrive long after the lead and miss the window.
- Different people using different definitions of qualified, so the signal is noisy.
- Switching to Conversion leads before the data is flowing. Send events first, check they are matched in Events Manager, then change the goal.
How Streakstone handles this
Streakstone keeps Meta's lead ID on every lead and sends each stage (valid, invalid, qualified, held, booked, showed, converted) to Meta through the Conversions API as it happens. Leads that fail a check are reported too. The Activity page shows each time a result was reported, so you can see the signal flowing. Start a 14-day trial.
Sources
- Meta for Developers: Conversions API for CRM integration