---
title: Google Display & Video 360 Customer Match Connector Setup Guide
description: This article describes how to set up the Google Display & Video 360 Customer Match connector.
url: https://docs.tealium.com/server-side-connectors/google-dv-360-customer-match-connector/
---
## API Information

This connector uses the following vendor API:

* API Name: Google Audience Partner API
* API Version: v2
* API Endpoint: `https://audiencepartner.googleapis.com/v2`
* Documentation: [Google Audience Partner API: Customer Match audience](https://support.google.com/displayvideo/answer/9539301?hl=en)

## 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](https://support.google.com/displayvideo/answer/9649053?hl=en).

## Configuration

Navigate to the Connector Marketplace and add a new connector. For general instructions on how to add a connector, see [About Connectors](https://docs.tealium.com/manage-connectors/).


<blockquote>
When you add this connector, you are prompted to accept the vendor's data platform policy.
</blockquote>


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.

### Create customer match list

To create a customer match list, click **Create Customer Match List** and enter the following information:

| **Parameter** | **Description** |
| --- | --- |
| List Name | (Required) Customer match list name. |
| List Type | (Required) The List Type. This affects the type of user identification information to be used with this list:<ul><li>Contact Info - members are matched from customer info such as email address, phone number, or physical address.</li><li>Mobile Advertising - members are matched from mobile advertising IDs.</li></ul> |
| App ID | Required for Mobile Advertising list types. A string that uniquely identifies the mobile application from which the data was collected. |
|  List Membership Lifespan | (Optional) The number of days a user stays on the list since their most recent addition to the list. Number must be between `0` and `540`. The default lifespan is 540 days. |
| List Description | (Optional) List description. |

## Actions

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

### 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

Either map attributes that are already normalized and hashed or 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` |  <ul><li>Provide Hashed Email, Hashed Phone Number, or Address Info.</li><li>**Address Info: Country Code** - 2-letter country code for user's address in ISO 3166-1 alpha-2 format.</li><li>**Address Info: First Name (already SHA256 hashed)** - Provide first name, with whitespace trimmed, that has been lowercased and SHA256 hashed.</li><li>**Address Info: First Name (apply SHA256 hash)** - Provide a plain text first name. The connector hashes this value using SHA256 hash.</li><li>**Address Info: Last Name (already SHA256 hashed)** - Provide last name, with whitespace trimmed, that has been lowercased and SHA256 hashed.</li><li>**Address Info: Last Name (apply SHA256 hash)** - Provide a plain text last name. The connector hashes this value using SHA256 hash.</li><li>**Address Info: Postal Code** - Postal code of the user's address.</li><li>**Email Address (already SHA256 hashed)** - Provide an email address, with whitespace trimmed, that has been lowercased and SHA256 hashed.</li><li>**Email Address (apply SHA256 hash)** - Provide a plain text email address. The connector hashes this value using SHA256 hash.</li><li>**Phone Number (already SHA256 hashed)** - Provide a phone number, with whitespace trimmed, that has been SHA256 hashed.</li><li>**Phone Number (apply SHA256 hash)** - Provide a plain text phone number. The connector hashes this value using SHA256 hash.</li></ul> |
|`MOBILE_ADVERTISING_ID`|  <ul><li>**Mobile ID** (Required) - Mobile device ID (advertising ID/IDFA).</li></ul> |

### Add to Customer Match List (multiple identifiers)

#### API Information

This connector uses the following vendor API:

* API Name: Google Data Manager API
* API Version: v1
* API Endpoint: `https://datamanager.googleapis.com`
* Documentation: [Google Data Manager API](https://developers.google.com/data-manager/api/reference/rest)

#### Batch Limits

This action uses batched requests to support high-volume data transfers to the vendor. For more information, see [Batched Actions](https://docs.tealium.com/batched-actions/). Requests are queued until one of the following thresholds is met or the profile is published:

* Max number of requests: 66,000
* 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 through the Tealium connector are available. To create a customer match list, see [Create customer match list](#create-customer-match-list). |
| User Identifier | The user identifier to match. For supported fields, see [User Identifiers](#user-identifiers). |

##### Consent

When using the **Add Visitor to Customer Match List** action, the connector sends the value of `GRANTED` for `adUserData` and `adPersonalization` consent by default. Use audience logic to prevent non-consented visitors from being added to lists. Use the **Remove from Customer Match List** action to remove non-consented visitors from lists.

### Remove from Customer Match List (multiple identifiers)

For mapping options, see [Add to Customer Match List (multiple identifiers)](#add-to-customer-match-list-multiple-identifiers).

### Add to Customer Match List (Deprecated)


<blockquote>
Tealium retrieves list statistics directly from Google DV 360, which may cause a difference between matches and the total volume of connector requests in this connector and the [Google DV 360 Customer Match connector insight](https://docs.tealium.com/connector-insights-google-dv360-customer-match/).
</blockquote>


#### API information

This connector uses the following vendor API:

* API Name: Google Ads API
* API Version: v18
* API Endpoint: `https://googleads.googleapis.com/`
* Documentation: [Google Ads API](https://developers.google.com/google-ads/api/docs/start)

#### Batch Limits

This action uses batched requests to support high-volume data transfers to the vendor. For more information, see [Batched Actions](https://docs.tealium.com/batched-actions/). Requests are queued until one of the following thresholds is met or the profile is published:

* Max number of requests: 100,000
* 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 through the Tealium connector are available. To create a customer match list, see [Create customer match list](#create-customer-match-list). |

##### Consent

When using the **Add Visitor to Customer Match List** action, the connector sends the value of `GRANTED` for `adUserData` and `adPersonalization` consent by default. Use audience logic to prevent non-consented visitors from being added to lists. Use the **Remove from Customer Match List** action to remove non-consented visitors from lists.

### Remove from Customer Match List (Deprecated)

#### API information

This connector uses the following vendor API:

* API Name: Google Ads API
* API Version: v18
* API Endpoint: `https://googleads.googleapis.com/`
* Documentation: [Google Ads API](https://developers.google.com/google-ads/api/docs/start)

#### Batch Limits

This action uses batched requests to support high-volume data transfers to the vendor. For more information, see [Batched Actions](https://docs.tealium.com/batched-actions/). Requests are queued until one of the following thresholds is met or the profile is published:

* Max number of requests: 100,000
* 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 through the Tealium connector are available. |