Why “installed” is not enough
The pixel snippet can sit on every page and still send nothing: a trigger that never fires, a JavaScript error earlier on the page, a deleted Pixel ID, a security policy that blocks the request. Nothing on the site looks different. You find out when conversions in Ads Manager drop to zero.
So the only proof that counts is a request watched leaving the browser, and that is the only thing TagZ counts as working.
What the check looks at
- The install. The
fbevents.jsloader and thefbq('init')call, with the Pixel ID it was given. - What was sent. Every request to
facebook.com/tr, read event by event: PageView, ViewContent, AddToCart, Purchase and the rest, with value, currency, content IDs and event ID. - Whether it is sane. A Pixel ID that does not look valid, a Purchase without the value and currency Meta requires, an amount that is not a plain number, and the same PageView sent more than once for one page view.
- The cookie banner. If a banner is holding the pixel back, the scan presses its accept button and watches again. A pixel still waiting behind a banner it could not answer is reported as not verified, never as broken.
If your events carry an event ID, the report says deduplication with the Conversions API is prepared. It does not claim a server event is actually being sent: that happens on your server, out of sight.
What a scan cannot see
A scan opens one page, once, as an anonymous visitor. It moves the mouse and scrolls, but never clicks a buy button or submits a form, so purchase, add-to-cart and lead events are listed as not tested rather than guessed. It sees requests leave the browser, not whether the platform accepted them, and it cannot see server-to-server events.
What the report says
This is the finding TagZ writes when it sees this fault, word for word.
Meta Pixel is installed but sent nothing
Ads on this platform are running without the signal they optimise on. Audiences stop growing and conversions stop being attributed, while the site looks perfectly normal.
Suggested fix
Open the page with the browser's network panel filtered to the platform's endpoint and confirm nothing is sent. Then check, in order: the tag's trigger (does it fire on this page?), a JavaScript error earlier on the page stopping the snippet, and whether that Pixel ID still exists in the platform account.
A scan is one look. Tags break later.
A theme update, a plugin, a new cookie banner, someone tidying up an old account: tracking rarely breaks loudly. TagZ monitoring runs this same check every six hours in a real browser and emails you when a tag that was working stops sending, after a second scan has confirmed it.
$7.99 a month for one website, billed yearly ($95.88 a year), or $2.63 a site per month on the Agency plan for 25 sites, billed yearly. See all plans.