This article describes how to set up the Google Ads Customer Match (Customer-Provided Credentials and Tealium-Provided Credentials) connectors.

In this article:

Overview

This connector replaces the deprecated Google AdWords Customer Match connectors.

API Information

This connector uses the following vendor API:

Connector Actions

Action Name AudienceStream EventStream
Add User to Remarketing List
Remove User from Remarketing List

Configure Settings

Go to the Connector Marketplace and add a new connector. Read the Connector Overview article for general instructions on how to add a connector.

When you add this connector you are prompted to accept the vendor's data platform policy.

After adding the connector, configure the following settings:

  • Customer ID
    • Required
    • Provide Ads account customer ID to manage.
  • Manager Customer ID
    • Optional
    • If you are accessing a client customer, the Manager Customer ID must be set.
  • Developer Token
    • Required
    • Provide the API developer token that has been approved by Google to make production volume API requests.
    • Obtaining and approving a developer token is a multi-step process that you will need to own and manage. To get started, see Obtain Your Developer Token.

Action Settings - Parameters and Options

Click Next or go to the Actions tab. This is where you configure connector actions.

This section describes how to set up parameters and options for each action.

User Identifiers

Each action requires a user identifier and the vendor requires these values to be normalized and hashed using SHA-256. Each user identifier value mapped is expected to be:

  • Lower-case
  • Trimmed whitespace from the front and end of the text
  • Hashed with SHA-256

You can map attributes that are already normalized and hashed or you can allow the connector to normalize and hash them for you. Select the appropriate mapping for your scenario.

The required user identifier is based on the user list type selected. The user list types are:

  • CONTACT_INFO
  • CRM_ID
  • MOBILE_ADVERTISING_ID

The following user identifier fields are supported:

User Identifier Field Description

CONTACT_INFO

  • Provide Hashed Email, Hashed Phone Number or Address Info.
  • Address Info: Country Code - 2-letter country code in ISO-3166-1 alpha-2 of the user's address.
  • Address Info: First Name (already SHA256 hashed) - Provide first name which has been already whitespace trimmed, lowercased and SHA256 hashed.
  • Address Info: First Name (apply SHA256 hash) - Provide a plain text first name and the connector will hash this value using SHA256 hash.
  • Address Info: Last Name (already SHA256 hashed) - Provide last name which has been already whitespace trimmed, lowercased and SHA256 hashed.
  • Address Info: Last Name (apply SHA256 hash) - Provide a plain text last name and the connector will hash this value using SHA256 hash.
  • Address Info: Postal Code - Postal code of the user's address.
  • Email Address (already SHA256 hashed) - Provide an email address which has been already whitespace trimmed, lowercased and SHA256 hashed.
  • Email Address (apply SHA256 hash) - Provide a plain text email address and the connector will hash this value using SHA256 hash.
  • Phone Number (already SHA256 hashed) - Provide a phone number which has been already whitespace trimmed, lowercased and SHA256 hashed.
  • Phone Number (apply SHA256 hash) - Provide a plain text phone number and the connector will hash this value using SHA256 hash.
 CRM_ID
  • User ID (Required) - Advertiser-assigned user ID for Customer Match upload.
 MOBILE_ADVERTISING_ID
  • Mobile ID (Required) - Mobile device ID (advertising ID/IDFA).

Action - Add User to Remarketing List

Parameters

Parameter Description
Remarketing List
User Identifier

Action - Remove User from Remarketing List

Parameters

Parameter Description
Remarketing List
User Identifiers
Public