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 custom audiences in Meta Ads Manager to advertise to customers on Facebook, Instagram, and Messenger, along with using the Meta Audience Network to extend your advertising beyond Facebook and 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.
Note
You can send offline events to Meta Ads Manager using the Conversions API for offline events .
Offline events are sent as a collection of transaction details that occurred within the previous seven days, after which Amperity can be configured to maintain a 7-day rolling window of those events.
Add that segment to a campaign, select Meta Ads Manager as a destination for at least one treatment 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
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.
What is Meta Ads Manager?
Audiences sent to Meta Ads Manager have access to Facebook, Messenger, Instagram and the Meta Audience Network.
Use Meta Ads Manager to configure a variety of ad placements across Facebook .
Use Meta Ads Manager to configure objectives that place ads on Instagram .
Use Meta Ads Manager to configure objectives that place ads on Messenger .
Use Audience Manager to reach users who are not on Facebook or Instagram, but are on mobile apps that are within the audience network. For example, creating ads that open conversation threads in WhatsApp .
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
|
The campaign builder is available from the Campaigns page. The Create Campaign button in the top right corner of the page opens the campaign builder. After the campaign builder opens, give your campaign a name. 
Tip The campaign name will always appear in the filename that is sent to any destination. Use good naming patterns for the campaigns you will send to Meta Ads Manager. Good naming patterns help ensure that you can easily find your campaigns within Amperity and that the campaign is discoverable in Meta Ads Manager by users who may not be the same users who built the campaign in Amperity. Avoid duplication between campaign and treatment group names. Avoid using Meta Ads Manager in the name unless the campaign is sent only to Meta Ads Manager. Use a naming pattern that ensures the campaign name works across every treatment group that is configured within any sub-audience. If brand names and/or region names apply to all sub-audiences in the campaign, consider using them within the campaign name. |
|
All campaigns start with an audience. Choose a segment from the Include drop-down list. The customers in that list will become the audience for this campaign. 
Tip When a campaign starts with an audience that is defined by a single segment, you can use the segment insights for that segment as a way to measure the performance of that audience over time. |
|
Sometimes campaigns need to exclude certain members of your audience. For example, a churn prevention campaign is often configured to exclude customers who have opted-out of SMS messaging and/or who have unsubscribed from an email list. When you need to exclude audience members, choose one (or more) segments from the Exclude drop-down list. The customers in an exclusion list will be removed from the audience for this campaign. 
|
|
Some campaigns have just one audience, while others have many and require sub-audiences. Sub-audiences can be many things. How you choose to configure them depends on your audience, marketing strategy and goals, and the type of campaign you will run in Meta Ads Manager. Click Add treatment to add another treatment group to a sub-audience. The total percentages for all treatment groups (and the control group, if present) must be 100%. Click Add Sub-audience to add more sub-audiences to this campaign, and then use the Audience Builder to define the criteria for that sub-audience. |
|
Assign Meta Ads Manager as a destination for at least one treatment group, and then edit the attributes for the sub-audience to ensure Amperity is sending the right data to Meta Ads Manager. |
|
Click Edit attributes to review the attributes that Amperity will send to Meta Ads Manager. Meta Ads Manager requires the EXTERN_ID, EMAIL, FN, LN, ST, CT, ZIP, COUNTRY, BIRTH, GEN, MADID, and PHONE attributes. The MADID (mobile advertising ID) attribute is optional. Amperity pre-selects the list of attributes that may be sent to Meta Ads Manager. The Edit attributes page for Meta Ads Manager is similar to: 
Note The Merged Customers table is the default table from which data is sent to Meta Ads Manager, even though segments are often built against the Customer 360 table. This is by design. The Merged Customers table is the underlying table for customer profile data and is the source for all customer profile data that exists within the Customer 360 table. |
|
A campaign can be configured to be sent once or on a recurring basis. A campaign can also be scheduled (i.e. “to be sent at the time you choose in the future”) or to be sent as soon as possible. 
|
|
Enter the date on which you plan to launch your campaign in Meta Ads Manager. This date helps Amperity improve results tracking and campaign results measurement. 
|
|
When your campaign is ready, click the Schedule button in the top right corner of the Campaigns page. Note Amperity will begin processing the segments that define audiences, exclusions, and sub-audiences, and will then send the results to Meta Ads Manager. Please allow for enough time for Amperity to complete this process before starting a campaign in Meta Ads Manager. |
Configure default attributes¶
Each unique destination that is configured to send data to Meta Ads Manager may be configured to have a set of default attributes that will sent to Meta Ads Manager every time this destination is associated with a treatment group in an active campaign.
Default attributes may be configured for a destination by clicking the Default attributes link next to the Create campaign button on the Campaigns page.
The source table is set to Merged Customers for most attributes. Your brand may configure each attribute to be pulled from the source table that best represents how your brand wants to use the attribute in Meta Ads Manager.
Meta Ads Manager has the following requirements for attributes.
Source attribute |
Destination attribute |
|---|---|
amperity_id |
EXTERN_ID |
given_name |
FN |
surname |
LN |
state |
ST |
city |
CT |
postal |
ZIP |
country |
COUNTRY |
birthdate |
BIRTH |
gender |
GEN |
phone |
PHONE |
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 |
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 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:
|
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:
|