A diagnosis guide
Meta ads leads not tracking?
The ads are probably fine.
Your CRM keeps filling with leads. Sales is talking to real people who saw the ads. And Ads Manager insists the campaigns produce almost nothing, while cost per lead climbs toward "shut it all down." I have seen the extreme version of this: an ad account reporting exactly 1 tracked lead when the real number was 355. This page covers the technical causes that actually produce that gap, and how the fix looked.
Take the symptom seriously. It costs more than it looks.
When Ads Manager undercounts your leads, three bad things happen at once. You make budget decisions on fiction: campaigns that quietly work get paused, and the "cost per lead" you optimize against is a made-up number. The algorithm optimizes blind: Meta's delivery system learns from the conversion events it receives, so missing events mean it cannot find more people like your actual buyers. And trust erodes: once the dashboard and the CRM disagree, every reporting conversation turns into an argument about whose numbers are real.
The instinct is to blame creative, audiences, or the platform. In setups like this, the honest first question is different: is the measurement broken? It usually is, in one of a small number of specific, findable places.
The four causes I actually find
1. Custom-conversion mapping is wrong. Ads Manager counts what your custom conversions tell it to count. If a custom conversion is bound to the wrong event, filtered by a URL rule that no longer matches your funnel, or, in multi-account setups, mapped against the wrong ad account, the leads exist but are never attributed. This is the least visible cause and, in my experience, the most brutal one, because everything else looks healthy: pixel fires, events arrive, and the dashboard still shows nothing.
2. Pixel-only tracking, no Conversions API. The browser pixel is one delivery path, and it is the fragile one: ad blockers, Safari and Firefox tracking prevention, and consent banners all eat events before Meta ever sees them. A server-side Conversions API integration sends the same events from your backend, deduplicated against the pixel by event ID. Without it, a real share of your conversions simply never reaches Meta, and lead campaigns are hit hardest because lead audiences skew privacy-conscious in exactly the browsers that block the most.
3. Lead webhooks that go nowhere. Leads captured on your own landing pages reach the CRM through form handlers and webhooks. If no corresponding Lead event is sent back to Meta at that moment, the CRM fills up while Ads Manager starves. The reverse failure exists too: platform-side lead forms delivering into a webhook nobody monitors, so leads silently pile up without follow-up. Both directions need to be wired and watched.
4. Form events fire at the wrong moment, or not at all. Classic versions: the Lead event fires on page load instead of on successful submission, so every visitor "converts." Or the thank-you page URL changed and the conversion rule still points at the old one, so nobody converts. Or the form is an embedded third-party widget inside an iframe the pixel cannot see into. The fix is always the same principle: fire the event on the confirmed submission, from a place you control.
A documented case: 1 tracked lead, 355 real ones
I build and operate the client operations platform for a German video-production and performance-marketing agency. Inside that platform, one client ad account reported exactly 1 tracked lead. On paper the funnel was dead, and the reasonable conclusion would have been to stop spending.
The cause was the first item on the list above: per-account custom-conversion mapping. The events existed; they were attributed against the wrong mapping. After I corrected the mapping, the same account showed 355 leads. That is the difference between "ads are dead" and a working funnel, on identical underlying performance. The fix was live in production the following day. Speed here is not a stunt; my workflow is AI-native, with agents doing implementation while I own architecture, review, and verification, and a corrected mapping is a small, verifiable change once the diagnosis is done.
This fix was one piece of a much larger system: a multi-tenant platform with ads dashboards, lead webhooks with reconciliation, Conversions-API forwarding, and a first-party tracking script. The full case study is here.
What a clean lead-tracking setup contains
Verified conversion mapping: every custom conversion checked against the account, event, and URL rules it is supposed to represent, and re-checked whenever the funnel changes. Pixel plus Conversions API: browser and server sending the same events, deduplicated by event ID, so blocked browsers stop costing you attribution. Lead webhooks with reconciliation: every lead lands in the CRM and produces its event back to Meta, and a scheduled job compares the two sides so drift gets caught instead of discovered. Events on confirmed submission: fired from code you control, at the moment the lead actually exists.
The last piece is a habit, not a tool: compare CRM lead counts against Ads Manager on a schedule. The gap between those two numbers is your tracking health metric. If nobody owns that comparison, you will find out about the next breakage the way most teams do, months late and after the budget meeting.
Common questions, answered straight
Why does my CRM show leads but Ads Manager shows almost none?
Because Ads Manager only counts events it actually receives and can attribute. Your leads are real; the signal path back to Meta is broken somewhere. The usual suspects: a custom conversion mapped to the wrong event or the wrong account, a pixel-only setup losing events to browsers and consent tools, or a form that never fires a Lead event on submission. Trace the event path end to end before you doubt the campaigns.
Do I need the Conversions API if I already have the pixel?
For lead generation, in practice yes. The browser pixel alone loses events to ad blockers, tracking prevention, and consent choices. Sending the same events server-side through the Conversions API, deduplicated by event ID, restores much of that signal. It also lets you send events the browser never sees at all, like a lead being qualified in your CRM.
Can broken tracking really make me kill profitable campaigns?
Yes, and that is the expensive part. Ads Manager numbers drive your budget decisions and feed the optimization algorithm. In the account I describe on this page, reported leads went from 1 to 355 once the custom-conversion mapping was corrected. Before the fix, every rational read of the dashboard said to switch the ads off. The ads were fine.
How fast can something like this be fixed?
Diagnosis is most of the work: tracing where events originate, where they are supposed to land, and where they disappear. Once the cause is clear, the change itself is often small. In the case above, the corrected mapping was live in production the day after diagnosis. I orchestrate AI agents for implementation while owning architecture, review, and verification personally, which is why that turnaround is possible without cutting corners. Not every account is a one-day fix; a tangle of old pixels and duplicate events can take longer to map.
Not sure where your leads are leaking?
Free systems teardown: I look at your setup, name your 3 biggest automation and tracking leaks, and estimate what each one costs you monthly. If your attribution is fine and the problem really is the creative, the teardown will say so. In your inbox within 72 hours.
Get your free systems teardown