Send audiences to Meta Ads Manager¶
You can use segments and campaigns to build custom audiences in Meta Ads Manager. Send customer information, such as email addresses, phone numbers, names, birthdates, gender, city, state, postal code, and mobile advertising IDs, from Amperity to find customer matches.
Use audiences in Meta Ads Manager to advertise to customers on Facebook, Instagram, and Messenger, and to use Meta Audience Network to extend your advertising beyond Facebook to reach new audiences on apps and mobile devices, such as WhatsApp.

A Meta Ads Manager destination works like this:
Build a custom audience using a segment.
Add that segment to a campaign, select Meta Ads Manager as a destination for at least one recipient group, and then configure the schedule for your campaign.
Send that audience to Meta Ads Manager.
Important
The custom audience terms of service must be signed by each business user that is associated with your Facebook Ads account. If the terms of service are not signed, a permissions error will prevent Amperity from sending data to Facebook Ads.
Meta Ads Manager uses OAuth to grant access to Amperity. You will need to reauthorize OAuth if the token expires or is removed.
Ask your DataGrid Operator to help resolve these issues if they occur.
Note
This destination uses the Facebook Marketing API , specifically the Replace Users endpoint . 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.
Replaces those users with the list of customers that was sent to Meta Ads Manager from Amperity.
Changes to 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.
Build ads in Meta Ads Manager.
Place ads on Facebook, Instagram, and Messenger; use Audience Network to extend advertising beyond Facebook to reach audiences on apps and mobile devices, such as WhatsApp.
Note
Ask your DataGrid Operator or your Amperity representative for help configuring Meta Ads Manager as a destination to which you can send campaigns for customer activation.
Build a segment¶
Use the Segment Editor to build any audience using a series of drop-downs and picklists.
As you define the attribute profile for an audience be sure to refresh segment insights to see how many customers match your audience and to see how much value they bring to your business.
When the segment is ready, activate it, and then use it use it in a campaign to send to your preferred destinations for customer activation.
Which attributes should you use?
You can use any attribute that is in your customer 360 database to define your audience.
When the list of customers who belong to this audience is sent to Meta Ads Manager as part of a campaign you will be required to choose specific attributes to send.
Meta Ads Manager supports the following attributes: customer profiles.
Build a campaign¶
Use the campaign editor to build campaigns that send data to Meta Ads Manager. Add a segment, define exclusions and sub-audiences, and then configure Amperity to send campaign data to Meta Ads Manager.
Important
Amperity requires access to Meta Ads Manager. This access may expire or be removed periodically, depending on how OAuth is managed at Meta Ads Manager. If Amperity is unable to send data to Meta Ads Manager ask your DataGrid Operator to reauthorize access to Meta Ads Manager.
To build a campaign
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: |
Email Addresses |
For this key, the connector:
|
|
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:
|
Gender |
GEN |
For this key, the connector:
|
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 |
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 |
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 |
Last Name |
LN |
This key supports special characters and non-Roman alphabet characters. For this key, the connector:
|
First Name |
FN |
This key supports special characters and non-Roman alphabet characters. For this key, the connector:
|
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:
|
City |
CT |
For this key, the connector:
|
Zip Code |
ZIP |
Use only the first five digits for the United States. Use postcodes (area, district, sector) format for United Kingdom. For this key, the connector:
|
Country Code |
COUNTRY |
A two-letter country code in ISO 3166-1 alpha-2 format. For this key, the connector:
|
Mobile Advertiser ID |
MADID |
For this key, the connector:
|