Meta CAPI Event ID Missing or Incorrect: Why Deduplication Can Fail
When the event ID is missing, inconsistent or incorrectly generated, deduplication cannot work. The event ID is the link between the browser event and the server event. Without a matching ID, Meta cannot tell they represent the same action. This article focuses specifically on the event ID itself.
Table of Contents
- 01.Why the event ID matters
- 02.What to check first
- 03.Missing on one path
- 04.Inconsistent generation
- 05.ID persistence across paths
- 06.GTM variables and server payloads
- 07.How to test it
Why the event ID matters
The event ID is the identifier that tells Meta a browser event and a server event are the same business action. For a purchase, it is usually the order ID. Without a matching event ID on both events, deduplication fails and the same action can be counted twice. The event ID is narrower than the broader deduplication problem, it is the specific identifier that makes deduplication possible.
What to check first
- Confirm an event ID is present on the browser event.
- Confirm an event ID is present on the server event.
- Confirm both use the same value for the same action.
- Check how the event ID is generated and whether it can match across paths.
- Confirm the event ID persists from the browser to the server for the same action.
Missing on one path
If the event ID is present on the browser event but missing on the server event, or vice versa, the two cannot be linked. Check both events for the event ID field. A common cause is the server event being built without access to the identifier the browser event used, so the server generates its own or sends none.
Inconsistent generation
If the browser generates an event ID and the server generates a different one, they will never match even though both are present. The event ID must be a stable identifier for the action, generated once and shared between both paths. For a purchase, the order ID is the natural choice because it is the same on the browser confirmation page and in the server order data.
ID persistence across paths
The event ID has to persist from the browser to the server for the same action. If the browser event uses a random ID that the server never sees, the server cannot send the same ID. Use an identifier that both paths can access, like the order ID, rather than a value generated only in the browser and not passed to the server.
GTM variables and server payloads
If you use GTM, the event ID is often a variable on the browser tag. Confirm the server event, whether sent through server-side GTM or a direct integration, uses the same value. A mismatch between the GTM variable and the server payload is a common cause of failed deduplication. The guide on Meta CAPI deduplication not working covers the broader deduplication mechanism.
How to test it
- 1.Fire one action and capture the event ID on the browser event.
- 2.Capture the event ID on the server event.
- 3.Confirm both IDs are present.
- 4.Confirm both IDs are the same value for the same action.
- 5.Check Events Manager to confirm the two events are deduplicated.
Frequently Asked Questions
What should I use as the event ID?
Use a stable identifier for the action that both the browser and server can access. For a purchase, the order ID is the natural choice because it is the same on the confirmation page and in the server order data.
Why is my event ID present on both events but deduplication still fails?
The two IDs are probably different values. The browser and server must use the same event ID for the same action. If each path generates its own ID, they will never match even though both are present.
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 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 Sending Duplicate Purchase Events: Common Causes and Fixes
Duplicate CAPI Purchase events come from repeated server requests or multiple integrations. Use a unique event ID like the order ID and make sure only one path sends Purchase per order.