Send data to Google Ads¶
Google Ads is search-based advertising that can be run across the Google advertising network and is shown to web users. Use search-based advertising 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 .
Send audiences to DV360, and then run video advertising campaigns in YouTube Ads or on web pages using any of the available placement options . DV360 supports advertiser and partner networks.
Use Amperity to build high-value and/or product affinity segments that are based on first-party data, and then configure Amperity to use the Google Customer Match destination to send those segments to Google Ads.
Once uploaded, Google Ads hashes each record, and then matches all records against hashed user accounts that already exist in Google Ads to identify segments that contain records that match the ones sent from Amperity.
Google Ads builds audience lists that are reachable across the Google-owned paid media ecosystem.
Use these audience lists for precision cross-selling, to reach and convert new customers, and to improve the retention rate for your most loyal customers.
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¶
Google Ads 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.
Use OAuth to configure Amperity to send customer data to Google Ads.
Important
OAuth for “Google Ads” must be completed within Google prior to configuring OAuth in Amperity.
To configure OAuth
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. ![]() Enter the name of the data template and a description. For example: “Google Ads” and “Send customer data to Google Ads.”. |
![]() |
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. |
Workflow actions¶
A workflow will occasionally show an error that describes what prevented a workflow from completing successfully. These first appear as alerts in the notifications pane. The alert describes the error, and then links to the Workflows tab.
Open the Workflows tab to review a list of workflow actions, choose an action to resolve the workflow error, and then follow the steps that are shown.
Cannot update audience¶
Amperity uses a refresh token that is generated from your Google Ads user account to access audiences that are associated with your Google Ads customer ID. The user for whom the refresh token is created must have permission to update audiences in the Google Ads account that is associated with the customer ID.
To resolve this error, verify that the user account can update audiences.
Open the Google Ads management console , and then sign in to your Google Ads account.
Verify that the user has permission to update audiences that are associated with the customer ID.
Return to the workflow action, and then click Resolve to retry this workflow.
Expired token¶
The token used with Google Ads has expired.
To resolve this error, refresh the token that is used with Google Ads.
Open the Google Ads management console , and then sign in to your Google Ads account.
Refresh the token that is associated with your Google Ads account.
Return to the workflow action, and then click Resolve to retry this workflow.
Incomplete account setup¶
Amperity cannot send data to an account in Google Ads that is not set up completely. For example, this error can occur when an account is an a “DRAFT” state in Google Ads.
To resolve this error, verify that your Google Ads account is set up correctly.
Open the Google Ads management console , and then sign in to your Google Ads account.
Verify the current state of your account. Complete any steps that are required to set up your Google Ads account.
Return to the workflow action, and then click Resolve to retry this workflow.
Invalid credentials¶
The credentials that are defined in Amperity are invalid.
To resolve this error, verify that the credentials required by this workflow are valid.
Open the Credentials page.
Review the details for the credentials used with this workflow. Update the credentials for Google Ads if required.
Return to the workflow action, and then click Resolve to retry this workflow.
Missing required field(s)¶
One (or more) required attributes are missing. Google Ads requires the following attributes for contact matching: firstname, lastname, email, phone, country, and zip.
For campaigns
To resolve this error, update the list of attributes to include all required fields.
Open the Campaigns page, and then open the segment used with this workflow.
Verify that all required attributes are associated with each recipient group that is being sent to Google Ads. Update the list of attributes if required.
Return to the workflow action, and then click Resolve to retry this workflow.
For orchestrations
To resolve this error, update the results of the query to include all required fields.
Open the Queries page, and then open the query used with this workflow.
Verify that all required attributes are included in the query results. Update the query if required.
Return to the workflow action, and then click Resolve to retry this workflow.
Two-factor authentication required¶
Google Ads requires two-factor authentication to be enabled.
To resolve this error, ensure that two-factor authentication is enabled for your Google Ads account.
Open the Google Ads management console , and then sign in to your Google Ads account.
Verify that two-factor authentication is enabled for your account.
Click on your username.
Click on Manage Account. Under Security enable the option for two-step verification.
Return to the workflow action, and then click Resolve to retry this workflow.
User cannot access audience¶
When the Google Ads user account that is associated with the Amperity workflow does not have permission to view, edit, and manage the linked client account, Amperity will be unable to complete the workflow.
To resolve this error, verify the permissions associated with the user account in Google Ads.
Open the Google Ads management console , and then sign in to your Google Ads account.
Verify that Google Ads user account that is associated with the Amperity workflow has permission to view, edit, and manage the linked client account.
Return to the workflow action, and then click Resolve to retry this workflow.
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 |
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 |
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 |
Google API Key |
Description |
---|---|---|
User ID |
user-id |
A list of customer IDs provided to Amperity by the customer. For this key, the connector:
|