Meta Pixel and CAPI Counting the Same Conversion Twice: How Deduplication Works
When the Pixel and CAPI both send the same conversion, Meta can count it twice unless deduplication works. This is not a bug, it is the expected result of sending the same business event through two delivery paths. The concept you need is deduplication, and it depends on matching identifiers on both events.
Table of Contents
- 01.Two paths for one event
- 02.What to check first
- 03.Event name and event ID
- 04.Two delivery paths is not two conversions
- 05.When deduplication fails
- 06.How to test it
Two paths for one event
The Pixel sends the event from the browser. CAPI sends the same event from the server. Both describe one business action, like one purchase. Without deduplication, Meta receives two events for one action and can count both. The goal is not to remove one path, it is to tell Meta they represent the same event.
| Element | Purpose |
|---|---|
| Browser event | One delivery path from the Pixel |
| Server event | Second delivery path from CAPI |
| Event name | Must match on both events |
| Event ID | Shared identifier that links the two |
| Deduplication | Meta merges the two into one business event |
What to check first
- Confirm both the Pixel and CAPI are sending the same event name.
- Confirm both send the same event ID for the same action.
- Check whether the event ID is generated and shared correctly.
- Confirm the event timing on both paths is close.
- Check Events Manager for whether events are being deduplicated.
Event name and event ID
Deduplication relies on two identifiers matching between the browser and server events. The event name must be the same on both. The event ID is a unique identifier for the specific action, like an order ID for a purchase. When both the event name and the event ID match, Meta can recognize the two events as one business action and count it once. If either identifier differs, deduplication fails and the event can be counted twice.
Two delivery paths is not two conversions
It is easy to assume that two events arriving means two conversions happened. It does not. Two events from the Pixel and CAPI for the same purchase are two delivery paths for one conversion. The question is whether deduplication is working, not whether you should remove one path. Both paths have value, because the server event can capture data the browser event misses.
When deduplication fails
If the event ID is missing on one path, different on each path or generated in a way that cannot match, Meta cannot deduplicate and may count both events. This is a deduplication problem, not a reason to disable CAPI. The guide on Meta CAPI deduplication not working covers the specific causes in detail, and the guide on Meta CAPI event ID missing covers the event ID specifically.
How to test it
- 1.Complete a test action that fires both the Pixel and CAPI.
- 2.Check that both events carry the same event name.
- 3.Confirm both events carry the same event ID.
- 4.Check Events Manager to see whether the two events are deduplicated.
- 5.If both are counted separately, the event ID is the first thing to check.
Frequently Asked Questions
Should I stop sending the Pixel or CAPI to avoid duplicates?
No. Both paths have value. The fix is deduplication using a matching event name and event ID on both events, not removing one delivery path. The server event often captures data the browser event misses.
How does Meta know two events are the same conversion?
Through the event name and event ID. When both match between the browser and server events, Meta can recognize them as one business action and count it once. If either differs, deduplication can fail.
Need help applying this to your business?
PPC, Conversion Tracking, CRM and Automation Specialist. Helping businesses generate qualified leads with Google Ads, accurate tracking and automated follow-up.
Related Guides
Meta CAPI Deduplication Not Working: Event ID and Event Name Problems Explained
Failed deduplication is an identifier mismatch. Confirm the event name is identical and the event ID is the same value on both paths for the same action before looking anywhere else.
Meta CAPI Event ID Missing or Incorrect: Why Deduplication Can Fail
The event ID is the link between the browser and server events. Use a stable identifier like the order ID, generate it once and confirm the same value is present on both paths.
Meta Browser Events and Server Events Do Not Match: How to Audit the Difference
Browser and server counts will not always be identical because the paths face different restrictions. Find unexpected differences, confirm event names and deduplication, then investigate.