Facebook 1P

Channel Type - Private

Products Supported - Targeting and Connect

Integration Type - 3P

This integration with Facebook Business Manager allows us to directly create audiences within the client's Facebook Ad account instead of licensing them from our third-party Facebook integration.

It is a global integration for Connect and Targeting and is live for all the countries. This integration only supports the following identifiers: MAID uploads for Targeting

MAID, FB External ID, HEM and Phone for Connect

Creating a Destination for Facebook 1P

Perform the following steps to create a Destination for Facebook 1P:

1. Log into Unity and go to the DESTINATIONS application.
2. Under the All Channels section, search for Facebook 1P.
3. Click Facebook 1P and enter the following details in the window that appears.
   1. Enter a name for the Destination.
   2. Enter the 16 digit Ad Account ID number.
   3. Enter the Access Token.
   4. Enter the API Version.
   5. Click Save Destination.

Creating a Segment for Facebook 1P

The following steps summarize the process of linking a Segment to a Destination:

1. Log into Unity to create a Segment from the TARGETING application.
2. Select the appropriate attributes.
3. To activate the Segment, search for the Facebook 1P Destination that you created and link the same. It may take up to one hour before Facebook 1P adds users to an audience.

Internal Content for Facebook 1P

Segment Creation

Segment creation in Unity is synonymous to creating a Custom Audience in Facebook. To create a Facebook audience, create a Connect segment and select a Facebook 1P destination. The corresponding audience will be created in Facebook. Destination creation in Unity requires

a. Ad Account ID b.client Access token as an input

Instructions on how a client can generate the access token is mentioned here: https://docs.google.com/document/d

/1L6h7G3x1u1S9E1JHS1VI9FaMsuQG4hE-_40XGVjpV2U/edit?usp=sharing

**IMPORTANT: These segments would be directly created in the client’s account so they would not appear under zeotap’s ad accounts unlike the current 3rd party setup. Also the 500 custom audiences limit would be applicable to each ad account client uses rather than being applied to the zeotap account.

Facebook compares the data uploaded by us against a segment with their encrypted user data. If they find a match, the IDs are added to the custom audience/segment and ads are delivered to them.

Segment Licensing

This is no longer required as segments are created directly under the client’s account.

Error Log

It is important for the client to follow the steps and get the permanent token (never-ending token) from their end. If they use the short-lived token it will expire in 2-3 hours and the segments will fail.