Meta Pixel

Why does the Meta Pixel miss sales?

Because it runs where the shopper can stop it. An ad blocker refuses the script, Safari and Firefox restrict what it can store, and a shopper who declines tracking removes it. None of that is a fault in the pixel; it is the environment the pixel was designed for changing underneath it.

Should you remove the Meta Pixel?

No, and Meta does not suggest it. The Meta Pixel still sees browsing that never reaches the shop's server, such as the products someone looked at before leaving without buying. The server connection covers what the browser loses; it does not cover what only the browser saw.

What does the Meta Pixel have to do with the Conversions API?

They are the two halves of one report. The Meta Pixel reports from the browser, the Conversions API reports from the server, and Meta matches the pair on a shared event identifier so a sale seen by both is counted once. Run together they cover each other's blind spots.

Is the Meta Pixel the same thing as a dataset?

Nearly. Meta renamed the pixel a dataset inside Events Manager, and a dataset groups a site's web, app and offline events rather than only the browser ones. The pixel itself is not retired and the identifier does not change: an existing pixel ID becomes the dataset ID.

The rename is worth knowing mainly because instructions written before it, which is most instructions, still say pixel while the screen now says dataset.