Leads, CRMs and follow-up

How do I troubleshoot lead routing issues from Meta lead ads?

Lead routing breaks in four places: the lead never left Meta, the identifiers are missing, the CRM mapped a field to nothing, or leads access is gone.

Published

Lead routing issues from Meta lead ads come from one of four places: the lead never left Meta, it arrived without the identifiers your routing rules use, your CRM mapped a field to nothing, or the token that reads the leads lost its permission. Work through them in that order, because each fault hides the next one.

Where lead routing breaks

What you seeMost likely faultFirst check
Nothing arrives in the CRMthe lead never left Meta, or the connection is not assigned leads accesswhether the page admin who connected the CRM still has leads access
Leads arrive, unassigneda routing rule reads a field that is emptythe ad ID and form ID on the record
Leads arrive in the right place, but CPL per ad is blankthe ad ID was dropped during mappingthe field list of the integration
Leads look right in the CRM, pipeline stages never reach Metathe lead ID is not stored, so stage events cannot matchwhether the integration keeps Meta’s lead ID

1. Confirm the lead left Meta

A native CRM integration should deliver new leads automatically, and Meta describes that delivery as real time. A webhook is near real time: Meta says its pings can arrive with a delay of up to a few minutes, which is not a fault.

To prove the path works end to end, use Meta’s Lead Ads Testing Tool, which creates a test lead for a form and shows whether your endpoint received it, payload included. Two limits matter: you get one test lead per form at a time, and the tool does not work in developer mode. Its leads are organic and carry no ad ID, so use it to test delivery, not to test the ad attribution.

The other check is a count. Meta keeps Instant Form leads downloadable for 90 days from submission, and Results keeps counting leads you can no longer download. If a lead is older than that window and nobody exported it, the fault is not routing.

2. Compare the three counts before you change anything

Take one form and one month, then compare what Ads Manager says with what a download holds and what your CRM holds.

Where you lookWhat it countsWhy it differs
Results column in Ads Managersubmissions that came from the adsthe baseline
Business Suite downloadthe same leads plus organic and test entriesorganic leads are downloadable there but not in Ads Manager
Leads Center exportyour current filter, contact fields onlya file holds up to 10,000 leads, and stage is a column, not a log
Your CRMwhatever the integration mappedfields that were never mapped are missing

Organic leads exist only when the form’s sharing setting is Open, which is not the default. Neither organic nor test leads count in Results. A gap of a handful of leads is usually those two, not a broken route. A gap of hundreds is a delivery problem.

3. Check the identifiers on every lead

Routing rules are only as good as the fields they read. Whatever route you use, two IDs belong on every lead record: Meta’s lead ID, so the CRM can send stages back later, and the ad ID, so you can compute cost per lead for the ad that produced it.

FieldComes fromWhy routing needs it
Lead IDdownloads, webhooks, the API, integrations that map itthe match key for stage events
Ad, ad set and campaign IDsdownloads and the API with advertiser access; the webhook carries the ad IDassigns the lead to the right offer and client
Form IDdownloads, webhooks, the APIone form can serve many ads
Tracking parametersset per form in Settingsfixed labels such as a client name or offer code
is_organic and platformdownloadsseparates paid from organic, Facebook from Instagram

Ad fields come out blank for organic leads, for ad preview submissions, and for anyone without advertiser privileges on the ad account, so a rule that routes on ad ID silently fails for those rows.

One more trap: not every native integration stores Meta’s lead ID. HubSpot Lead Sync does not, Zoho’s social integration does not, and Microsoft Dynamics 365 has no leads integration at all. Salesforce Lead Capture does, in a Lead ID field you map yourself. The comparison of routes is in Facebook lead ads CRM integration.

4. Check the CRM side, starting with permissions

Connecting a CRM takes one pass through Meta Business Suite, and the permission it needs is easy to lose later. Only admins of the Facebook Page who hold leads access can connect a CRM, and if someone with full control of the business portfolio has customized leads access, the CRM has to be assigned there before any lead arrives.

An integration installed from the CRM’s own website cannot be edited or disconnected in Business Suite, so when it stops, the CRM side is the only place to look. Lead the diagnosis with all the questions on leads, CRMs and follow-up if the fault is a field rather than a connection.

5. Check what happens after the lead lands

A lead that reaches the CRM and goes nowhere is a routing rule problem, not a delivery problem. Three things cause most of it: the rule reads an empty field, two rules overlap and cancel each other, or the owner is a user who no longer exists.

If you send pipeline stages back to Meta, the CRM needs an event per stage change, starting with the raw lead. A batch holds up to 1,000 events and one error discards the whole batch, so keep batches small and retry. event_time must come after the lead was created and no more than 7 days before you send it. Meta’s own example: 100 leads that become 70 marketing qualified leads, 30 opportunities and 15 sales make 215 events, not 15.

Keep a safety net that catches what the route misses

Webhooks are the fastest route and the easiest to break silently. A daily bulk read on the form or the ad, with a filter on time_created, compares the IDs Meta holds with the IDs you already stored, so a missed lead turns up the next morning instead of expiring in 90 days.

The rate limit is generous: 200 × 24 × the number of leads the Page created in the past 90 days, per 24 hours. Meta suggests bulk read for a few fetches a day and webhooks for anything more frequent, which is the pairing worth running.

A short checklist before you blame the integration

  • Send one test lead and confirm the payload arrives with its IDs.
  • Open one real lead in the CRM and check the lead ID, ad ID and form ID.
  • Confirm the Page admin who owns the connection still has leads access.
  • Compare the Results column with the CRM count and explain the gap by organic and test leads.
  • Confirm the CRM stores Meta’s lead ID before you rely on stage events.
  • Keep one manual export as a backup, as Meta itself recommends while an integration is being fixed.

Most of these faults are invisible from Ads Manager, because buried in an average that looks normal. When the ad ID survives the trip, the same lead that routes a client’s call also feeds cost per lead per ad, per creative and per landing page, which is what DropCPL computes from the spend Meta reports. Routing rules and form settings belong together: the lead ads best practices are the ones that make the route worth fixing.

Questions on this topic

All questions on this topic →

FAQ

Which check should I run first when leads stop arriving?+

The identifiers, not the automation. Open one recent lead in your CRM and look for Meta's lead ID, the ad ID and the form ID. A lead that arrived without them will route to the wrong owner or to nobody, and no rule change fixes that until the mapping is corrected.

Why do the Results column and my CRM disagree by a few leads?+

Because they count different things. Results counts submissions that came from the ad. A download or a CRM can also hold organic leads, which exist only when the form's sharing setting is Open, and test leads you submitted yourself, and neither of those counts in Results.

Can I test the route before I spend money on ads?+

Yes. Meta's Lead Ads Testing Tool creates a test lead for a form and shows whether your endpoint received it, payload included. You get one test lead per form at a time, delete it to make another, and the tool does not work in developer mode.

What breaks a working route months after launch?+

Usually access. Webhooks and API reads run on a token whose owner needs leads access on the Page, so the route dies the day that person leaves the team or loses their role on the ad account. Give the token to a shared system user, not to an individual.

Ready to find out what
converts, for real?

Free to start.

Start free →