Send data 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.
This topic describes the steps that are required to send customer data to Google Ads from Amperity:
Get details¶
The Google Ads destination requires the following configuration details:
The name of the custom audience to which Amperity will send data. Amperity will create the custom audience name if it does not already exist.
The membership duration for the custom audience. Membership duration defines for how long a name stays in the custom audience list. When the duration expires, the name is removed from the list. The default is 30 days. The maximum is 540 days.
The upload key type. The upload key type must be one of the following: “Contact Info”, “User ID”, or “Mobile ID”.
If the upload key type is “Mobile ID”, add the ID for the iOS or Android application from which the data will be collected.
Caution
A list can be uploaded with only one type of data–contact info, mobile device ID, or user ID–and once uploaded will not accept any other list ID types.
Authorize Amperity to send data to the customer’s Google Ads account.
Configure OAuth¶
OAuth is an open standard for access delegation, commonly used to grant websites or applications access to information on other websites.
To configure OAuth
From the Destinations tab, click Add Destination. The Add Destination dialog box opens.
From the Plugin drop-down, select Google Ads.
From the Credential drop-down, select Create a new credential. This opens the Create New Credential dialog box.
Generate an authorization link, and then visit the URL that was generated to complete the authorization process.
Log in to Google Ads at the generated URL using the customer’s credentials to allow access to the customer’s instance of Google Ads.
Tip
Send the URL to an individual who can provide the customer’s credentials, and then ask them to log into Google Ads on your behalf.
When complete, you will be redirected to the Credentials page in Amperity.
Verify the credential is on the page, and then return to the Destinations tab.
Add destination¶
Configure Amperity to send data to Google Ads using the Google Ads API.
Warning
Amperity must be authorized to send data to the customer’s Google Ads account prior to configuring the destination.
To add a destination
From the Destinations tab, click Add Destination. This opens the Add Destination dialog box.
Enter the name of the destination and a description. For example: “Google Ads” and “This sends customer data to Google Ads”.
From the Plugin drop-down, select Google Ads.
From the Credentials drop-down, select the “the OAuth credential you created for your Google Ads account” credential type. Select the OAuth credential you created for your Google Ads account, after which configuration settings are added automatically.
Under Google Ads Settings, enter the customer ID.
Select Allow business users to use this destination.
This allows users who have been assigned to the Amp360 User and/or AmpIQ User policies to use this destination with orchestrations and/or campaigns.
Select Allow business users with limited PII access to send data.
This allows users who have been assigned to the Restrict PII Access policy option to use this destination with orchestrations and/or campaigns.
Click Save.
Add data template¶
A data template defines how columns in Amperity data structures are sent to downstream workflows. A data template is part of the configuration for sending query and segment results from Amperity to an external location.
You have two options for setting up data templates for Google Ads:
for campaigns¶
You can configure Amperity to send campaigns to Google Ads. These results are sent from the Campaigns tab. Results default to a list of email addresses, but you may configure a campaign to send additional attributes to Google Ads.
To add a data template for campaigns
From the Destinations tab, open the menu for a destination that is configured for Google Ads, and then select Add data template.
This opens the Add Data Template dialog box.
Enter the name of the data template and a description. For example: “Google Ads audiences” and “Send audiences to Google Ads.”
Enable the Allow customers to use this data template option, and then enable the Make available to campaigns option. This allows users to send campaign results from Amperity to Google Ads.
Verify all template settings and make any required updates.
Click Save.
for orchestrations¶
You can configure Amperity to send query results to Google Ads. These results are sent using an orchestration.
To add a data template for orchestrations
From the Destinations tab, open the menu for a destination that is configured for Google Ads, and then select Add data template.
This opens the Add Data Template dialog box.
Enter the name of the data template and a description. For example: “Google Ads customer profiles” and “Send email addresses and customer profiles to Google Ads.”
Enable the Allow customers to use this data template option. This allows users to build queries, and then configure orchestrations that send results from Amperity to a configured destination.
Optional. Enable the Allow orchestrations from customers with limited PII access option. This allows users who have been assigned the Restrict PII Access policy option to send results from Amperity.
Verify all template settings and make any required updates.
Click Save.
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:
|