Send campaigns to Google Audience Partner API

Google Audience Partner API uses first-party data that your customers have shared with you to enable advertising across Google – including search and display advertising, the Shopping tab, Gmail, and YouTube – to your customers and to similar audiences.

Note

This destination uses the Google Audience Partner API .

Changes to audiences are not immediately available in Google Audience Partner API. Allow for up to 48 hours after the point at which Amperity has finished sending audience updates for them to be available.

Important

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

This topic describes the steps that are required to send customer profiles to Google Audience Partner API.

  1. Build a segment

  2. Build campaign

Note

Ask your DataGrid Operator or your Amperity representative to configure Google Audience Partner API 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 Segments tab, click Create Segment. This opens the Segment Editor.

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

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

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

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

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

  7. When the segment returns the parameters that meets the goals for your campaign, click Save, and then give your segment a name.

Build campaign

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

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 Google Audience Partner API.

    Important

    Do not assign Google Audience Partner API to the control group!

  7. Click Edit attributes to review the attributes that Amperity will send to Google Audience Partner API.

    Google Audience Partner API accepts any combination of email address, phone number, first name, last name, zip code, and country attributes.

    Amperity pre-selects the list of attributes that may be sent to Google Audience Partner API. When you open the Edit attributes page for Google Audience Partner API, it will be similar to:

    Attributes for campaigns that send data to Google Audience Partner API.

    Note

    The Merged_Customers table is the default table from which data is sent to Google Audience Partner API, 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.

Google Audience Partner API Matching

Google Audience Partner API matching can be done through the following list ID types:

Contact Info Matching

Personally identifiable information (PII) is any data that could potentially identify a specific individual. PII data includes details like names, addresses, email addresses, and other profile attributes, but can also include attributes like a loyalty number, customer relationship management (CRM) system identifiers, and foreign keys in customer data.

A list can be matched to contact information that contains PII data. If a row contains a NULL value, it will be automatically filtered out by the connector and will be shown in the error logs. Each field should be matched to (at least) one of the following columns:

Amperity Column

Google API Key

Description

Email Address

email

For this key, the connector:

  • Trims leading and trailing whitespace

  • Converts to lower-case

  • Hashes data as SHA-256

Phone Number

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

  • Hashes data as SHA-256

Last Name

lastname

For this key, the connector:

  • Trims leading and trailing whitespace

  • Removes spaces in-between

  • Converts to lower-case

  • Hashes data as SHA-256

First Name

firstname

For this key, the connector:

  • Trims leading and trailing whitespace

  • Removes spaces in-between

  • Converts to lower-case

  • Hashes data as SHA-256

Zip Code

zip

For this key, the connector:

  • Trims leading and trailing whitespace

  • Converts to lower-case

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

Mobile Device ID Matching

A list can be matched to mobile device IDs. These may be identifier for advertising (IDFA) or Google advertising IDs (AAID) for mobile devices. If a row contains a NULL value, it will be automatically filtered out by the connector and will be shown in the error logs.

Amperity Column

Google API Key

Description

Mobile Device ID

mobile-id

A list of mobile device IDs provided to Amperity by the customer. For this key, the connector:

  • Trims leading and trailing whitespace

  • Converts to lower-case

  • Retains any hyphens in the mobile device ID

User ID Matching

A list can be matched to advertiser-generated and assigned user IDs and/or to custom IDs created by the customer. This list of IDs must be provided to Amperity by the customer so they may be returned as part of the query data sent to Google Audience Partner API. If a row contains a NULL value, it will be automatically filtered out by the connector and will be shown in the error logs.

Amperity Column

Google API Key

Description

User ID

user-id

A list of customer IDs provided to Amperity by the customer. For this key, the connector:

  • Trims leading and trailing whitespace

  • Optional. Hashes data as SHA-256