Send custom audiences to Meta Ads Manager

Note

This topic contains information about configuring a destination that sends query results to Meta Ads Manager using orchestrations. To configure a destination that sends audiences to Meta Ads Manager using campaigns see this topic .

Send custom audiences to Meta Ads Manager to help find people who already know about or have engaged with your brand. Use custom audiences for re-marketing, finding potential repeat customers, and finding lookalike audiences that can be activated from Facebook, Facebook Messenger, Instagram, and WhatsApp.

The Facebook Marketing API, specifically the Replace Users endpoint, is used to send custom audiences.

This endpoint removes existing customers from an audience without resetting your ad set’s learning phase when an audience is part of active ad sets, and then replaces those users with the list of customers that was sent to Meta Ads Manager from Amperity.

Note

Changes to custom audiences are not immediately available in Meta Ads Manager. Allow for up to 24 hours after the point at which Amperity has finished sending audience updates for them to be available.

Get details

Review the following details before configuring credentials for Meta Ads Manager and before configuring Amperity to send custom audiences to Meta Ads Manager.

Detail 1.

Credential settings

Access token

Required

A refresh token is generated by the OAuth process and authorizes Amperity to send data to Meta Ads Manager. The value for the refresh token is updated automatically.
Detail 2.

Meta Ads Manager settings

Account ID

The account ID for your Meta Ads Manager account.

Custom audience name (Required at orchestration)

The name of the custom audience in Meta Ads Manager.

Customer file source

A setting that describes how the information in the custom audience was originally collected. Select one of the following settings:

  • USER_PROVIDED_ONLY

  • PARTNER_PROVIDED_ONLY

  • BOTH_USER_AND_PARTNER_PROVIDED

About Meta Ads Manager

Audiences sent to Meta Ads Manager have access to Facebook, Messenger, Instagram and the Meta Audience Network.

Configure credentials

Configure credentials for Meta Ads Manager before adding a destination.

An individual with access to Meta Ads Manager should use SnapPass to securely share “refresh token” details with the individual who will configure Amperity.

To configure credentials for Meta Ads Manager

Step 1.

From the Settings page, select the Credentials tab, and then click the Add credential button.
Step 2.

In the Credentials settings dialog box, do the following:

From the Plugin dropdown, select Meta Ads Manager.

Assign the credential a name and description that ensures other users of Amperity can recognize when to use this destination.
Step 3.

The settings that are available for a credential are determined by the credential type. For the “facebook” credential type, configure settings, and then click Save.

Access token

Required

A refresh token is generated by the OAuth process and authorizes Amperity to send data to Meta Ads Manager. The value for the refresh token is updated automatically.

Reauthorize Amperity

You may need to reauthorize access to Meta Ads Manager. This is necessary when an authorization token has expired or when it has been removed by someone with permission to manage access within Meta Ads Manager. To reauthorize access to Meta Ads Manager, follow the steps to configure OAuth and create a new credential.

Terms of service

The custom audience terms of service must be signed by each business user that is associated with your Meta Ads Manager account. If the terms of service are not signed, a permissions error will prevent Amperity from sending data to Meta Ads Manager.

The permissions error is similar to:

Permissions error: To create or edit an audience with an uploaded
customer list, please agree to the Custom Audience terms at
https://business.facebook.com/ads/manage/customaudiences/tos/?act=123.

To resolve this error the terms of service must be signed by a business user who has a role in your Meta Ads Manager account.

Add destination

Use a sandbox to configure a destination for Meta Ads Manager. Before promoting your changes, send a test audience, and then verify the the results in Meta Ads Manager. After the end-to-end workflow has been verified, push the destination from the sandbox to production.

To add a destination for Meta Ads Manager

Step 1.

Open the Destinations page, and then click the Add destination button.

Add

To configure a destination for Meta Ads Manager, do one of the following:

  1. Click the row in which Meta Ads Manager is located. Destinations are listed alphabetically and you can scroll up and down the list.

  2. Search for Meta Ads Manager. Start typing “meta”. The list will filter to show only matching destinations. Select “Facebook”.
Step 2.

Select the credential for Meta Ads Manager from the Credential drop-down, and then click Continue.

Tip

Click the “Test connection” link on the “Configure destination” page to verify that Amperity can connect to Meta Ads Manager.
Step 3.

In the “Destination settings” dialog box, assign the destination a name and description that ensures other users of Amperity can recognize when to use this destination.

Configure business user access

By default a destination is available to all users who have permission to view personally identifiable information (PII).

Enable the Admin only checkbox to restrict access to only users assigned to the Datagrid Operator and Datagrid Administrator policies.

