Event deduplication
Browser and server events, matched by Meta, counted once
Free trial. No card, no tag manager.
Every event gets a shared ID, without setup
The browser pixel and the Conversions API both report the same conversion. PixelFlow attaches one event ID to both copies, so Meta recognises the pair and counts it once. There is no manual event_id to generate or pass around.
Lead
Processed
Browser
Lead
Processed
Browser
Lead
Deduplicated
Server
Purchase
Processed
Browser
Purchase
Processed
Browser
Purchase
Deduplicated
Server
Matched by Meta
Meta uses the event ID and event name to pair the browser and server copies.
Visible in the log
Each conversion shows its two copies and which one Meta kept.
Accurate reporting
Purchases and revenue in Ads Manager reflect real sales, not two of every sale.
Attribution
Last 30 days
Source
Visitors
Revenue
Direct
831
$549.45
Organic
1,919
$172.09
511
$318.20
147
$76.10
Totals
3,408
$1,115.84
Double counting breaks optimisation
If Meta sees two purchases for every real one, it optimises towards the wrong signals and your reported ROAS is wrong. Deduplication keeps the training data honest.
Stop repeats before they start
Deduplication handles the browser and server pair. Blocking rules stop the same conversion firing again on a refresh or a return visit. Together your counts are exact.
Purchase · blocking rules
3 active
Block if already fired this session
Block without a Facebook click ID
Block repeats within 30 minutes
Block if same referrer
Connected
2 active
Stripe
Purchase, Subscribe, StartTrial
Calendly
Schedule
Platforms
Webflow
Framer
Squarespace
WordPress
Shopify
+ 9 more
Stripe and Calendly events are deduplicated too
A purchase that fires on your thank-you page and again from the Stripe webhook is matched, so an off-site payment is still one sale.
FAQ
Everything you need to know about deduplication.
Do I need to configure deduplication?
No. It is automatic on every event, on every plan.
How does Meta know two events are the same?
They carry the same event ID and event name. Meta pairs them within its deduplication window.
Why do I see two events in Events Manager?
Both copies are received. One is marked as deduplicated and not counted.
What if only the server event arrives?
Then it is counted once, as it should be. Server-side delivery is there for exactly that case.
Does it work with the Programmatic API?
Yes. Pass your own event ID with the request and it will be matched against the browser event.
Does it deduplicate across pixels?
Each pixel receives its own pair and deduplicates independently.
Smarter, server-side tracking
Start sending accurate conversions today - no tag manager, no code, no developer required.
Compatible with
