The Conversions API is designed to create a connection between an advertiser’s marketing data (such as website events, app events, business messaging events and offline conversions) from an advertiser’s server, website platform, mobile app, or CRM to Meta systems that optimize ad targeting, decrease cost per result and measure outcomes.
Rather than maintaining separate connection points for each data source, advertisers are able to leverage the Conversions API to send multiple event types and simplify their technology stack. In the case of direct integrations, this entails establishing a connection between an advertiser’s server and Meta’s Conversions API endpoint.
Server events are linked to a dataset ID and are processed like events sent via the Meta Pixel, Facebook SDK for iOS or Android, mobile measurement partner SDK, offline event set, or .csv upload. This means that server events may be used in measurement, reporting, or optimization in a similar way as other connection channels. Offline events may be used for attributed offline events measurement, offline custom audience creation or measurement.
For optimal ad performance and measurement, we recommend that advertisers follow the Conversions API best practices.
POSTrequests and learn more about dropped events, batch requests, and event transaction time.
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.
Meta Pixel Events
Business Help Center
Playbook and Webinar
Learn more about the Limited Data Use feature and how to implement it for Conversions API.