How to Send Lead Quality Back to Meta with the Conversions API

Quick answer: To send lead quality back to Meta, record what happens to each lead after the form (for example contacted, qualified, converted) and send those stages to Meta as events through the Conversions API, matched to the original lead. Meta can then optimise campaigns for leads that become customers, using the Conversion leads performance goal. In LeadSmart you do this by mapping your lead labels to Meta events: when you label a lead, the mapped event is sent to Meta automatically, with Meta's lead ID, so it works with the Conversion leads goal.

A Facebook lead ad campaign optimised for "Leads" learns one thing: who fills in forms. It never learns that half of those people did not answer, or that one ad set brings buyers while another brings browsers. Sending lead quality back closes that gap. It is the single most useful change for businesses whose leads look cheap in Ads Manager but expensive in the sales team.

What does "sending lead quality back to Meta" mean?

After a lead arrives, your team works it: calls, qualifies, books a meeting, closes. Each of those moments is a stage. When you send a stage to Meta as a server event, with an identifier that ties it to the original lead, Meta can connect "this person filled in the form" with "this person became qualified". Meta calls this approach Conversions API for CRM, and the campaign goal that uses it is Conversion leads.

Why does it improve lead quality?

• Better optimisation: Meta can look for people who resemble your qualified leads, not just your form fillers.
• Clearer reporting: you can see which campaigns produce qualified leads, not just cheap ones.
• Less waste: money moves away from audiences and placements that only produce junk.

It does not fix a bad offer or a slow callback. Use it together with good form settings, covered in how to get quality leads from Facebook lead forms.

What does Meta need?

Meta's guidance for the Conversion leads goal, as summarised by integration partners such as Make, includes these points:

• Leads must come from Meta's own instant forms (Facebook or Instagram lead ads).
• You keep Meta's lead ID for each lead, because stage events are matched using it.
• You send events promptly, starting when the lead is received and then as stages change.
• Volume: commonly cited as at least 200 leads a month.
• The stage you optimise for should happen within 28 days of the lead and convert at roughly 1% to 40% of leads.

Meta updates these rules, so check the current requirements in Events Manager before switching an ad set's goal. Even below the volume guidance, sending stage events still gives you better reporting on which campaigns bring good leads.

What does a CRM event look like?

For reference, a CRM stage event sent to the Conversions API looks roughly like this. You do not need to write it yourself if a tool sends it for you.

{
  "event_name": "Qualified",
  "event_time": 1792540800,
  "action_source": "system_generated",
  "user_data": { "lead_id": 1234567890123456 },
  "custom_data": {
    "event_source": "crm",
    "lead_event_source": "Your CRM name"
  }
}

The important parts are the stage name, the time it happened, the lead ID that links it to the form submission, and the fields that mark it as a CRM event.

How to send lead quality back to Meta with LeadSmart

LeadSmart captures every lead from your Facebook and Instagram instant forms, so each lead in your dashboard comes from Meta's own form. LeadSmart's Conversions API events include Meta's lead ID, so they work with Meta's Conversion leads optimisation goal. You map your labels to Meta events once, with no developer needed, and from then on your team only has to label leads as they work them.

1. Connect your Meta Pixel / dataset for Conversions API events.
2. Connect your Facebook Page and choose your lead forms. New leads appear in the LeadSmart dashboard, in Google Sheets and on your WhatsApp alert.
3. Decide your stages. Keep them few and consistent, for example "Contacted", "Qualified", "Visit booked" and "Converted".
4. Map each label to a Meta event. Choose which Meta event each label should send.
5. Label leads as you work them. When someone labels a lead, LeadSmart sends the mapped event to Meta, including Meta's lead ID, so Meta can match it to the original form submission.
6. Check Events Manager. Confirm the events are arriving for your dataset before you change any campaign settings.

Example label-to-event mapping

The right stages depend on your business. Here are examples for common industries:

Pick the stage you most want more of as your optimisation target, usually the first stage that clearly separates real buyers from the rest, such as "Qualified" or "Site visit booked". It needs to happen often enough and soon enough to meet Meta's guidance.

See how this works for real estate, education and solar businesses.

Switching a campaign to Conversion leads

Because LeadSmart's events carry Meta's lead ID, you can use them with the Conversion leads goal. Once your stage events have been arriving reliably for a while and you meet Meta's volume guidance, you can test it:

1. In Ads Manager, create or edit a Leads campaign that uses instant forms.
2. At the ad set level, choose the Conversion leads performance goal.
3. Select the dataset that receives your CRM events and the stage you want to optimise for.
4. Run it alongside your existing ad set for a few weeks and compare cost per qualified lead, not cost per lead.

Expect cost per lead to rise. What matters is whether more of those leads reach your target stage.

Common mistakes

• Too many stages. Ten labels used inconsistently send noise. Four or five used every day send signal.
• Labelling late. Stages entered weeks later miss Meta's 28-day window. Label during the call.
• Losing the lead ID. Leads copied by hand into a sheet without Meta's lead ID cannot be matched.
• Judging too early. Give a Conversion leads test enough time and budget before deciding.

Website leads are different: if your leads come from a landing page instead of an instant form, use Pixel and Conversions API website events. See our guide to setting up Meta Conversions API using Google Tag Manager.

Questions and answers