Skip to main content

Conversions API for Meta

If you deliver your ads through Facebook, you can utilize the Conversions API for Meta to send conversion events to Meta systems. This allows you to optimize ad targeting, decrease cost per result, and measure outcomes through Meta's events manager. You can implement Conversions API for Meta with ATS for Web through Console or directly with our API, to bypass the complexity of building a server-side integration with Meta.

If you need to enable attribution analysis for offline data (such as in-store transactions or call center contacts), you can do this in LiveRamp Connect with the Facebook Offline Conversions API Attribution Program.

About Conversions API for Meta

The Conversions API for Meta adapter allows you to send conversion events directly to Meta. It does not use cookies and is a more reliable way to share data with Meta than through browser-based methods, optimizing your ads delivery. You will have more accurate insights into your customers' actions and their full journey, while maintaining user privacy with opt-out handling.


To implement the conversions API, you must have the following:

  • Meta envelope: Contact our team at to get Meta envelopes implemented for you. When applied, two envelopes will be returned on a given ATS request. One is a regular ATS identity envelope and the other is a Meta-encoded RampID.

  • Meta Pixel ID: You must obtain a Meta pixel ID to use the Conversions API. If you’ve already set up a pixel for your website, we recommend that you use the same Meta pixel ID for your browser and server events.

  • Access token: To use the Conversions API, you need an access token. There are two ways of getting your access token: via Events Manager (recommended) or using your own app.

Learn more about Meta's requirements and how to obtain them here.

Don't forget to add Conversions API for Meta to your subscription from the Marketplace. To learn how to do this, see Add Products to Your Subscription.

Set Up Conversions API for Meta Integration in Console

Once you have completed all the requirements, you can start the process of integrating your ATS configuration with Conversions API for Meta in Console.

  1. In Console, select ATS and then select the Web tab.

  2. Select a configuration you want to integrate with, or create a new configuration.

  3. Select the Integration tab and click New.

  4. Select Facebook Conversion API.

  5. Select your ATS implementation method.

  6. Enter a Meta Pixel ID and the access token.

  7. Select an Action Source for where the conversion events occur. The action source impacts what data are required to be sent to Meta on a given event. If you select Website, ATS.js will send the following data fields to the conversions API by default; client_user_agent, action_source, and event_source_url. Other options require only action_source. These parameters contribute to improving the quality of events used for ad delivery and may improve campaign performance.


To continue implementing Conversions API for Meta with ATS for Web in Console, go to the following article: Implement Conversions API for Meta via ATS for Web.

If you are implementing Conversions API for Meta via an HTTP POST call, Click Save. See our developers documentation to learn how to create the request.