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

What the Meta Lead ID Is and Why It Decides Your Match Rate

The Meta lead ID is the 15 to 17 digit number Meta gives every Instant Form lead. Here is where it comes from, why it is the strongest identifier you can send with CRM events, how it gets lost, and what to send when you do not have one.

Written by Qualimize Team

Founder, Qualimize

Published
November 16, 2026
Last updated
November 16, 2026
Reading time
9 min read
META CAPI & TRACKINGInstant Form leadCRM status changelead_idlead_idlead_idMetaMatched to the ad

Table of contents

  1. 01 The short answer
  2. 02 Where the lead ID comes from
  3. 03 Why it beats email and phone
  4. 04 What match rate means in practice
  5. 05 How lead IDs get lost
  6. 06 How to protect it
  7. 07 What to send when there is no lead ID
  8. 08 A quick audit you can run today

Full article

The short answer

The Meta lead ID is the unique number Meta assigns to every Instant Form submission, described in Meta's documentation as a 15 to 17 digit number from the leadgen_id field. When your CRM sends it back with a stage event, Meta can tie that event to the exact form submission and ad, without guessing from email or phone. That is why it decides how many of your CRM events Meta can actually use.

In this guide, match rate means the share of your CRM events that Meta can connect to a person who saw your ad. Meta reports related measures in Events Manager; the principle is the same: an event Meta cannot match teaches it nothing.

Where the lead ID comes from

When someone submits an Instant Form, Meta creates a lead record and gives it an ID. If your CRM receives leads through Meta's webhook, the notification carries that ID as leadgen_id, and the CRM uses it to fetch the lead's answers. A direct integration therefore has the ID from the first second.

The ID is not hashed and never needs to be. Meta's customer information parameters page lists lead_id as an integer that should not be hashed, unlike email and phone. It identifies a form submission, not a person, so it is safe to store alongside the lead.

Leads that do not come from Instant Forms have no lead ID. A website form, a walk-in, a phone enquiry or an IndiaMART lead will not have one, and that is expected.

One person can create several lead IDs. If the same person fills in your Instant Form twice, for example once from a property ad in March and again from a different ad in May, Meta creates two submissions with two IDs. Your CRM may flag them as duplicates and merge them into one lead, which is good for your sales team, but it means you need a rule for which ID the merged lead keeps. The usual choice is the submission that your team actually worked, because that is the one whose outcome you want Meta to learn from.

Why it beats email and phone

Without the lead ID, Meta matches CRM events by comparing hashed email, phone and name against its own records. That works, but only when the person typed the same details Meta holds. Instant Forms pre-fill from the person's account, yet people edit them, use a work email, or give a family member's phone number.

The lead ID removes that uncertainty. It points to the specific submission Meta already holds, which is tied to the specific ad, ad set and campaign. Meta's Conversion Leads payload specification puts lead_id in its highest priority group of customer information parameters, alongside the click ID and hashed email.

Send both anyway. The lead ID gives the precise link to the ad; hashed email and phone help Meta understand the person, and they are the fallback for any lead whose ID is missing.

What match rate means in practice

Every CRM event you send falls into one of two groups: events Meta can tie to a person who interacted with your ads, and events it cannot. Only the first group helps. An unmatched SubmitApplication is invisible to optimisation, however accurate your sales team was.

Example: a Pune broker sends 100 SubmitApplication events in a month. If 95 of them carry a valid lead ID, Meta has a direct route to the original form submission for nearly all of them. If the lead IDs were lost in a spreadsheet import and only hashed phone numbers are sent, the share Meta can match depends on how many people gave the same number Meta holds, and some will not have. The broker's sales work is identical in both cases; the value Meta gets from it is not.

This is why the lead ID matters more than almost any other setting in a CRM integration for Instant Form leads. It is free, it is already in the webhook, and keeping it costs nothing except not losing it.

How lead IDs get lost

Lead IDs are rarely missing at the start. They are lost on the way, usually by people, not code.

The most common route is a spreadsheet. Excel stores numbers with 15 significant digits of precision, so a 16 or 17 digit lead ID typed or imported as a number is silently rounded, and the last digits become zeros. The ID still looks plausible, but it no longer exists. Meta's documentation says that if you send a lead_id, it must be valid or the event is rejected, so a rounded ID is worse than none.

Other routes are copying leads by hand into a CRM that has no lead ID field, merging duplicate leads and keeping the record without the ID, and re-creating leads from a call log.

Switching CRMs is a quieter risk. When a business moves from one tool to another, lead IDs are often left out of the export because nobody recognises the column as important. Every Instant Form lead migrated without its ID becomes a lead whose future stage changes Meta can only match by email and phone. Include the ID column in any migration, as text.

  • Importing leads through Excel with the ID as a number
  • Manual entry into a CRM with no lead ID field
  • Duplicate merges that drop the ID
  • Leads re-created from WhatsApp or call logs

How to protect it

Use a direct integration so leads arrive with the ID already attached, and store it in a text field, not a number field. If you must use a CSV, format the ID column as text before importing, and spot-check a few IDs against Meta's lead record.

When merging duplicates, keep the lead ID from the Instant Form submission on the surviving record. When a lead fills in two forms, there will be two IDs; keep the one tied to the submission your team actually worked.

