QualimizeQualimize
FeaturesHow it worksQualified leadsMeta CAPIComparePricingResourcesContact
LoginBook 1:1 Demo
QualimizeQualimize

The CRM for teams running Meta Ads. Capture every lead, record what your sales team finds, and send those outcomes back to Meta.

+91 94997 11011WhatsApp us

Address

Sama Savli Road, Vadodara,
Gujarat, 390008

Product

  • Features
  • Pricing
  • Product tour
  • How it works
  • Qualified leads
  • Meta CAPI
  • For agencies
  • Partner program

Industries

  • All industries
  • Real estate CRM
  • Travel CRM
  • Education CRM
  • Visa consultancy CRM
  • Healthcare CRM
  • Solar CRM
  • Marketing agencies

Compare

  • All comparisons
  • vs Zoho CRM
  • vs LeadSquared
  • vs TeleCRM
  • vs Privyr
  • vs GoHighLevel
  • vs HubSpot
  • vs Salesgem
  • vs FlowZo
  • LeadSquared alternatives
  • GoHighLevel alternatives
  • Privyr alternatives

Company

  • About
  • Contact
  • What's new
  • Pricing
  • Login

Legal

  • Security & data
  • Privacy policy
  • Terms of service
QualimizeQualimize

The CRM for teams running Meta Ads. Capture every lead, record what your sales team finds, and send those outcomes back to Meta.

+91 94997 11011WhatsApp us

Address

Sama Savli Road, Vadodara,
Gujarat, 390008

Product

  • Features
  • Pricing
  • Product tour
  • How it works
  • Qualified leads
  • Meta CAPI
  • For agencies
  • Partner program

Industries

  • All industries
  • Real estate CRM
  • Travel CRM
  • Education CRM
  • Visa consultancy CRM
  • Healthcare CRM
  • Solar CRM
  • Marketing agencies

Compare

  • All comparisons
  • vs Zoho CRM
  • vs LeadSquared
  • vs TeleCRM
  • vs Privyr
  • vs GoHighLevel
  • vs HubSpot
  • vs Salesgem
  • vs FlowZo
  • LeadSquared alternatives
  • GoHighLevel alternatives
  • Privyr alternatives

Company

  • About
  • Contact
  • What's new
  • Pricing
  • Login

Legal

  • Security & data
  • Privacy policy
  • Terms of service

© 2026 Qualimize. All rights reserved.

Better signals in. Better customers out.

Back to blog
Meta CAPI & Tracking

How to Send CRM Lead Stages to Meta, Step by Step

A step-by-step guide to sending CRM lead stages to Meta through the Conversions API: choosing stages, mapping them to events, building the payload with the Meta lead ID, testing, and going live.

Written by Qualimize Team

Founder, Qualimize

Published
November 16, 2026
Last updated
November 16, 2026
Reading time
11 min read
META CAPI & TRACKING01New02Contacted03Interested04Qualified05ConvertedContactLeadSubmitApplicationPurchaseSent to Meta via CAPIMeta

Table of contents

  1. 01 The short answer
  2. 02 Before you start: what you need
  3. 03 Step 1: Choose the stages that matter
  4. 04 Step 2: Map each stage to a Meta event
  5. 05 Step 3: Build the event payload
  6. 06 Step 4: Test before going live
  7. 07 Step 5: Go live and keep it healthy
  8. 08 Mistakes that stop stage events from counting

Full article

The short answer

To send CRM lead stages to Meta, you pick the three or four stages that show real progress, map each one to a Conversions API event, and send that event from your server the moment a rep changes the lead's status, with the Meta lead ID and hashed contact details attached. Meta then matches each event to the original ad and can learn which leads turn into customers. You test it with a test event code in Events Manager before switching it on for real.

That is the whole idea. The rest of this guide walks through each step in the order you would actually do it, with the exact fields Meta expects and the mistakes that most often stop events from counting.

Nothing here needs a developer if your CRM already has a Conversions API connection built in. If it does not, the same steps tell a developer exactly what to build.

Before you start: what you need

