Send data to Google Ads¶
Google Ads appear within the Google advertising network to web users. Use ads to promote your brand, help sell products or services, raise awareness, and increase traffic to your website or stores.
What is Google Customer Match?
Google Customer Match is a unified ad creation tool that you can use to create and publish search, display, and video ads across the Google-owned paid media ecosystem. For example:
Use Discovery campaigns to reach customers in the Promotions and Social tabs in Gmail .
Use Google Ads to configure campaign types for search, display, video, app, local, hotel, call, smart, goal-based, and shopping.
Run ads within search results on Google.com .
Run ads within the Shopping tab on Google.com .
Note
This destination uses the Google Audience Partner 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:
![]() |
Configuration details for Google Ads. The name of the product to which Amperity will send data: “Google Ads”. The customer ID associated with your Google Customer Match account, along with the customer ID associated with the “Google Ads” account. Note The customer ID must be 10 digits and may not contain dashes. A refresh token that is generated from the OAuth process that authorizes Amperity to send data to the selected product. This must be a Google account with permission to access the configured customer ID and product within Google. Important OAuth for “Google Ads” must be completed within Google prior to configuring OAuth in Amperity. |
![]() |
The name of an audience in Google Ads. The description is optional. If the audience does not exist, Amperity will create it. The membership duration defines the length of time (in days) at which individual audience members will belong to the segment. The membership duration must be between 0-540 (inclusive) or 10000 for an unlimited duration. Tip Set this value to “0” to remove all audience members. The Upload key type must be set to one of Contact Info, User ID, or Mobile ID. If the Upload key type is set to “Mobile ID”, use the Mobile app ID setting to provide the ID for the iOS or Android app from which the mobile ID was collected. |
Configure OAuth¶
OAuth is an open standard for access delegation, commonly used to grant websites or applications access to information on other websites.
Important
OAuth for “Google Ads” must be completed within Google prior to configuring OAuth in Amperity.
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 customer data directly to Google Ads.
Warning
Amperity must be authorized to send data to your Google Ads account prior to configuring the destination.
To add a destination
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.
To add a data template
![]() |
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. ![]() 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. |
![]() |
Verify business user access to queries and orchestrations and access to segments and campaigns. A business user may also have restricted access to PII, which prevents them from viewing and sending customer profile data. ![]() If business user access was not configured as part of the destination, you may configure access from the data template. Important To allow business users to use this destination with campaigns, you must enable the Make available to campaigns option. This allows users to send campaign results from Amperity to Google Ads. If you enable this option, the data extension settings require using campaign name and group name template variables to associate the name of the data extension to your campaign. |
![]() |
Verify all configuration settings. ![]() Note When the customer ID setting was are not configured as part of the destination, you must configure it as part of the data template before making this destination available to campaigns. |
![]() |
Review all settings, and then click Save. ![]() After you have saved the data template, and depending on how you configured it, business users can send query results and/or send campaigns to Google Ads. |
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:
|