Google Ads - Customer Match Upload

On this page

Overview

This connector uses the Google Ads Customer Match lists.

It may take up to several hours for the list to be populated with members.

For privacy purposes, the user list size will show as zero until the list has at least 1,000 members. After that, the size will be rounded to the two most significant digits.

Audiences uploaded via this mechanism to Google Ads can only use audiences within:

• Search

• YouTube

• GMail (if the email is an @gmail.com email address)

Customer match lists cannot be used within Google Display Network.

Pre-requisites for using Google Customer Match in Wondaris

• You must be eligible and already be allow-listed to use this connector - for more info on eligibility and to get whitelisted, please see the information here.

• You need to link your ad account to Wondaris Partner ID. Follow the below instructions:
  ^{(reference: https://support.google.com/google-ads/answer/12504105)}

  • Log into your Google Ads account

  • From your account, navigate to Tools → Data manager in the left menu

  • Click Connect Product

    Open

    

  • Select Wondaris from the dropdown menu and Authorise

    Open

    

  • Select Audiences in Use case

    Open

    

  • Click Done

Available Fields

The following fields are currently supported (and auto-mapped) by Wondaris. Any newly added fields that are added can be mapped manually when creating an activation.

• Email (hashed)

• Mobile Device ID

• Phone Number (hashed)

• First Name (hashed)

• Last Name (hashed)

• Country Code

• Zip Code

• Consent for Ad User Data

• Consent for Ad Personalisation

For formatting information visit https://support.google.com/google-ads/answer/7659867

User choice and control

All customer information is hashed before it reaches Google. No PII is shared with Google.

Google users can control the ads they see on Google services, including Customer Match ads, in their Google Ads Settings.

Consent Signal Requirements

Google requires consent from users in the EEA before activating audiences into Google Ads.

The Google Ads Destination includes option field mappings for Consent for Ad User Data and Consent for Ad Personalisation.

The following video shows how to use these within your Google Ads Activation if required.

Open

More info

For more information please see: https://support.google.com/google-ads/answer/6379332

For more information on eligibility & to request whitelisting, please see: https://support.google.com/adspolicy/answer/6299717

Problem Solving / FAQ

My Google Ads Destination activations are failing with the message “Unable to complete activation execution - failing: Error: Error when push data to Google Ads“?

This is a fairly generic error message from Google Ads, however an important inclusion to note is that if this has occurred, but no updates have been made, then this could be due to a Google Ads API update - take a look at the release notes and any linked migration how-to guides.

When I update my destination settings it does not update the activation?

We store the configuration settings for the destination WITHIN an activation separately to actual destination configuration settings. This is so that if you allow other users to override the default configuration for a destination within an activation, that overridden configuration is used.

The flip side to this is that if you update the default configuration settings for a destination that is used in an activation, you need to also update the activation.

To do this, simply go into a saved activation that uses that destination, change the destination to some other choice, move to the mapping phase, then change it back to the original.

You can check if your settings have been updated by checking on the destination configuration tab when completing the mapping during the activation workflow:

Open