Meta Pixel Not Tracking Leads? How to Find the Fault

01 • first, the terms

What should the Meta pixel be sending when someone becomes a lead?

The Meta pixel is code on your website that sends visitor actions, called events, to Meta. Events go into a dataset (Meta's name for the container that holds your pixel and server events, identified by the pixel ID). When someone submits an enquiry form, the usual event is Lead, one of Meta's standard events.

If Lead never arrives, or arrives twice, everything built on it is wrong: your cost per lead, your reports and what Meta optimises for.

02 • common faults

Why is my Lead event not showing in Events Manager?

1. 1No thank-you page. Many forms show a 'thanks' message on the same page. If the Lead event was set to fire on a thank-you page URL that never loads, it never fires.
2. 2Event on the wrong trigger. Lead fires on a button click instead of a successful submit, so it records attempts (including failed ones) or nothing at all.
3. 3Form inside an iframe. Forms embedded from another service (booking tools, form builders) run on that service's page. Your pixel cannot see inside it unless the tool has its own Meta integration.
4. 4Wrong pixel ID. An old pixel, a different client's pixel, or two pixels on the same page.
5. 5Consent banner blocking it. In the UK and EU, the pixel should wait for consent. If nobody accepts, no event fires, which is correct, but expected numbers drop.
6. 6Ad blockers and browser privacy. Some visitors block tracking scripts entirely.
7. 7Single-page app routing. On sites that change pages without a full reload, PageView and Lead may not fire unless they are triggered in code.
8. 8Event sent before the pixel loads. The code calls the event before the base pixel has finished loading.

03 • test it properly

How do I test whether my pixel tracks leads?

1. 1Open Meta Events Manager, choose your dataset and open Test Events.
2. 2Enter your website address and open it from the Test Events window, or use the test code for server events.
3. 3Submit a real test lead through your form.
4. 4Watch Test Events: you should see Lead arrive once. Note whether it came from the browser, the server, or both.
5. 5Check the Overview tab later. Meta's Conversions API guide says new events should appear within about 20 minutes.

04 • the backup

Will the Conversions API catch leads the pixel misses?

Often, yes. Meta's best-practices page says the Conversions API can capture events the pixel misses, such as those lost to network issues or page loading errors, and recommends using both together. Your server knows a form was submitted even when the visitor's browser blocked the pixel.

Running both means the same lead can be reported twice, so each event needs a shared event ID that Meta uses to count it once. See Meta event deduplication and Meta pixel vs Conversions API.

05 • what good looks like

What does a correctly set up Lead event look like?

A healthy setup has the same shape on almost any website, whatever platform it uses. Use this as a checklist against your own.

If you use a website builder or form tool, look for a built-in Meta integration before adding custom code. If it supports the Conversions API with event IDs, that is usually the simplest route. If it only supports the pixel, the server side can come from your CRM instead.

06 • key terms

Which terms do I need to know?

Short, plain definitions of the terms used on this page.

07 • the bigger picture

Is tracking the Lead event enough?

Fixing Lead is step one. The bigger win is telling Meta what happened after the lead: qualified, booked, won. That happens in your CRM, not on your website. See send purchase events to Meta from your CRM.