Your pixel is installed and your data is still wrong

Two different checks that get confused

"Is the pixel installed" and "are events arriving" are separate questions. The first is answered by viewing source. The second is answered by looking at what the platform actually received, and only the second one matters.

A pixel can be present on every page and still send nothing useful: fired before the element exists, blocked by a consent gate that never resolves, scoped to the wrong business, or firing a page view where a purchase was expected.

This is the single most common cause of an account that mysteriously underperforms. The campaign is optimising toward a signal that is incomplete or absent, and the optimiser has no way to tell you that.

Install it before you need it

The strongest recommendation from the webinar was to install the pixel immediately — even if you are not ready to launch a campaign. Conversion data is the foundation everything else sits on, and it is only useful once it has been accumulating.

If you already run a Meta pixel with meaningful history, keep it. Install alongside rather than instead. There is no benefit to throwing away conversion history you already paid to build.

Where events actually come from

Browser events cover page views and funnel steps on pages you control. They are the easiest to install and the easiest to lose — ad blockers, consent gates and single-page navigation all interfere.

Server-side conversions are sent from your backend rather than the browser. They survive ad blockers, and they are the only reliable route when the transaction completes somewhere the browser never reaches. If your checkout lives on another platform, this is not optional.

The two are complementary, not alternatives. A serious setup sends both and deduplicates them with a shared event identifier.

How to verify properly

Complete a real transaction end to end, then look for that specific event in the platform — not a test fire, a real one. Confirm it arrived against the correct business, with the values you expect.

Then check the boring things: that purchase events are not also firing on page load, that a refresh does not create a second conversion, and that the event names match what your campaigns optimise toward.

Do this before spend, not after. Diagnosing a tracking fault retroactively means you also cannot trust the performance data you gathered while it was broken.