Your ads are paying
for bad data.
The pixel misses a large share of real purchases, so ad platforms optimise on a partial picture. Server-side events and better match quality fix the input, and cheaper conversions follow.
Seen by the pixel · example6 in 10
Every ad platform works the same way underneath. It watches who buys, finds more people like them, and bids harder on those people. The whole loop depends on one input: knowing who bought.
For most stores that input comes from a browser pixel, a script that fires when the thank-you page loads. It was a reasonable design in 2015. It is a weak one now.
Why the pixel misses
Ad blockers strip it. Safari and Firefox cap the cookies it depends on. Consent banners stop it firing until someone clicks accept, and plenty never do. Slow thank-you pages lose it to people who close the tab after paying.
None of this is rare. On many stores we look at, the pixel reports noticeably fewer purchases than the store's own order table. Every missing sale is a lesson the algorithm never gets.
What a conversions API does
A conversions API lets your server tell the platform about the purchase directly. Meta calls it the Conversions API, TikTok the Events API, Google enhanced conversions. The idea is the same. The order is real, it sits in your database, and no browser setting can block it.
You keep the pixel too. Both send the same event with the same ID, and the platform keeps one. That is deduplication, and getting it wrong is the most common way a server setup makes reporting worse instead of better.
Blocked by browsers and extensions
Waits on consent and page load
Cookie and IP only
Match quality around 4
Sent from the order, not the page
Consent-aware, still respected
Hashed email, phone, click ID
Match quality around 8
Match quality is the real lever
Sending the event is half the job. The platform still has to tie it to a person who saw an ad. It does that with identifiers: a hashed email, a hashed phone number, the click ID from the ad URL, the IP and browser. Meta scores this as event match quality, and other platforms have their own version.
A purchase with only a cookie might score 4 out of 10. The same purchase with a hashed email, phone and click ID can score 8 or more. Higher match quality means more of your sales count as training data, and the algorithm finds cheaper buyers faster. That is where the lower CPA comes from. Not from a new creative, not from a new audience, from better input.
“You cannot out-bid bad data. You can only fix what the algorithm is learning from.”
Four signals you need it
- 01Ads Manager reports clearly fewer purchases than your store does for the same week.
- 02Match quality sits below 6, or you have never looked at it.
- 03You run a consent banner and your reported conversions dropped the week it went live.
- 04A server integration is already live, and purchases now count twice.
What we set up in a week
We audit what fires today and compare it with your orders. We stand up a server-side Tag Manager container on your own cloud account, so the data stays yours. Then we connect each platform you use, add hashed identifiers, set event IDs for deduplication, and wire consent so a refusal is still a refusal.
Moving tags off the page also takes weight off it. Third-party scripts are one of the most common causes of slow pages, as web.dev explains, so the store usually gets a little faster too. See how Integrations fits with the other practices, or the full Pixel & CAPI offer.
When to skip it
If you spend under about $2k a month on ads, the platforms do not have enough volume to learn much faster, and the pixel alone is fine. If you sell mostly offline, fix how offline sales are recorded first. And if nobody on your team looks at ad reporting, better data will not change a decision. We will tell you if you are one of these, before you pay anything.
The references behind this post.
Keep reading.
02Plugins are debt
Read more →
03