You need four things in place before a single event can be sent. Missing any one of them is the most common reason a setup stalls halfway.

First, a dataset (the Pixel ID you see in Events Manager) that the events will be sent to, and a Conversions API access token generated for it in Events Manager settings. Treat that token like a password: it lets anyone who holds it send events into your ad account's data.

Second, the Meta lead ID stored on every Instant Form lead in your CRM. Meta describes it as a 15 to 17 digit number that comes from the leadgen_id field when the lead is delivered. If your leads arrive through Meta's webhook or a direct integration, it is usually saved automatically. If you copy leads by hand from a CSV file, it is often lost.

Third, a clear list of statuses your team actually uses, with written rules for when a rep moves a lead into each one. If one rep marks every lead who picks up the phone as Qualified and another waits for a site visit, Meta receives noise.

  • Dataset (Pixel) ID and a Conversions API access token
  • Meta lead ID saved on every Instant Form lead
  • Hashed email and phone where you have them, with phone numbers including the 91 country code
  • Written definitions for each status, agreed with the sales team

Step 1: Choose the stages that matter

Do not send every status in your CRM. Statuses like Call Back Later or Wrong Number describe your team's workload, not the lead's intent. Sending them teaches Meta nothing useful and makes Events Manager harder to read.

Pick the stages that mark a real step towards a sale. For most Indian lead businesses that means four: the lead was reached, the lead showed genuine interest, the lead is ready to buy, and the lead paid. A Pune property broker might call these Contacted, Interested, Site Visit Done and Booked. A Jaipur coaching centre might call them Contacted, Counselled, Demo Class Attended and Admission.

The names can be anything. What matters is that each stage is reached by a meaningful share of leads and that reps apply it the same way every time. A stage that only 1 in 500 leads ever reaches gives Meta very little to learn from.

Write each definition as one sentence a new rep could apply on day one, and pin it where the team works. For example: Interested means the lead confirmed a budget and a time frame on a call. Ten minutes spent on these definitions saves weeks of confusing data later, because every event Meta receives is only as reliable as the rep who triggered it.

Step 2: Map each stage to a Meta event

Meta's standard events give each stage a name the ad system already understands. For lead generation the four that fit best are Contact, Lead, SubmitApplication and Purchase. Meta's own definitions are: Contact is when a person initiates contact with your business by phone, SMS, email or chat; Lead is when a sign-up is completed; SubmitApplication is when a person applies for a product, service or program; and Purchase is when a purchase is made.

A common mapping is Contacted to Contact, Interested to Lead, Ready to Buy to SubmitApplication and Converted to Purchase. Purchase is the only one of the four where Meta requires a value and a currency, so the event that marks a paid customer should carry the deal amount in rupees.

If you plan to use Meta's Conversion Leads performance goal, the rules are different: Meta's payload specification for that integration treats event_name as a free-form field for your own CRM stage names. We cover that in a separate guide, linked at the end.

Step 3: Build the event payload

Each status change becomes one server event. Meta requires an event name, an event time as a Unix timestamp in seconds, and an action source. For lead stage events sent from a CRM, Meta's Conversion Leads specification requires action_source set to system_generated, and it is the usual choice for any CRM-sent stage event.

Then add the customer information that lets Meta match the event to a person. The Meta lead ID goes in user_data as lead_id, unhashed, because it is an integer that Meta generated. Email, phone, first name and last name go in as SHA-256 hashes after normalising them: email trimmed and lowercased, phone with symbols and leading zeros removed and the country code added. A Mumbai number written 098200 12345 becomes 919820012345 before hashing.

Finally, add an event_id. Meta describes it as any unique string you choose, and it is what lets Meta discard a duplicate if the same event is sent twice. A good pattern is the lead's ID plus the stage name, so a retry of the same status change carries the same ID and does not count twice.

  • event_name: the mapped event, for example SubmitApplication
  • event_time: when the status changed, in Unix seconds
  • action_source: system_generated for CRM events
  • user_data.lead_id: the Meta lead ID, not hashed
  • user_data.em / ph / fn / ln: SHA-256 hashes of normalised values
  • event_id: stable per lead and stage
  • custom_data.value and currency: on Purchase only, for example 45000 and INR

