For the same customer action,
event from Facebook Pixel must match
event_name from Server-Side API. If we find a match between events sent within 48 hours of each other, we only consider the first one. If a server and browser event arrive at approximately the same time (within 5 minutes of each other), we favor the browser event.
Learn about Deduplicate Pixel and Server-Side Events.
A Unix timestamp in seconds indicating when the actual event occurred.
A map that includes additional business data about the event. See Custom Data Parameters.
The browser URL where the event happened.
A flag that indicates we should not use this event for ads delivery optimization. If set to
true, we only use the event for attribution.
This ID can be any unique string chosen by the advertiser.
event_id is used to deduplicate events sent by both Facebook Pixel and Server-Side API.
event_name is also used in the deduplication process.
For deduplication, the
eventID from Facebook pixel must match the
event_id in the corresponding Server-Side API event. Learn about Deduplicate Pixel and Server-Side Events.