Then check it end to end: send one test event with a recent lead's ID and a test event code, and confirm it appears in the Test Events tab without an error. Doing that once tells you more than any amount of reading.

What to send when there is no lead ID

For website leads, the strongest alternative is the click ID. When someone clicks your ad, Meta adds an fbclid parameter to the landing page URL. Your website form can capture it and pass it to the CRM, which sends it as fbc (Meta's format is fb.1. followed by a timestamp and the fbclid, which is what the _fbc cookie holds). Meta's customer information page says fbc and fbp must not be hashed.

Alongside that, send everything you have, hashed and normalised: email lowercased and trimmed, phone with the 91 country code, first and last name, and city, state, zip and country when you have them. Meta's customer information page sets out the normalisation rules for each.

For offline leads with no ad click at all, there is nothing to tie back to an ad. Do not send fake identifiers to force a match.

For ad-level reporting on website leads, also add URL parameters to your ads so the campaign, ad set and ad IDs arrive with the lead. Those parameters do not help Meta match events, but they let your CRM show which ad each website lead came from, the same way Instant Form leads are tagged.

A quick audit you can run today

You do not need a developer to find out whether your lead IDs are healthy. Open your CRM, filter to Instant Form leads from the last 30 days, and look at the lead ID field.

Check four things. Every Instant Form lead should have one; a blank means it was lost on the way in. Each should be 15 to 17 digits; anything shorter was probably truncated. None should end in a long run of zeros; that is the sign of spreadsheet rounding. And no two different leads should share the same ID; duplicates usually mean a bad import.

If more than a handful fail, fix the intake route before worrying about anything else in your Conversions API setup. Better event names or extra parameters will not help events that cannot be matched to the lead they describe.

  • Blank lead ID on an Instant Form lead: lost at intake
  • Fewer than 15 digits: truncated
  • Ends in several zeros: rounded by a spreadsheet
  • Same ID on two leads: bad import or merge

Comparison tables

Identifiers you can send with a CRM event

IdentifierFieldHashed?Instant Form leadsWebsite leads
Meta lead IDlead_idNoYes, from leadgen_idNo
Click IDfbcNoNot usuallyYes, if fbclid is captured
Browser IDfbpNoNoYes, if the Pixel cookie is read
EmailemYes, SHA-256UsuallyUsually
PhonephYes, SHA-256UsuallyUsually
Name, city, state, zip, countryfn, ln, ct, st, zp, countryYes, SHA-256If on the formIf on the form

Ways a lead ID breaks, and the fix

ProblemWhat happensFix
Imported as a number in ExcelDigits after the 15th become zerosFormat the column as text before import
CRM has no lead ID fieldID never storedUse a direct integration or add a text field
Duplicate merge drops itWorked record has no IDKeep the Instant Form ID on the surviving record
Typo in a hand-copied IDEvent rejected as invalidNever type lead IDs by hand

FAQ

What is the Meta lead ID?

It is the unique ID Meta assigns to each Instant Form submission, a 15 to 17 digit number delivered as leadgen_id. CRMs store it so they can send it back with later stage events through the Conversions API.

Should I hash the lead_id before sending it to Meta?

No. Meta's customer information parameters page says lead_id is an integer and should not be hashed. Email, phone and name should be hashed with SHA-256 after normalising.

Why are my Conversions API events with lead_id being rejected?

Meta rejects events with an invalid lead_id. The most common cause is an ID rounded by a spreadsheet, which keeps only 15 significant digits, or a typo from copying by hand. Check the stored ID against the original lead.

Do website leads have a Meta lead ID?

No. Only Instant Form submissions have a lead ID. For website leads, capture the fbclid from the landing page URL and send it as fbc, along with hashed email and phone.

Does sending the lead ID improve Event Match Quality?

Sending more valid customer information generally helps Meta match events. The lead ID is the most direct link for Instant Form leads, and Meta's Conversion Leads specification puts it in the highest priority group of identifiers. Keep sending hashed email and phone as well.

Where does Qualimize fit?

Qualimize receives Instant Form leads through Meta's webhook, so the Meta lead ID is stored on the lead from the moment it arrives. Every Conversions API event it sends on a status change includes that lead ID plus hashed email, phone and name where the lead has them. For website leads posted to its webhook, it captures UTM parameters and fbclid.

Key takeaways

  • The Meta lead ID is a 15 to 17 digit number from leadgen_id, unique to each Instant Form submission.
  • It is never hashed, and it gives Meta the most direct link from a CRM event to the ad.
  • An invalid lead_id gets the event rejected, so a rounded ID is worse than none.
  • Excel rounds 16 and 17 digit numbers; store and import lead IDs as text.
  • Website leads have no lead ID: send fbc from the captured fbclid plus hashed email and phone.

Further reading

  • Meta: Customer information parameters
  • Meta: Conversion Leads payload specification
  • Meta: Conversions API for CRM integration

Keep reading

  • ProductHow Qualimize sends lead stages to Meta (CAPI)
  • GuideEvent Match Quality (EMQ): Complete Guide
  • GuideHow to Send CRM Lead Stages to Meta, Step by Step
  • GuideMeta's Conversion Leads Goal Explained: Requirements and When to Switch
  • ProductPricing: one plan, every feature
  • CompareCompare CRMs for Meta lead ads
Discuss Qualimize

Keep reading

Related articles

Meta CAPI & Tracking

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

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.

Read next
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

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