Conversions API
Sending conversion events to Meta from your server rather than from the homeowner’s browser.
The Meta pixel is a piece of JavaScript that runs in the visitor’s browser and reports back what they did. That works right up until it does not: an ad blocker stops it, a cookie banner holds it until someone clicks accept, a browser trims the identifiers it carries, or the page navigates away before it fires. Every one of those is an event Meta never hears about.
The Conversions API sends the same events from your own server instead. Nothing in the visitor’s browser can suppress them, and the event can carry more identifying information than a browser event is allowed to.
The Conversions API sends the same events from your own server instead. Nothing in the visitor’s browser can suppress them, and the event can carry more identifying information than a browser event is allowed to.
Why it matters for HVAC
Home service leads are phone-led, and phone numbers are one of the strongest identifiers you can attach to a server event. A contractor’s lead flow carries exactly the data that makes server-side matching work well. The inverse is also true: an HVAC account running browser events alone is throwing away its best signal, and then judging the creative on what is left.
The practical effect is not on reporting accuracy, which is what most agencies sell it as. It is on delivery. Meta buys impressions for the people most likely to produce the event you told it about, and if half those events never arrive, it is optimising against a half-blind picture of who your customers are.
How it is measured
Three things tell you it is genuinely running rather than merely installed. Events Manager shows an event count broken down by source, so you can see server events arriving alongside browser events rather than instead of them. Event match quality is scored out of ten per event type. And the deduplication rate tells you whether the two sources are being correctly recognised as the same action, which needs a shared event ID on both sides.
A worked example
A contractor runs instant-form campaigns and sees 90 leads in Ads Manager for the month. Their CRM has 140 new enquiries from Meta over the same period, matched by the phone numbers people typed in. That gap of 50 is not a reporting curiosity: those 50 are conversions Meta never learned from, so it spent the month looking for people who resemble the 90 rather than the 140. Turning on server-side events closes the gap at the source.
These figures are invented to show the shape of the problem. They describe no real business.
What it is not
It is not offline conversion upload, though the two travel down the same pipe. This one sends events that happen on your website. That one sends outcomes that happen in your CRM days later. An agency can do the first and not the second, and on this ledger that difference is worth points.
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.