Google Ads Data Manager API

Fuel AI-powered personalization and support advanced measurement use-cases by connecting first-party audience and conversion data to Google Ads, Google Analytics, and Google Marketing Platform through a single unified API.

View Google Ads Data Manager API's documentation and status page.

Supported syncing

For more information about sync modes, refer to the sync modes docs.

Connect to Google Data Manager

Go to the Destinations overview page and click the Add destination button. Select Google Data Manager and click Continue. You can then authenticate Hightouch to Google Data Manager via OAuth.

Click Log in to Google Data Manager, log in with your Google Account, and click Allow. You should then see a success notification in the Hightouch UI.

Enter the Google Ads account ID you'd like to use with this destination. You can find this value in Google Ads, at the top-right corner with your account information. This should be a 10 digit value. Remove any dashes that may be present in Google Ads.

Sync configuration

Once you've set up your Google Data Manager destination and have a model to pull data from, you can set up your sync configuration to begin syncing data. Go to the Syncs overview page and click the Add sync button to begin. Then, select the relevant model and the Google Data Manager destination you want to sync to.

Syncing audience members

Hightouch lets you create and maintain customer match lists via the Google Data Manager API. It can take 6 to 48 hours for a list to be populated with members once Hightouch has sent the data to Google.

User list type

To begin, select which type of Customer Match User List you'd like to create or sync to. The available options are:

• CONTACT_INFO
• MOBILE_ADVERTISING_ID

Select an existing list or create a new one

You can create a new Customer match user list or use an existing one. When creating a new list, you can optionally enter a name. Otherwise, Hightouch defaults to the name of the associated model.

To use an existing list, enter the list's ID in the following format: products/{product}/customers/{customer_id}/userLists/{user_list_id}. Example: products/GOOGLE_ADS/customers/12345678/userLists/12345678

User identifiers

Select which columns in your model you'd like to send to Google Ads as user identifiers.

For user lists with the Contact Info type, you must select either hashed email addresses or hashed phone numbers. If you choose to sync addresses, all fields of the address are required.

For user lists with the Mobile Advertising ID type, the mobile advertising ID is required.

Handling PII and hashing

You can enable PII hashing if you wish for Hightouch to detect whether your data requires normalization and hashing based on the chosen record mapping. For example, if you select Email and the model column with the email data is unhashed, Hightouch hashes the value for you.

By default, Hightouch automatically detects if the following fields require hashing:

• Email
• Phone
• Given name
• Family name

EU user consent policy

If you are uploading data for users in the European Economic Area (EEA), you need to ensure you are passing the required consent signals to Google.

For each sync, you can specify the consent status for these types:

• ad_user_data: consent for sending user data to Google for advertising purposes
• ad_personalization: consent for ad personalization

Check out Google's support doc to learn more.

Syncing events

Hightouch supports syncing:

• Online events: Send event data as an additional data source for your tag conversions, to maximize ad interaction signals and strengthen your data and overall performance.
• Offline events: Send event data for offline conversions or enhanced conversions for leads.

When syncing conversion events, Hightouch treats any records added to your source as new events and sends them to Google Data Manager when your sync runs.

Field mapping

Select which columns in your model you'd like to sync as attributes of conversion events.

Google Data Manager requires the following fields for each event:

• Event timestamp (event_timestamp): The time the event occurred.
• Transaction ID (transaction_id): The unique identifier for the event.
• Event source (event_source): The source of the event. Required for offline events. Optional for online events. If specified for an online event, must be WEB.
• Ad identifiers (GCLID, GBRAID, or WBRAID) or user data (email, phone, or address): The event must have either an ad identifier or user data. Send both if you have both for the event.

The accepted values for event_source are:

• EVENT_SOURCE_UNSPECIFIED
• WEB
• APP
• IN_STORE
• PHONE
• OTHER

Additional user properties mappings include:

• Customer type
  • Accepted values: CUSTOMER_TYPE_UNSPECIFIED, NEW, RETURNING, REENGAGED
• Customer value bucket
  • Accepted values: CUSTOMER_VALUE_BUCKET_UNSPECIFIED, LOW, MEDIUM, HIGH

EU user consent policy

If you are uploading data for users in the European Economic Area (EEA), you need to ensure you are passing the required consent signals to Google.

For click conversions, call conversions and offline store conversions, you can specify the Google consent status for advertising purposes, by mapping these fields in the sync configuration:

• Ad user data consent (for the ad_user_data property)
• Ad personalization consent (for the ad_personalization property)

Tips and troubleshooting

Common errors

Live debugger

Hightouch provides complete visibility into the API calls made during each of your sync runs. We recommend reading our article on debugging tips and tricks to learn more.

Sync alerts

Hightouch can alert you of sync issues via Slack, PagerDuty, SMS, or email. For details, please visit our article on alerting.