Send campaigns to Facebook Ads

Facebook Ads appear in the news feed and in the right-side column on Facebook. Facebook Ads provides an API for integrating with third-party systems.

Note

This destination uses the Facebook Marketing API .

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

Important

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

This topic describes the steps that are required to send customer profiles to Facebook Ads.

  1. Build a segment

  2. Build campaign

Note

Ask your DataGrid Operator or your Amperity representative to configure Facebook Ads as a channel to which you can send campaigns.

Build segment

Use the visual editor in the Segments tab to easily build a segment from a series of drop-downs and picklists. As you build the attribute profile refresh segment insights to see how many customers match and to see how much value they bring to your business. When the segment is ready, activate it, and then use it to initiate marketing campaigns.

To build a segment for use with campaigns

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

  2. Give your segment a name.

  3. Select a table that contains the attributes you want to use, and then use the drop-downs, picklists, conditions, and values to define the attribute profile.

    Note

    The Customer_360 table is the default. For many segments it’s the only table you will need.

  4. When more than one attribute is present within an attribute group use AND or OR to filter values on more than one condition.

  5. Click Add section to add additional attribute groups.

    Each attribute group has the same requirement for using AND or OR to filter values. There is another AND versus OR choice that must be made in-between each each attribute group.

  6. For each attribute group that is added to the segment, select the database table that contains the attributes, and then select attributes.

    Tip

    Any table that is listed in the lower right may be used to build the attribute profile. Open the Data Explorer to learn more about the individual attributes within these tables.

  7. To view updated segment insights based on the currently-defined attributes, click REFRESH. This will validate the segment, after which segment insights are updated to match the condition-value pairs associated to all of the attributes in the segment.

  8. When the segment returns the parameters that meets the goals for your campaign, click ACTIVATE.

Build campaign

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

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

    Important

    Do not assign Facebook Ads to the control group!

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

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

    Attributes for campaigns that send data to Facebook Ads.

    Note

    The Merged_Customers table is the default table from which data is sent to Facebook Ads, 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