Step 4: Test before going live

Events Manager has a Test Events tab that gives you a test event code. Send a few events with that code attached, using real lead IDs from recent leads, and they appear in the Test Events tab within a short time. Meta's CRM implementation guide specifically says to include the test_event_code and a valid lead_id when testing.

Check three things in the test view: the event name is spelled and capitalised exactly as Meta's standard event (Purchase, not purchase), the customer information fields you sent are listed, and there are no errors flagged on the event.

Then remove the test code from your live setup. Meta's Conversions API documentation says events sent with a test_event_code are not dropped: they still flow into Events Manager and are used for targeting and ads measurement. The code is only for checking that events arrive correctly, and Meta says to remove it from production payloads. Because test events are real events, test with real lead IDs and real stages rather than made-up purchases with large values.

Step 5: Go live and keep it healthy

Send events as close to real time as you can. Meta's CRM implementation guide says calls should ideally be made in real time, with hourly or daily batches as a fallback, and at least once a day. Events sent within minutes of a status change are the easiest for Meta to use.

Respect the 7-day window. Meta's server event documentation says event_time can be up to 7 days before you send the event, and if any event in a request is older than that, the entire request is rejected and no events in it are processed. This matters if your integration goes down for a week and you try to resend a backlog: send in small batches so one stale event does not sink the rest.

Watch Events Manager weekly for the first month. You should see each event appear, the volume should roughly match the number of status changes your team made, and the event detail should show the customer information you are sending. Qualimize, for example, sends these events automatically when a rep changes a status and shows every send, with its result, in Settings, so you can compare the two.

Mistakes that stop stage events from counting

Most broken setups fail for a small number of reasons, and almost all of them are visible in Events Manager if you know where to look.

The biggest is missing lead IDs. Without the lead ID, Meta has to match on hashed email and phone alone, and people sometimes edit the pre-filled email or phone on an Instant Form, so it no longer matches their Facebook account. The second is phone numbers hashed without the 91 country code, which produces a hash that matches nobody. The third is reps updating statuses in bulk at the end of the month: Meta learns about the outcomes weeks late, and any event back-dated to the real day of the outcome falls outside the 7-day window.

  • Lead ID not stored, or stored as a rounded number in a spreadsheet
  • Phone hashed without the country code, or email hashed with capital letters
  • Access token or dataset ID copied wrongly, so requests fail
  • Event names that do not match Meta's standard names exactly
  • Status updates entered days late, in bulk
  • Every CRM status sent, including ones that mean nothing about intent

Comparison tables

Example mapping of CRM stages to Meta events

CRM stage (example)Meta eventWhat it tells MetaValue attached?
ContactedContactThe lead was real and reachableNo
Interested / Pre-qualifiedLeadThe lead showed genuine interestOptional
Qualified / Site visit doneSubmitApplicationThe lead is ready to buyNo
Converted / BookedPurchaseThe lead paidYes: value and currency required

Fields in a CRM stage event

FieldWhat goes in itHashed?
event_nameContact, Lead, SubmitApplication or PurchaseNo
event_timeUnix seconds when the status changed (within 7 days)No
action_sourcesystem_generatedNo
user_data.lead_idMeta lead ID from leadgen_idNo
user_data.em, ph, fn, lnNormalised email, phone with 91, namesYes, SHA-256
event_idStable ID per lead and stageNo
custom_data.value, currencyDeal amount and INR (Purchase)No

FAQ

How do I send lead status from my CRM to Facebook?

Use Meta's Conversions API. Each time a lead's status changes to a stage that matters, your CRM sends a server event with the mapped event name, the time of the change, action_source set to system_generated, the Meta lead ID and hashed email and phone. Test with a test event code in Events Manager first, then switch it on.

Which CRM stages should I send to Meta?

Send the three or four stages that mark real progress towards a sale, such as contacted, genuinely interested, ready to buy and paid. Skip workload statuses like call back later or not reachable. Each stage you send should be reached by a meaningful share of leads and applied consistently by every rep.

