Google Display & Video Customer Match Connector Setup Guide

[#1]

This article describes how to set up the Google Display & Video 360 Customer Match connector.

This article can be found on the new Tealium Docs web site: Google Display & Video 360 Customer Match Connector Setup Guide. In the future, this article will be archived.

In this article:

• Connector Actions
• Requirements
• Batch Limits
• Configure Settings
• Action Settings — Parameters and Options
• User Identifiers
• Action — Add to Customer Match List
• Action — Remove from Customer Match List

Connector Actions

ACTION NAME	AUDIENCESTREAM	EVENTSTREAM
Add to Customer Match List	✓	✓
Remove from Customer Match List	✓	✓

Requirements

Before configuring this connector, add Tealium as a linked account in the Google DV360 UI (Tools and Settings > Linked Accounts). For more information, see the Google article on sharing audience lists.

Batch Limits

This connector uses batched requests to support high-volume data transfers to the vendor. Requests are queued until one of the following three thresholds is met:

• Max number of requests: 33000
• Max time since oldest request: 60 minutes
• Max size of requests: 40 MB

Configure Settings

Navigate to the Connector Marketplace and add a new connector. For general instructions on how to add a connector, see the About Connectors article.

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. The account to which Tealium is linked in the DV360 UI (Tools and Settings > Linked Accounts).
• Target Product
  • Required. The target product of the linked account.

Click Done when you are finished configuring the connector.

Action Settings — Parameters and Options

Click Continue to configure the connector actions. Enter in a name for the action and then select the action type from the drop-down menu.

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

User Identifiers

Each action requires a user identifier and these values must be normalized and hashed using SHA-256. Each user identifier value mapped must meet the following requirements:

• Lower-case
• Whitespace trimmed from the beginning 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 User List type you select determines the type of user identifier. The User List type can be one of the following:

• CONTACT_INFO
• 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 for user’s address in ISO-3166-1 alpha-2 format. Address Info: First Name (already SHA256 hashed) - Provide first name, with whitespace trimmed, that has been lowercased and SHA256 hashed. Address Info: First Name (apply SHA256 hash) - Provide a plain text first name. The connector hashes this value using SHA256 hash. Address Info: Last Name (already SHA256 hashed) - Provide last name, with whitespace trimmed, that has been lowercased and SHA256 hashed. Address Info: Last Name (apply SHA256 hash) - Provide a plain text last name. The connector hashes 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, with whitespace trimmed, that has been lowercased and SHA256 hashed. Email Address (apply SHA256 hash) - Provide a plain text email address. The connector hashes this value using SHA256 hash. Phone Number (already SHA256 hashed) - Provide a phone number, with whitespace trimmed, that has been SHA256 hashed. Phone Number (apply SHA256 hash) - Provide a plain text phone number. The connector hashes this value using SHA256 hash.
MOBILE_ADVERTISING_ID	Mobile ID (Required) - Mobile device ID (advertising ID/IDFA).

Action — Add to Customer Match List

Parameters

PARAMETER	DESCRIPTION
Customer Match List	Select a Customer Match List. Only lists created via the Tealium connector are available.

Action — Remove from Customer Match List

Parameters

PARAMETER	DESCRIPTION
Customer Match List	Select a Customer Match List. Only lists created via the Tealium connector are available.