What is signal loss, and why did it grow so much?
Signal loss is when a conversion actually happens but the ad platform never sees it. The cause is not one change; it is several blocking layers stacked on top of each other. Safari's tracking prevention (ITP) restricts third-party and some first-party cookies. iOS App Tracking Transparency (ATT) weakens mobile matching because most users decline consent. Ad blockers stop the pixel from loading at all.
One important correction: Chrome's plan to fully remove third-party cookies was reversed in 2025. So the problem is not 'the death of cookies'; the loss happens mainly at the browser layer, which is exactly why the fix is moving from the browser to the server.
What exactly is server-side tracking?
Server-side tracking sends conversion events straight from your own server (or a server-side tag container) to the platform's API, instead of from the user's browser. The event leaves from a place ad blockers and browser restrictions cannot reach. Meta provides this via the Conversions API (CAPI), Google via enhanced conversions and its conversion API.
- Browser pixel: runs on the user's device and is exposed to blocking and cookie limits.
- Server-side: sends the event from your own infrastructure, largely unaffected by blocking.
- Both together: the most robust setup; the same event travels two paths and is then deduplicated.
Meta Conversions API: raise your event match quality
The value of CAPI depends on how well Meta can match your events to the right person. The score that measures this is Event Match Quality (EMQ, 1-10). The higher it climbs, the more conversions reach the optimization system, and the lower your CPA.
- Hashed email: the single strongest field; on most accounts it moves EMQ from 4-5 to 7-8.
- Hashed phone, name and location: hash identity fields with SHA-256.
- fbc, fbp, IP and user agent: send these in plain text, do not hash them.
- event_id: the shared key that matches pixel and server events.
How much of your data are you really seeing?
Ads Sensor unifies your Meta, Google and GA4 data in one panel and makes the gap between reported and actual visible.
The Google Ads side: enhanced conversions and the server
Google's counterpart is enhanced conversions. It sends hashed first-party data collected at conversion time (email, phone) to Google and recovers part of the loss caused by iOS and Safari. In a more advanced setup, server-side tagging sends events entirely from the server.
- Enhanced conversions: the fastest win; on many accounts it is enabled within hours.
- Server-side tagging: more robust but requires technical setup.
- Consent Mode: fills the gap with modeled conversions when consent is declined.
Pixel and server together: deduplication
The most robust setup runs both at once: the same conversion is sent from the browser and from the server, and the platform uses a shared event_id to recognize them as one event and count it once. Without deduplication, this setup double-counts conversions and performs worse than either method alone.
After setup: trusting the number
Server-side tracking brings the data back, but it does not finish the job. The real question is: can you trust the number you report? Missing tracking looks like a genuine performance drop; freshly installed tracking creates a 'jump' that can distort your comparison with the prior period. Telling these two apart keeps your campaign decisions on solid ground.
This is exactly where Ads Sensor comes in: it unifies your Meta, Google and GA4 data in one panel, catches sudden changes in reported conversions with 24/7 anomaly monitoring, and helps you tell whether it is a performance problem or a tracking change. Join the beta and connect your account to see your cross-platform picture in minutes.
Common mistakes
- Turning on pixel and CAPI without deduplication (double counting).
- Not sending identity fields; EMQ stays low and CPA looks high.
- Sending raw fbclid instead of fbc/fbp, or hashing those.
- Setting up enhanced conversions but skipping Consent Mode; a gap remains when consent is declined.
- Mistaking the 'lift' right after a tracking change for real performance and scaling budget wrongly.