Facebook CAPI Adapter
If you deliver your ads through Facebook, our Facebook Conversion API Adapter can help you improve your measurement by using ATS. The ATS Facebook CAPI Adapter offers an easy way to send both conversion event data paired with an envelope. You can implement Facebook CAPI Adapter as part of ATS.js through LiveRamp Console or directly with our API, to bypass the complexity of building a server-side integration with Facebook.
About Facebook CAPI Adapter
The Facebook Conversion API Adapter allows you to send conversion events directly to Facebook. Facebook CAPI does not use cookies and is a more reliable way to share data with Facebook 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.
Requirements
To use Facebook CAPI, you must have the following:
Facebook Envelope: Contact our team at atsimplementations@liveramp.com to get Facebook 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 Facebook-encoded RampID, scoped for Facebook.
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.
Facebook 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 Facebook's requirements and how to obtain them here.
Set up Facebook CAPI Integration in Console
In Console, select ATS and then select the Web tab.
Select a configuration you want to integrate Facebook CAPI with, or create a new configuration.
Select the Integration tab and click New.
Select Facebook Conversion API.
Select your ATS implementation method.
Enter a Meta Pixel ID and a Facebook Token.
Select an Action Source for where the conversion events occur. The action source impacts what data are required to be sent to Facebook on a given event. If you select Website, ATS.js will send the following data fields to Facebook CAPI 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 Facebook CAPI Adapter via ATS.js, go to the following article: Implement Facebook CAPI Adapter via ATS.js.
If you are implementing Facebook CAPI via an HTTP POST call, Click Save. See our developers documentation to learn how to create the request.