In plain English
Instead of relying on the visitor's browser, events are sent from your server. That means blockers and browser privacy features do not remove them.
Run alongside the pixel it recovers a meaningful share of lost measurement. Both must send an event ID so Meta can deduplicate, or conversions get counted twice.
What to know
Server to server
Not dependent on the browser.
Recovers lost events
Which improves optimisation, not just reporting.
Runs alongside the pixel
Both, not either.
Needs deduplication
Matching event IDs prevent double counting.
Why it matters
Better event coverage improves delivery as well as reporting, because the system optimises on what it can see. This is one of the few technical changes that improves results directly.
Common mistakes
×Sending events without deduplication IDs.
×Server-side only, discarding browser signals.
×Poor match quality from missing customer parameters.
×Assuming it is only a reporting improvement.
FAQs
Do I need this as well as the pixel?
Yes. They work together and Meta deduplicates matched events.
What does it improve?
Both measurement accuracy and delivery optimisation.
WRITTEN BY TARIQ SALLAM
Marketing Consultant. Entrepreneur. Content Creator.
I'm a marketing consultant, entrepreneur and content creator. I help businesses grow through practical marketing, websites, SEO, content and AI.
More About Tariq →