Google Display & Video 360 Customer Match Connector Setup Guide

API Information

This connector uses the following vendor API:

• API Name: Google Audience Partner API
• API Version: v1
• API Endpoint: https://audiencepartner.googleapis.com/v1
• Documentation: Google Ads API: Get started with Customer Match

Connector Actions

Action Name	AudienceStream	EventStream
Add to Customer Match List	✓	✓
Remove from Customer Match List	✓	✓
Add to Customer Match List (multiple identifiers)	✓	✓
Remove from Customer Match List (multiple identifiers)	✓	✓

Requirements

Before configuring this connector, add Tealium as a linked account in your Google Display & Video 360 account.

For more information, see Google Display & Video 360: Sharing audience lists from external data management platforms or customer match uploader partners.

Configure Settings

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

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. Your Google DV360 Partner ID that is linked to Tealium. To find your Partner ID from the Google DV360 dashboard go to Partner Settings > Basic Details.
• 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 a name for the action and then select the action type from the drop-down menu.

The following sections describe how to set up parameters and options for each action.

We recommend that you use the single identifier actions unless you are passing multiple identifiers.

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
• Blank spaces 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 (single identifier)

Batch Limits

This action uses batched requests to support high-volume data transfers to the vendor. For more information, see Batched Actions. Requests are queued until one of the following thresholds is met or the profile is published:

• Max number of requests: 100000
• Max time since oldest request: 1440 minutes
• Max size of requests: 50 MB

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 (single identifier)

Batch Limits

This action uses batched requests to support high-volume data transfers to the vendor. For more information, see Batched Actions. Requests are queued until one of the following thresholds is met or the profile is published:

• Max number of requests: 100000
• Max time since oldest request: 1440 minutes
• Max size of requests: 50 MB

Parameters

Parameter	Description
Customer Match List	Select a Customer Match List. Only lists created via the Tealium connector are available.

Action — Add to Customer Match List (multiple identifiers)

Batch Limits

This action uses batched requests to support high-volume data transfers to the vendor. For more information, see Batched Actions. Requests are queued until one of the following thresholds is met or the profile is published:

• Max number of requests: 33000
• Max time since oldest request: 1440 minutes
• Max size of requests: 50 MB

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 (multiple identifiers)

Batch Limits

This action uses batched requests to support high-volume data transfers to the vendor. For more information, see Batched Actions. Requests are queued until one of the following thresholds is met or the profile is published:

• Max number of requests: 33000
• Max time since oldest request: 1440 minutes
• Max size of requests: 50 MB

Parameters

Parameter	Description
Customer Match List	Select a Customer Match List. Only lists created via the Tealium connector are available.