Connecting your Meta pixel tells the CRM how to talk to Meta. It does not tell it when. That is a separate step, done from Marketing → Meta Event Actions, and skipping it is the most common reason someone connects Meta correctly and then sees no conversions arrive.
Step 1: define the events
Add the events you want to report. Meta has a set of standard event names — Lead,
Purchase, Schedule, CompleteRegistration and others — and
using a standard name matters: Meta's optimisation understands those specifically, while a custom event
name is stored but treated as far less meaningful for bidding.
For most businesses, two events cover it: Lead when someone becomes a qualified enquiry,
and Purchase when they actually buy.
Step 2: map stages to events
On the mapping screen you get one row per pipeline stage with a dropdown. Pick the event each stage should fire. Leave every other stage on "None" — there is no requirement to map them all, and mapping a stage you do not want reported sends Meta a false signal about what a result is.
From then on, moving a lead into a mapped stage sends the event automatically. Nobody has to remember to do anything per lead.
Map the stage that represents a genuine result, not an early one. Meta's bidding learns from whatever you report and goes looking for more of it. Map "Contacted" and you are training Meta to find people who answer the phone — not people who buy. This single mistake quietly undoes the point of connecting the integration at all.
Send a value with the event
Every event carries a value, and that is what enables value-based bidding: Meta learns that one conversion was worth ₹2,00,000 and another ₹8,000, rather than treating them as identical.
The number sent is the lead's Budget custom field when it holds one, and the event action's own default value when it does not — so set a sensible default on the action even if you fill Budget in most of the time.
For a business with widely varying deal sizes this is the difference between optimising for volume and optimising for revenue. See tracking deal value.
Checking it worked
Move a lead into a mapped stage, then check Marketing → Meta Conversions in the CRM for the upload record. In Meta Events Manager the event can take a while to appear in reporting even after a successful send — that lag is on Meta's side.
If nothing is uploaded at all, the usual causes are an expired access token or a lead Meta has no way
to match. A lead qualifies on either of two keys: a Meta click identifier
(fbclid/fbc/fbp) captured on your landing page, or a Meta lead ID
if it came from an Instant Form — those have no click ID by definition and are matched by lead ID
instead. A lead that arrived organically or was typed in by hand has neither, so it will never produce
an upload. That is expected rather than broken.
How this differs from the Google Ads mapping
The pattern is identical and the two are configured separately, which is deliberate — you will often want different stages reporting to each platform. The mechanics are covered in mapping Google Ads conversion actions, and reading both is worthwhile if you run both channels.