Meta Ads
Why purchase event IDs matter for Meta CAPI
When the same purchase is sent to Meta from both the browser Pixel and CAPI, Meta needs a way to know those are two representations of one business event. The event ID is a key part of that deduplication process.
What goes wrong without a match
Suppose Order #500 triggers:
- one browser Purchase;
- one server Purchase.
If Meta cannot associate them, reporting may treat the events incorrectly. A properly coordinated implementation provides matching event information according to Meta's current deduplication requirements.
Consistency is more important than complexity
The browser and server copies of the same event need the same intended identifier. Generating unrelated IDs on each side defeats deduplication.
Test in Events Manager
Review current browser/server event details and diagnostics. Do not assume that seeing two data sources means two conversions; Meta can receive both and count one when deduplication is working. See how to check whether Meta CAPI is working.
Event IDs do not repair everything
Wrong purchase value, currency, duplicated server calls or multiple separate CAPI integrations can still create inaccurate data.
Think of event ID as one component of an accurate event architecture.
Inspect the CAPI implementation
If Meta shows browser and server purchases and you cannot tell whether they are deduplicated correctly, contact us. We can inspect the CAPI implementation.