Facebook Destination Account Integration Options
There are many options available when deciding which Facebook destination account integration to activate, depending on the type of data you’re distributing and your uses:
Distributing first-party data
Distributing Data Marketplace data
Removing opt-out users from first-party data distributions
See the appropriate section below for more information on choosing the integration that is best suited to your use case.
Once you’ve selected the appropriate integration, follow the instructions in “Activate a New Destination Account”.
Tip
To get a brief description of a particular integration, click the help icon in the lower right of the tile in Connect:
Note
When creating a new Facebook destination account, you will be prompted to enter your Facebook Ad Account ID (this is different from your Facebook Business Manager ID).
You can find your ad account ID by going to the Facebook Ads Manager UI and navigating to Business Settings > Accounts > Ad Accounts, selecting the ad account to which you would like to distribute segments, and then copying the ID that appears next to the ad account.
Be sure to pick the integration that’s labeled for your country or region (US, FR, UK, DE, LATAM, etc.).
First-Party Data Integration Options
When distributing first-party data to Facebook, two primary integration methods are available:
Direct Integration: This type of integration creates an audience directly in your Business Manager account, where the data can be used for targeting, Lookalike Audiences, and audience sharing. For most customers, this is the recommended first-party integration.
Managed Integration: This type of integration creates an audience first in LiveRamp’s Facebook ad account and then shares that audiences out to your Facebook ad account. The data delivered can only be used for targeting and is not eligible for Lookalike Audiences or further audience sharing.
Within these two primary methods, additional integration options are available in certain circumstances:
Record Sync: For US data only, the “Record Sync” version of a particular integration allows you to keep your data fresh, up to date, and relevant through the ability to propagate user deletions to Facebook. For more information, see "Keep Destination Data Fresh with Record Sync".
Direct to Platform: For certain countries and regions (such as Latin America, Canada, and Mexico), the “Direct to Platform” version uses the Direct Integration method to pass through hashed PII in a privacy-safe and compliant manner without performing matching (or any leveraging of our Identity Graph) on our end. If you're in one of these non-US markets, talk to your LiveRamp account team to see if Direct to Platform is a good fit. For more information, see "Direct to Platform Destination Integrations”.
For more information on these integration methods and options, see the sections below.
Caution
Our first-party non-Record Sync Facebook integrations are add-only (i.e., they do not support full refreshes). As a result, even if you are importing your files as full refreshes, this will not trigger an overwrite for the corresponding segments in Facebook - it will only add to them. Instead, you may create new segments in Facebook on a regular cadence to achieve the same effect as a “full refresh”.
To keep your U.S. first-party data up-to-date at Facebook, activate a Record Sync-enabled destination (see "Keep Destination Data Fresh with Record Sync" for more information).
Note
Which Facebook Ads properties can be accessed? Both the Managed Integration and the Direct Integration method allow you to distribute data to Facebook's ad system, which you can use to run ads on any Facebook Ads properties (Facebook, Instagram, Audience Manager, etc.).
Direct Integration
The Direct Integration method is the recommended integration method for most customers.
Uses: Targeting, audience sharing, and Facebook Lookalike Audiences.
Note
This integration is required if you want to perform audience sharing and/or use Facebook Lookalike Audiences.
Integration Method: In this type of integration, your first-party distributions are delivered directly to your Facebook account.
Matching Process:
For a regular Direct Integration, LiveRamp matches your data to RampIDs and delivers any pre-approved-for-marketing encrypted hashed PII that is associated with those RampIDs within our Identity Graph to Facebook. Facebook looks for a match between the encrypted hashed PII and Facebook IDs, and then adds those Facebook IDs to the selected Ad Account in the customer’s Business Manager account.
For a Direct to Platform version of this integration, LiveRamp passes through your hashed PII in a privacy-safe and compliant manner without performing matching (or any leveraging of our Identity Graph) on our end. Facebook looks for a match between the encrypted hashed PII and Facebook IDs, and then adds those Facebook IDs to the selected Ad Account in the customer’s Business Manager account.
Requirements:
This integration type requires that you go through the steps (listed in "Add LiveRamp as a Partner in Facebook" below) to add LiveRamp as a partner in Facebook with permission to manage campaigns.
Apart from the Direct to Platform version of this integration, this integration is only for US-based data.
Note
Depending on your Facebook agreement, you might have a limit on the total number of segments you can distribute to each Facebook ad account.
Available Options: When distributing your first-party data to Facebook through the Direct integration, three integration options are available (depending on your country or region):
A Record Sync-enabled Direct Onboarding integration, which keeps your data fresh at the destination by enabling data refreshes to utilize user deletions (see "Keep Destination Data Fresh with Record Sync" for more information).
A Direct Onboarding integration that isn't enabled for Record Sync (US example shown).
Caution
The regular Direct Integration is only available for U.S. first-party data. For non-U.S. first-party data, you must use either the Managed Integration or a Direct to Platform integration.
A Direct to Platform Direct Onboarding integration, which uses the Direct Integration method to pass through hashed PII in a privacy-safe and compliant manner without performing matching (or any leveraging of our Identity Graph) on our end (integration for North American for data from Canada or Mexico shown). For destinations that are based on hashed PII, this allows the destination to match the hashed PII to their universe of users. For more information, see "Direct to Platform Destination Integrations”.
LiveRamp’s Direct Integration delivers data directly into the customer’s Business Manager account (as opposed to the Managed Integration, which uses Facebook’s shared feature).
The data delivered may be used for targeting, Lookalike Audiences, and audience sharing.
Direct Integration Matching Steps
Apart from the matching process for the Direct to Platform version of this integration (shown below), the matching process follows the steps outlined below:
When first-party customer data are uploaded, LiveRamp matches that data to RampIDs and delivers any pre-approved-for-marketing encrypted hashed PII that is associated with those RampIDs within our Identity Graph to Facebook.
Facebook looks for a match between the encrypted hashed PII and Facebook IDs, and then adds those Facebook IDs to the selected Ad Account in the customer’s Business Manager account.
Apart from a Direct to Platform version of this integration, LiveRamp only delivers the encrypted hashed PII that is already contained in our Identity Graph and does not deliver your PII.
Direct to Platform Matching Steps
For a Direct to Platform version of this integration, the matching process follows the steps outlined below:
LiveRamp passes through your hashed PII in a privacy-safe and compliant manner without performing matching (or any leveraging of our Identity Graph) on our end.
Facebook looks for a match between the encrypted hashed PII and Facebook IDs, and then adds those Facebook IDs to the selected Ad Account in the customer’s Business Manager account.
Managed Integration
Uses: Targeting only.
Integration Method: In this type of integration, your first-party data distributions are delivered into LiveRamp’s Facebook ad account, and then shared by LiveRamp to your Facebook ad account.
Matching Process: LiveRamp matches your data to RampIDs, finds all possible Facebook CIDs that are tied to the same RampID, and delivers those matched CIDs via an API to LiveRamp’s Business Manager within Facebook. Facebook then uses a mapping file it has generated in its backend to look up the CIDs it received and matches them to their Facebook IDs.
Available Options: When distributing your first-party data to Facebook through the Managed integration, two integration options are available:
A Record Sync-enabled Managed Onboarding integration, which keeps your data fresh at the destination by enabling data refreshes to use user deletions (for more information, see "Keep Destination Data Fresh with Record Sync").
Note
Record Sync is currently only available to US customers.
A Managed Onboarding integration that isn't enabled for Record Sync.
LiveRamp’s Managed Integration delivers data tied to CIDs (custom IDs) first into LiveRamp’s Facebook ad account and then shares the audiences out to the customer’s Facebook ad account. See Facebook’s help page “About Shared Audiences” for more information.
Matching Steps
On a quarterly basis, LiveRamp sends Facebook a mapping file of pre-approved-for-marketing hashed PII tied to our Facebook CIDs (also referred to as “ExternIDs” by Facebook). Facebook then generates a mapping in their backend of ExternID to Facebook ID, which allows us to send only ExternIDs when delivering data.
When first-party customer data are uploaded, LiveRamp matches that data to RampIDs, finds all possible Facebook CIDs that are tied to the same RampID, and delivers those matched CIDs via an API to LiveRamp’s Business Manager within Facebook.
Facebook then uses the mapping file it generated in its backend to look up the CIDs (ExternIDs) it received and matches them to their Facebook IDs.
LiveRamp then shares the Custom Audience from a LiveRamp-owned ad account to the customer’s ad account.
The data delivered may only be used for targeting and is not eligible for Lookalike Audiences or further audience sharing. See Facebook’s help page “About Lookalike Audience” for more information.
Data Marketplace Distributions
When distributing Data Marketplace data to Facebook, only one integration option is available:
Note
Before activating a Facebook Data Marketplace destination account, you must add LiveRamp as a partner in your Facebook Ad Account with the “View Performance” role for all ad account IDs you're using by following the steps in "Adding LiveRamp as a Partner in Facebook". If you try to activate the destination account without doing this step, the activation process will fail.
Data Marketplace Tile Example
See “Distribute Data Marketplace Data to Facebook” for complete instructions.
Note
Distributing Data Marketplace data to this platform goes through LiveRamp’s Advertiser Direct program, which requires a separate agreement and follows a different process from Data Marketplace distribution to other platforms. For more information, see “Implementing LiveRamp's Advertiser Direct Solution”.
Removing Opt-Out Users
LiveRamp has two Facebook Opt Out destination account integration types to enable you to remove opt-out users from your Facebook first-party data campaigns by distributing segments containing opt-out users to that destination account:
To opt out users that are being distributed through a Facebook Direct Onboarding destination account, use the Facebook (U.S.) Direct Opt Outs destination account integration:
Direct Opt Outs Tile Example
To opt out users that are being distributed through a Facebook Managed Onboarding destination account, use the Facebook Managed Opt Outs destination account integration:
Managed Opt Outs Tile Example
See “Distribute First-Party Data to Facebook” for complete instructions.