For the same customer action,
event from the browser event match
event_name from the server event. 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. The specified time may be earlier than the time you send the event to Facebook. This is to enable batch processing and server performance optimization. You must send this date in GMT time zone.
event_time can be up to 7 days before you send an event to Facebook. If any
data is greater than 7 days in the past, we return an error for the entire request and process no events.
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 deduplication.
For deduplication, the
eventID from a browser event must match the
event_id in the corresponding server event. Learn about Deduplicate Pixel and Server-Side Events.