Signal quality is how complete, accurate and timely the conversion data you send to Meta is. Every purchase, lead or sign-up reported back to Meta is a signal that tells its delivery system who responded to an ad. The more of those signals arrive, the more accurately they are matched to real people and the faster they turn up, the better the system can find more people like them.
How signal quality works
Signals reach Meta through the Meta Pixel in the browser, the Conversions API (CAPI) from your server, app events, offline uploads and Meta’s own lead forms. Quality depends on several things:
- Coverage: how many real conversions are reported at all.
- Matching: whether each event carries enough customer information, such as a hashed email address or phone number, for Meta to link it to an account. Meta scores this as Event Match Quality.
- Accuracy: whether each conversion is counted once. When the pixel and CAPI both send the same purchase, a shared event ID lets Meta remove the duplicate.
- Freshness: whether events arrive within minutes rather than days.
- Value: whether purchases carry the right order value and currency, GBP for a UK shop.
Signal loss is the opposite: conversions that happen but never reach Meta, or reach it without enough detail to match. The usual causes are browser tracking restrictions, ad blockers, Apple’s App Tracking Transparency prompt, broken tags after a site update, and visitors declining cookies.
Why it matters
Meta’s delivery is automated, and automation learns only from what it is told. If half your sales go unreported, the system optimises on a partial picture, costs per result look higher than they are, and campaigns may struggle to leave the learning phase. Good signals do not make bad ads work, but poor signals can make good ads look as if they fail.
In the UK there is a legal dimension. Under PECR and UK GDPR, the pixel and similar tags need consent before they run, so some consent-driven data loss is unavoidable and correct. Improving signal quality means sending better data about the people who did agree, not finding ways round those who did not. Server-side sending through CAPI is still subject to the same consent choices. A consent banner that loads tags only after someone agrees, and passes that choice to every tag, is the starting point for honest signals.
Common mistakes
- Running the pixel without CAPI. Browser-only tracking misses conversions that ad blockers and browser restrictions stop.
- Double counting. Pixel and CAPI both sending purchases without a shared event ID inflates results.
- Sending no customer details. Events with no email or phone are hard to match, which lowers Event Match Quality.
- Ignoring consent. Firing tags before consent, or sending server events for people who refused, creates legal risk.
- Never checking after site changes. A new checkout or theme often breaks tracking quietly.
How to act on it
Open Events Manager and review each key event: its volume, its match quality score and any diagnostics warnings. Compare a week of reported purchases or leads with your own order or CRM records to estimate how much is missing. Then add CAPI with deduplication, pass hashed customer details for people who have consented, check that order values and currency are right, and retest after every site release. Setting up and checking tracking so the delivery system gets clean, lawful signals is part of my Facebook ads management service.