Send campaigns to Google Ads¶
Google Ads appear within the Google advertising network to web users. Advertisers pay to display brief advertisements, service offerings, product listings, and so on.
Note
This destination uses the Google Ads API .
Changes to audiences are not immediately available in Google Ads. 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 Ads. This access may expire or be removed periodically, depending on how OAuth is managed at Google Ads. If Amperity is unable to send data to Google Ads ask your DataGrid Operator to reauthorize access to Google Ads.
Note
Ask your DataGrid Operator or your Amperity representative to configure Google Ads as a channel to which you can send campaigns.
Build campaign¶
Use the campaign editor to build campaigns that send data to Google Ads. Add a segment, define exclusions and sub-audiences, and then configure Amperity to send campaign data to Google Ads.
To build a campaign
From the Campaigns tab, click Create Campaign. This opens the New Campaign page.
Give your campaign a name.
Choose the segment that represents the audience to use for this campaign.
Optional. Choose a segment that contains a list of customers to exclude from this campaign.
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.
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 Ads.
Click Edit attributes to review the attributes that Amperity will send to Google Ads.
Google Ads 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 Ads. When you open the Edit attributes page for Google Ads, it will be similar to:
Note
The Merged_Customers table is the default table from which data is sent to Google 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.
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.)
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 Ads API Matching¶
Google Ads 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 |
For this key, the connector:
|
|
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:
|
Last Name |
lastname |
For this key, the connector:
|
First Name |
firstname |
For this key, the connector:
|
Zip Code |
zip |
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 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:
|
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 Ads. 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:
|