Meta ads

Meta Conversions API for CRM: better leads from the same ad budget

What the Meta Conversions API is, why lead-ad advertisers need it, which CRM stages to send, and how to set it up without a developer.

4 Nov 2026 · CloseLyt Team

Meta's algorithm learns from the signals you give it. If the only signal is "someone filled the form", Meta finds more form-fillers — including people who never pick up. The Conversions API (CAPI) for CRM fixes that.

What it is

The Conversions API lets your CRM send events to Meta from the server: this lead was contacted, this one qualified, this one bought, this one was junk. Meta matches them to the lead that came from your ad and learns what a good lead looks like.

Which stages to send

A good funnel sends both the positive and the negative:

  • Lead → Contacted → Interested → Qualified → Meeting / site visit → Proposal → Purchase
  • Not interested, Lost and Disqualified (bad leads)

Sending bad leads is just as important — it tells Meta who *not* to find. See map your stages to Meta.

Do it right

  • Send each event once per lead — duplicates confuse Meta.
  • Include Meta's lead ID and phone number with country code so matches are accurate.
  • Send from every place a stage changes — web, mobile app, bulk edits and imports.
  • Match your campaign goal: if your campaign maximises *qualified leads*, your qualified stage must send that event.

No developer needed

In CloseLyt, connect Meta, pick your dataset, and each stage's Meta event is shown in brackets — e.g. *Qualified lead (Meta: QUALIFIED)*. Every stage change then reaches your own Meta dataset automatically. Check deliveries in the event log.

Read more: What the Conversions API does for you · CRM for Meta ads · Pricing

Keep reading

All articles