Glossary · Tracking and event quality

Pixel

A piece of JavaScript on your website that reports visitor actions back to Meta.

Definition

It loads with the page, watches for the events you have defined, and sends them to Meta. Everything Meta knows about what happens on your site, it knows because of this.

Why it matters for HVAC

An ad with real link clicks and zero conversions is more often a broken pixel than a bad ad. The most expensive analysis mistake available in this vertical is rebuilding creative that was never the problem, and it happens because nobody checked the tag first.

The common causes are mundane: the pixel sits behind a cookie banner and never fires until someone accepts, the wrong pixel ID is installed after a site rebuild, or the thank-you page the conversion fires on was quietly replaced.

How it is measured

Load the page and watch for the request to Meta’s tracking endpoint. Events Manager shows events arriving in near real time, and the browser extension Meta publishes shows which pixel ID fired and what it sent. If nothing fires, nothing downstream means anything.

A worked example

A contractor’s campaign shows 340 link clicks and 2 conversions for the month, and the agency proposes new creative. The site added a consent banner three weeks earlier and the pixel now waits for acceptance that most visitors never give. The creative was fine and the month was spent on the wrong repair.

These figures are invented to show the arithmetic. They describe no real business.

What it is not

It is not the Conversions API, and running one does not make the other unnecessary. The pixel reports from the browser and loses events there; the API reports from your server and does not.

Where this is demonstrated

The Tracking and the Conversions API pillar scores every listed agency on what they document here, and gives you the questions that tell you which one you are being sold.

Related terms