Do I need a developer to send CRM events to Meta?

Not if your CRM has a Conversions API connection built in; you only map statuses to events and paste in your dataset ID and access token. If it does not, a developer can build it from Meta's Conversions API documentation, or you can use a third-party connector.

How late can I send a CRM event to Meta?

Meta accepts an event_time up to 7 days before the event is sent. If any event in a request is older than that, Meta rejects the whole request. Send status changes as they happen, ideally in real time and at least once a day.

Why are my CRM events not showing in Events Manager?

The usual causes are an invalid lead ID (Meta rejects the event), an event_time more than 7 days old (Meta rejects the whole request), or a wrong access token or dataset ID. Check the error message in the API response, then send one event with a test event code and look at the Test Events tab to confirm the fix.

Where does Qualimize fit?

Qualimize is a CRM for Meta lead ads that has this built in. A status in your workspace can be attached to Contact, Lead, SubmitApplication or Purchase, and the event is sent server-side when a rep changes the status, with the Meta lead ID, hashed contact details and a stable event ID. Failed sends retry automatically and every send is visible in Settings. If you already use a CRM you like, the steps in this guide work with any tool that can call the Conversions API.

Key takeaways

  • Send three or four stages that mark real progress, not every status in your CRM.
  • Map them to Contact, Lead, SubmitApplication and Purchase; only Purchase requires value and currency.
  • Attach the Meta lead ID unhashed, and hash email and phone after normalising them, with 91 on Indian numbers.
  • Use a stable event_id per lead and stage so retries do not double count.
  • Events older than 7 days get the whole request rejected, so send status changes as they happen.

Further reading

  • Meta: Implementing the CRM integration
  • Meta: Conversion Leads payload specification
  • Meta: Conversions API server event parameters
  • Meta: Customer information parameters
  • Meta Pixel reference: standard events

Keep reading

  • ProductHow Qualimize sends lead stages to Meta (CAPI)
  • GuideWhich Meta Events to Send for Lead Gen: Contact, Lead, SubmitApplication, Purchase
  • GuideWhat the Meta Lead ID Is and Why It Decides Your Match Rate
  • GuideHow to Test Your Meta CAPI Setup
  • ProductPricing: one plan, every feature
  • CompareCompare CRMs for Meta lead ads
Discuss Qualimize

Keep reading

Related articles

Meta CAPI & Tracking

Which Meta Events to Send for Lead Gen: Contact, Lead, SubmitApplication, Purchase

Qualimize uses exactly this ladder. Each workspace status can be attached to one of four signals: Contact, Lead, SubmitApplication or Purchase, with defaults of Contacted, Pre-Qualified, Qualified and Converted. Purchase carries the deal value and currency when a rep records it. If you need a different event, such as Schedule, you would need another tool or a custom integration.

Read next
Meta CAPI & Tracking

Meta's Conversion Leads Goal Explained: Requirements and When to Switch

Qualimize sends CRM stage events to Meta through the Conversions API, with the Meta lead ID, within minutes of a status change. It does not send two CRM fields that Meta's Conversion Leads specification lists, so Qualimize does not claim Conversion Leads support. What it does give you is standard Contact, Lead, SubmitApplication and Purchase feedback, plus cost per qualified lead by campaign. If Conversion Leads is a hard requirement for you today, use a tool that states support for it.

Read next
Meta CAPI & Tracking

How to Send Purchase Value from Your CRM to Meta

In Qualimize, the status your workspace attaches to the Converted tier sends a Purchase event when a rep moves a lead into it. It carries the deal value and currency when the rep has entered the deal value on the lead (entered by hand), and a nominal value of 1 otherwise, never 0. Qualimize does not pull payment amounts from billing or accounting tools, so the value is only as good as what your team records.

Read next

Build a cleaner Meta Ads sales workflow

Qualimize helps you capture leads, qualify them faster, and connect CRM outcomes back to ad performance.

Book 1:1 Demo
20-minute walkthroughMeta CAPI built-inNo lock-in
See Plans & Pricing