Meta Pixel

What the Meta Pixel does, how pixel IDs work, and how the audit detects Meta's advertising tracker on any public site.

What the Meta Pixel is

The Meta Pixel (formerly the Facebook Pixel) is Meta's advertising tracker: a JavaScript snippet that reports page views and conversion events (purchases, sign-ups, add-to-cart) back to Meta so advertisers can measure ad performance and build retargeting audiences across Facebook and Instagram. It's one of the most common third-party trackers on commercial sites.

Pixel IDs

Each pixel has a numeric ID (e.g. 1234567890123456) embedded in the fbevents.js snippet or fbq('init', '<id>') call. The audit extracts every pixel ID found. Multiple IDs on one page typically mean multiple ad accounts are being fed — common after agency changes where the old agency's pixel was never removed.

Detection

• Static scan: matches the fbevents.js / connect.facebook.net snippet patterns and extracts the pixel ID. Directly installed pixels are reliably caught.
• Via tag manager: many sites deploy the pixel through GTM or another container, in which case the static scan sees only the container. Browser-render mode executes the page and catches the pixel as it fires.

Why it shows up in audits

The pixel is the canonical example of a tracker with privacy implications: it sends browsing behavior to an ad platform, which is exactly the kind of third-party data flow privacy reviews and consent audits care about. Finding a Meta Pixel on pages where it doesn't belong (login flows, account pages, health or children's content) is a routine audit finding worth flagging to the site owner.

What the report tells you

Beacon rows show the pixel ID and load method — direct script tag, or via tag manager. Because the pixel often fires conversion events from JavaScript rather than page load, render mode gives the more complete picture of where it's active.