The Conversions API allows advertisers to send web events from their servers directly to Facebook. Server events are linked to a pixel and are processed like browser pixel events. This means that server events are used in measurement, reporting, and optimization in the same way as browser pixel events.
POSTrequests and learn more about dropped events, batch requests, and event transaction time.
The Conversions API used to be called Server-Side API.
Website events shared using the Conversions API require the following data parameters:
event_source_url, while non-web events require only
action_source. These parameters contribute to improving the quality of events used for ad delivery and may improve campaign performance.
We've released a Limited Data Use feature to give businesses more control over how their data is used in our systems and better support them with their California Consumer Privacy Act (CCPA) compliance efforts.
For the Conversions API, implement this feature by adding
data_processing_options_state inside each event within the data parameter of your events.
Required and optional parameters you can use to improve ads attribution and delivery optimization.
See how your payload should be structured when it is sent to Facebook from your server.
Learn how to handle error codes returned by the Conversions API.
For subscription advertisers. Prerequisites, required parameters, and reporting metrics for subscription events.
Facebook Pixel Events
Business Help Center
Playbook and Webinar
Learn more about the Limited Data Use feature and how to implement it for Conversions API.