Most accounts assume the pixel works because the base code is on the site. But the base code only fires a page view. The events that actually feed bidding and audiences, Lead, Purchase, a form submit, often never fire, and nobody notices until performance is already suffering.
The 60-second Test Events check
Open Events Manager, go to Test Events, enter your site URL, and use the site as a real visitor would: load a page, submit a form, complete a purchase. Each action should appear in the live feed within seconds, mapped to the right event. If Lead does not show when you submit the form, your pixel is installed but not firing where it counts.
Firing is not the finish line
Once events fire, the next question is how well Meta can match them to people. That is event match quality, improved by sending more clean parameters and by adding the Conversions API alongside the pixel with deduplication. Weak matching under-reports conversions and weakens delivery even when the pixel technically fires.
Why it matters
Bidding optimizes to the events it can see. A pixel that misses your real conversions trains Meta on the wrong signal, and no budget or creative fixes a measurement hole. Verify first; optimize second. Server-side tracking is what keeps it resilient as browser tracking erodes.
Common questions
How do I check if my Meta pixel is working?
Open Events Manager, use the Test Events tool, enter your URL, and perform actions like submitting a form or purchasing. Each should appear in the live feed mapped to the right event within seconds. If a key event does not show, the pixel is installed but not firing there.
Why does an installed pixel still miss conversions?
The base pixel only fires a page view; specific events like Lead or Purchase must be configured to fire on the right actions. Weak event match quality also under-reports, which is why the Conversions API and clean parameters matter.