Meta CAPI Deduplication Not Working: Event ID and Event Name Problems Explained
Deduplication is set up but events are still being counted twice. The mechanism exists but is failing, which means the identifiers that link the browser and server events are not matching. This article focuses on why deduplication itself fails, separate from the broader concept of duplicate counting.
Table of Contents
- 01.Deduplication depends on matching identifiers
- 02.What to check first
- 03.Event name mismatch
- 04.Event ID mismatch or absence
- 05.Timing and duplicate server requests
- 06.How to test it
Deduplication depends on matching identifiers
Deduplication works only when the browser event and the server event share the same event name and the same event ID for the same action. If those identifiers do not match, Meta cannot tell the two events apart from two separate conversions. Failed deduplication is almost always an identifier mismatch, not a setting you can toggle.
What to check first
- Confirm the event name is identical on the browser and server events.
- Confirm an event ID is present on both events.
- Confirm the event ID is the same value on both for the same action.
- Check how the event ID is generated and whether it can match across paths.
- Check the timing of both events, since large gaps can affect deduplication.
Event name mismatch
The event name must match exactly. A browser event named Purchase and a server event named Purchases will not deduplicate, because the names differ. Case and spelling matter. Confirm the event name string is identical on both paths, including any custom event names you use.
Event ID mismatch or absence
The event ID is the key that links the two events. If it is missing on one path, different on each path or generated independently so it can never match, deduplication fails. The event ID should be a stable identifier for the action, like an order ID, generated once and passed to both the browser event and the server event. If the browser generates its own ID and the server generates its own, they will never match.
This is distinct from the broader duplicate counting problem. The guide on Meta Pixel and CAPI duplicate conversions explains the concept. Here the focus is the specific failure of the identifiers. The guide on Meta CAPI event ID missing goes deeper into event ID generation and persistence.
Timing and duplicate server requests
Deduplication expects the browser and server events for the same action to arrive close together. A large gap between the two can affect whether Meta treats them as the same event. Also watch for duplicate server requests, where a retry or a webhook firing twice sends the same server event more than once. Each duplicate server request without a unique event ID can be counted separately.
How to test it
- 1.Fire one action that triggers both the browser and server events.
- 2.Capture the event name and event ID on the browser event.
- 3.Capture the event name and event ID on the server event.
- 4.Confirm both names match exactly and both event IDs match.
- 5.Check Events Manager to confirm the two events are deduplicated into one.
Frequently Asked Questions
Why is deduplication not working even though I set it up?
The event name or event ID is not matching between the browser and server events. Deduplication depends on both identifiers being identical for the same action. Check the exact strings and the event ID generation.
Can a timing gap break deduplication?
A large gap between the browser and server events for the same action can affect whether Meta treats them as the same event. The two events should arrive close together, and the event ID should be the same on both.
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 Pixel and CAPI Counting the Same Conversion Twice: How Deduplication Works
Pixel and CAPI sending the same event is expected. The goal is deduplication through a matching event name and event ID, not removing one of the delivery paths.
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.