Meta CAPI: doubling the match rate when the cookies died
Browser-side tracking lost signal as cookies and privacy controls tightened. I moved conversion reporting to Meta's Conversions API. Match rate doubled from 3.0 to 6.0 and held there, with no PII sent.
- 2.0×
- 6.0
- None
The problem
As browsers and operating systems restricted third-party cookies and cross-site tracking, browser-side conversion tracking began missing a large share of conversions. For a paid social program, that shows up as a low match rate: the share of conversion events Meta can tie back to a user it recognizes.
Our match rate was 3.0. A low match rate limits how much an ad platform can learn from your conversions, and that limits how well it can optimize delivery.
The approach
Meta's Conversions API (CAPI) reports conversion events from the server instead of relying only on the browser. Server-to-server reporting is less exposed to cookie restrictions and browser privacy controls, which is why it is the standard answer to this problem.
The integration was built with one rule: no PII sent.
The result
Match rate, before: 3.0
Match rate, after: 6.0
Lift: 2.0×, and it held there.
PII sent: none.
This write-up sticks to the documented result. The match rate doubled and stayed there, without sending any PII.
What this project says about how I work
This is the kind of work I want to be doing. It is infrastructure: no flashy UI, no headline announcement, just a measurable result that held and a privacy posture that kept PII out of the pipeline.
That's the bar for what shows up on this site. Every project here has a real result behind it.
Want to talk about CAPI, server-side tracking, or just compare notes on your own match rate horror stories? You can reach me here or grab a slot on my Friday office hours.