Send campaigns to Facebook

You can use segments and campaigns to build custom audiences in Facebook. 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 on Facebook.

Use custom audiences to advertise to these customers on Facebook, Instagram, and Messenger, and to use Audience Network to extend your advertising beyond Facebook to reach new audiences on apps and mobile devices, such as WhatsApp.

A Facebook destination works like this:

1. Build a custom audience using a segment.

2. Add that segment to a campaign, select Facebook as a destination for at least one recipient group, and then configure the schedule for your campaign.

3. Send that audience to Facebook.

   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.

   Facebook 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:

   1. Removes existing customers from an audience without resetting your ad set’s learning phase when an audience is part of active ad sets.

   2. Replaces those users with the list of customers that was sent to Facebook from Amperity.

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

4. Build ads in Meta Ads Manager.

   What is Meta Ads Manager?

   Meta Ads Manager is a unified ad creation tool that you can use to create and publish ads to Facebook, Messenger, Instagram and the Meta Audience Network. When you send data to Facebook using the Facebook Ads destination, your data will be available from Meta Ads Manager.

   	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 .

5. 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 to configure Facebook as a channel to which you can send campaigns.

Build campaign

Use the campaign editor to build campaigns that send data to Facebook. Add a segment, define exclusions and sub-audiences, and then configure Amperity to send campaign data to Facebook.

Important

Amperity requires access to Facebook. This access may expire or be removed periodically, depending on how OAuth is managed at Facebook. If Amperity is unable to send data to Facebook ask your DataGrid Operator to reauthorize access to Facebook.

To build a campaign

1. From the Campaigns tab, click Create Campaign. This opens the New Campaign page.

2. Give your campaign a name.

3. Choose the segment that represents the audience to use for this campaign.

4. Optional. Choose a segment that contains a list of customers to exclude from this campaign.

5. Configure at least one control group/recipient group set for this campaign. Rename these groups as necessary.

   Tip

   A campaign may have many control group/recipient group sets and each set may have more than one recipient group. Click Add recipient group to add another recipient group. Click Add Sub-audience to add more sets to this campaign, and then use the Audience Builder to define the criteria for each sub-audience.

6. For each control group/recipient group set, configure the percentages for each group, and then select a destination that is configured to send campaigns from Amperity to Facebook.

7. Click Edit attributes to review the attributes that Amperity will send to Facebook.

   Facebook 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 Facebook. When you open the Edit attributes page for Facebook, it will be similar to:

   

   Note

   The Merged_Customers table is the default table from which data is sent to Facebook, even though your segments were 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 customer profile data that exists in the Customer_360 table.

8. Specify if this campaign is a one-time or recurring campaign, define the delivery schedule, and then define the campaign launch date. (Amperity uses the campaign launch date internally to improve results tracking for campaigns.)

9. Click Schedule.

   Note

   Amperity will begin processing the segments that define audiences, exclusions, and sub-audiences, and will then send the results to configured destinations. Please allow for enough time for Amperity to complete this process before kicking off a campaign in your downstream systems.

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 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