Enable the PII setting checkbox to allow users with limited access to PII access to this destination.

Restricted PII access is enabled when the Restrict PII access policy option that prevents users who are assigned to that option from viewing data that is marked as PII anywhere in Amperity and from sending that data to any downstream workflow.
Step 4.

Configure the following settings, and then click “Save”.

Account ID

The account ID for your Meta Ads Manager account.

Custom audience name (Required at orchestration)

The name of the custom audience in Meta Ads Manager.

Customer file source

A setting that describes how the information in the custom audience was originally collected. Select one of the following settings:

  • USER_PROVIDED_ONLY

  • PARTNER_PROVIDED_ONLY

  • BOTH_USER_AND_PARTNER_PROVIDED
Step 5.

After this destination is configured, users may configure Amperity to:

  • Use orchestrations to send query results

  • Use orchestrations and campaigns to send audiences

  • Use orchestrations and campaigns to send offline events

to Meta Ads Manager.

Facebook Marketing API keys

The following Amperity columns should be mapped to the corresponding Facebook Marketing API keys when they are present in query data:

Amperity Column

Facebook API Key

Description

Amperity ID

EXTERN_ID

This value is a unique ID used by the advertiser, such as a loyalty ID, a customer ID, an external cookie ID, or the Amperity ID.

For this key, the connector trims leading and trailing whitespace.

Tip

A query can alias the Amperity ID directly in a query: SELECT amperity_id AS EXTERN_ID from custom_table. This approach can be helpful for queries that are dedicated to returning data to be sent only to Facebook Ads.

Email Addresses

EMAIL

For this key, the connector:

  • Trims leading and trailing whitespace

  • Converts to lower-case

  • Hashes data as SHA-256

Phone Numbers

PHONE

Converts each phone number to E.164 format which represents a phone number as a number up to fifteen digits in length (without spaces) that starts with a + symbol. For example: +12061234567.

For this key, the connector:

  • Trims leading and trailing whitespace

  • Removes symbols, letters, and any leading zeros

  • Hashes data as SHA-256

Gender

GEN

For this key, the connector:

  • Trims leading and trailing whitespace

  • Converts to lower-case

  • Converts to m and f

  • Hashes data as SHA-256

Birth Date

BIRTH

The birth date in Amperity date format.

For this key, the connector splits this value into three fields: birth year (DOBY), birth month (DOBM), and birth day (DOBD).

Birth Year

DOBY

Warning

Do not pass this column. For this key, the connector will use birthdate to split out the value for DOBY with a format of YYYY and a range from 1900 to the current year.

Birth Month

DOBM

Warning

Do not pass this column. For this key, the connector will use birthdate to split out the value for DOBM with a format of 01 to 12.

Birth Day

DOBD

Warning

Do not pass this column. For this key, the connector will use birthdate to split out the value for DOBD with a format of 01 to 31.

Last Name

LN

This key supports special characters and non-Roman alphabet characters. For this key, the connector:

  • Trims leading and trailing whitespace

  • Converts to lower-case

  • Removes punctuation

  • Updates special characters to UTF-8 format

  • Hashes data as SHA-256

First Name

FN

This key supports special characters and non-Roman alphabet characters. For this key, the connector:

  • Trims leading and trailing whitespace

  • Converts to lower-case

  • Removes punctuation

  • Updates special characters to UTF-8 format

  • Hashes data as SHA-256

First Initial

FI

Warning

Do not pass this column. The connector will use the first character of the normalized first name.

US States

ST

A two-character ANSI abbreviation code for US states.

For this key, the connector:

  • Trims leading and trailing whitespace

  • Converts to lower-case

  • Normalizes states located outside of the United States

  • Removes punctuation, special characters, and whitespace

  • Hashes data as SHA-256

City

CT

For this key, the connector:

  • Trims leading and trailing whitespace

  • Converts to lower-case

  • Removes punctuation, special characters, and whitespace

  • Hashes data as SHA-256

Zip Code

ZIP

Use only the first five digits for the United States. Use Use postcodes (area, district, sector) format for United Kingdom.

For this key, the connector:

  • Trims leading and trailing whitespace

  • Converts to lower-case

  • Removes whitespace from lower-case for United Kingdom

  • Trims to five digits for United States

  • Hashes data as SHA-256

Country Code

COUNTRY

A two-letter country code in ISO 3166-1 alpha-2 format.

For this key, the connector:

  • Trims leading and trailing whitespace

  • Converts to lower-case

  • Hashes data as SHA-256

Mobile Advertiser ID

MADID

For this key, the connector:

  • Trims leading and trailing whitespace

  • Converts to lower-case

  • Keeps hyphens

  • Hashes data as SHA-256