What are server event parameters?

What are server event parameters?

Following are the server events paramters

1. event_name:

A standard event or custom event name. This field is used to deduplicate events sent by both web (via Meta Pixel) and the Conversions API. The event_id parameter is also used in deduplication.
For the same customer action, event from the browser or app event matches 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/app event arrive at approximately the same time (that is, within 5 minutes of each other), we favor the browser/app event. Learn more about Deduplicate Pixel and Server Events.

2. event_time

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.
The event_time can be up to 7 days before you send an event to Facebook. If any event_time in data is greater than 7 days in the past, we return an error for the entire request and process no events.

3. user_data

A map that contains customer information data.

4. event_source_url
​

The browser URL where the event happened. The URL must begin with http:// or https:// and should match the verified domain.

Note: The event_source_url is required for website events shared using the Conversions API.

5. event_id

This ID can be any unique string chosen by the advertiser. The event_id and event_name parameters are used to deduplicate events sent by both web (via the Meta Pixel) or app (via SDK or App Events API) and the Conversions API. Note that while event_id is marked optional, it is recommended for event deduplication.

For deduplication, the eventID from a browser or app event must match the event_id in the corresponding server event. Learn more about Handling Duplicate Pixel and Conversions API Events.

An order number or transaction ID are two potential identifiers that can be used for event_id. For example, if a customer makes two purchases on your website with order numbers 123 and 456, each Conversions API call would need to include its respective order number for event_id. This allows us to properly distinguish these two purchase events as distinct orders. The two corresponding browser Pixel purchase events would need to also send the same order numbers in the eventID parameter for us to understand that there were only two events that took place, not four unique purchases.

For other events without an intrinsic ID number, a random number (so long as the same random number is sent between browser and server events) can be used.

6. action_source

This field allows you to specify where your conversions occurred. Knowing where your events took place helps ensure your ads go to the right people. By using the Conversions API, you agree that the action_source parameter is accurate to the best of your knowledge.

The values you can send in the action_source field are as follows:
email — Conversion happened over email.
website — Conversion was made on your website.
app — Conversion was made on your mobile app.
phone_call — Conversion was made over the phone.
chat — Conversion was made via a messaging app, SMS, or online messaging feature.
physical_store — Conversion was made in person at your physical store.
system_generated — Conversion happened automatically, for example, a subscription renewal that’s set to auto-pay each month.
other — Conversion happened in a way that is not listed.

    • Related Articles

    • What are the recommended steps to set up event deduplication?

      Deduplication is handled automatically by Datahash CAPI Gateway setup. Datahash ensures that the same event ID is used for events sent through both client-side and server-side to avoid duplicates.

    • Server-to-server integration: what is it?

      Server-to-server integration is the process that enables two servers to communicate directly with each other without the need for client-side interaction. This type of integration allows to create an automated workflow, offers secure data exchange ...

    • How to Create offline event sets

      Creating an offline event set is one of the first steps to help you understand how much your Meta ads lead to in-store events. To create an offline event set: Go to Events Manager. Navigate to the green plus sign and select Connect data sources. ...

    • Post Live QA of Event Matching

      Step 1 : Go to Event Matching. Step 2 : Follow below steps for event matching. During the audit please make sure that script is making First Party data correctly. Reference : How to check First Party data on a website? For Lower funnel events like ...

    • Can I use the CAPI Gateway for offline event tracking?

      No, the Conversions API Gateway (CAPI Gateway) is specifically designed for website event tracking. For offline event tracking, you can still send events directly to Meta, but it requires a different type of integration. If you are looking to ...