Send audiences 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.
This topic describes the steps that are required to configure campaigns to send customer profiles to Google Ads.
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.
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 for help configuring Google Ads as a destination to which you can send campaigns for customer activation.
Build a segment¶
Use the Segment Editor to build any audience using a series of drop-downs and picklists.
As you define the attribute profile for an audience be sure to refresh segment insights to see how many customers match your audience and to see how much value they bring to your business.
When the segment is ready, activate it, and then use it use it in a campaign to send to your preferred destinations for customer activation.
Which attributes should you use?
You can use any attribute that is in your customer 360 database to define your audience.
When the list of customers who belong to this audience is sent to Google Ads as part of a campaign you will be required to choose specific attributes to send.
Google Ads supports the following attributes: customer profiles.
Build a 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
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:
|