When Meta and a CRM disagree on lead numbers, first test whether leads are still arriving, then compare one fixed week lead by lead, because most gaps come from a broken connection, duplicates, date differences or tracking that counts the wrong step.
The monthly report says 120 leads. The client's CRM says 95. Now the client wants to know which number is real, and the meeting is about trust instead of results.
A small gap is normal, because the two systems count different things. A large or sudden gap usually has a specific cause, and you can find it. Those numbers are illustrative, but the check below works at any size.
Check first: are leads still arriving?
This is the urgent one, so rule it out first. For Instant Forms, Meta's Lead Ads Testing Tool sends a test lead through a live form and shows whether it reached the CRM. If it did not, leads are piling up inside Meta with nobody calling them. Download them now. Meta keeps them for 90 days.
The usual reasons
- A broken connection: a CRM update, an expired login or a changed form can stop the sync with no warning.
- A form that was never connected: the integration covers the old form, and the new form was never added.
- Duplicates: Meta counts each form submission, while many CRMs merge entries with the same phone number.
- Date differences: Ads Manager can credit a result to the day the ad was shown, while a CRM records the day the lead arrived.
- Time zones: the ad account and the CRM may close the day at different times.
- Other sources in the CRM: if it also holds calls and walk-ins, its number can be higher than Meta's.
If the leads come from your website
Website leads add two more causes. The pixel may fire on the wrong step, so a Next button or a page reload counts as a lead. And Meta counts leads it can attribute to an ad within its attribution window, including some people who saw the ad and came back later, while the CRM only knows that a lead arrived.
To test the first, submit the form once yourself with the Meta Pixel Helper browser extension running, and confirm the Lead event fires once, on the final step.
Watch for a change in the gap, not the gap itself. A steady 10% is arithmetic. A jump is an event.
How to find the cause in 20 minutes
- Pick one complete week that ended at least a few days ago.
- Download that week's leads from Meta as a CSV.
- Export the same week from the CRM.
- Match them by phone number.
- Look at the leads on one side only. They will usually share a form, a date or a phone number, and that points to the cause.
What to do afterwards
Compare the two counts every week for each client, not once a quarter. A broken sync found on day two costs a few calls. Found on day thirty, it costs a month of leads and a difficult meeting. Tell the client which number you report, what it counts and why it will never match the CRM exactly, before they ask.