> For the complete documentation index, see [llms.txt](https://docs.mediarithmics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mediarithmics.io/connectors/destinations/google/dv360.md).

# DV360

Send offline hashed data to Google DV360 Customer Match, for YouTube, Gmail and Search.

Google DV360 Customer Match sends offline hashed data from mediarithmics to Google DV360, for activation across Google owned and operated inventory - YouTube, Gmail - and, when shared to Google Ads, on Search.

<table data-search="false"><thead><tr><th width="220">Connection</th><th></th></tr></thead><tbody><tr><td><strong>Type</strong></td><td>Server-side</td></tr><tr><td><strong>Category</strong></td><td><a href="/connectors/partner-types/dsp.md">DSP</a></td></tr><tr><td><strong>Identifiers sent</strong></td><td>Mobile IDs, Hashed emails (SHA-256), Profile data</td></tr><tr><td><strong>Authentication</strong></td><td>Google OAuth on an individual account holding admin roles</td></tr></tbody></table>

## Description

### What you can do with this connector

Once the feed is connected and synchronised, your mediarithmics audiences can be activated everywhere Customer Match is supported - **YouTube**, **Google Search** and **Gmail**. On YouTube you can:

* target or exclude existing customers in YouTube campaigns;
* reactivate users or promote new offers through video ads.

<a href="https://support.google.com/displayvideo/answer/9539301?hl=en" class="button secondary" data-icon="arrow-up-right-from-square">YouTube audience creation</a>

<a href="https://support.google.com/displayvideo/answer/6401903?hl=en" class="button secondary" data-icon="arrow-up-right-from-square">Supported formats and partner site limitations</a>

### Which identifiers are sent

* **Mobile IDs**
* **Email identifiers** - hashed email in SHA-256
* **Profile data** - postal code, gender, age, hashed email in SHA-256, if you store it in mediarithmics

The industry match rate varies from **30% to 70%** depending on which IDs you send. The **email hash** has the highest match rate.

## Connector setup

### Prerequisites

* **Whitelisting is mandatory.** The conditions are in [Google's Customer Match policy](https://support.google.com/adspolicy/answer/6299717).
* **Admin rights** on the Google account performing the authorisation.

{% hint style="warning" %}
**The whitelisting is tied to one individual Google account on your side.** That account must hold admin roles on the advertising accounts you want to push data to. If it is deleted - when someone leaves the company, for instance - or loses its admin roles, Google stops allowing the data push.
{% endhint %}

### Authentication

Authorise mediarithmics by opening [this link](https://accounts.google.com/o/oauth2/v2/auth?redirect_uri=https%3A%2F%2Fnavigator.mediarithmics.com\&prompt=consent\&response_type=code\&client_id=473116266037-ja9bid4u8t7orbv6slafsa3kbp2c55ia.apps.googleusercontent.com\&scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fdisplay-video\&access_type=offline).

If the application is blocked, check that you have Google admin rights, and ask your IT department to unblock the app.

Once you have granted the authorisation you are redirected to Navigator, and the URL carries a `code` parameter. Send the URL to your CSM - the client authorisation code is needed for the next step.

{% hint style="danger" %}
If you are **not logged in** to `navigator.mediarithmics.com`, you are redirected to `auth.mediarithmics.com` and the authorisation code is lost from the request. Copy the URL quickly, or log in first.
{% endhint %}

### Setup steps

{% stepper %}
{% step %}
**Log in to the mediarithmics platform first**, so the redirect does not drop the code.
{% endstep %}

{% step %}
**Open the authorisation link with a Google account holding admin roles on the target advertising accounts, and grant consent.**
{% endstep %}

{% step %}
**Copy the redirect URL and send it to your CSM.**
{% endstep %}

{% step %}
**Select the Google DV360 Customer Match connector and fill in its configuration.**

<table data-search="false"><thead><tr><th width="360">Field</th><th></th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>Identifies the feed. Used inside the platform only; not visible on the external system.</td></tr><tr><td><strong>Google DV360 Advertiser account id</strong></td><td>The DV360 advertiser to synchronise the audience to. Requires the prior authorisation.</td></tr><tr><td><strong>Mobile App Id</strong></td><td>Identifies the mobile application the data was collected from. On iOS, the 9-digit string at the end of the App Store URL - <code>476943146</code>. On Android, the package name - <code>com.labpixies.colordrips</code>. <strong>Required</strong> when creating Device Customer Match audiences to upload mobile advertising IDs.</td></tr><tr><td><strong>Consent status for the use of ad user data</strong></td><td><code>GRANTED</code>, <code>DENIED</code> or <code>UNSPECIFIED</code>. See <a href="/connectors/destinations/google/consent-management.md">Google - Consent management</a>.</td></tr><tr><td><strong>Consent status for the use of ad personalization data</strong></td><td><code>GRANTED</code>, <code>DENIED</code> or <code>UNSPECIFIED</code>. See <a href="/connectors/destinations/google/consent-management.md">Google - Consent management</a>.</td></tr></tbody></table>
{% endstep %}

{% step %}
**Set the advanced fields if you need them.**

<table data-search="false"><thead><tr><th width="360">Field</th><th></th></tr></thead><tbody><tr><td><strong>DV360 audience ID</strong></td><td>An existing DV360 advertiser user list to enrich.</td></tr><tr><td><strong>DV360 Audience Display Name</strong></td><td>Forces the audience name. Defaults to the segment name.</td></tr><tr><td><strong>Type of Audience Data Source</strong></td><td><code>unspecified</code>, <code>first_party</code> or <code>third_party</code>. Defaults to unspecified.</td></tr><tr><td><strong>DV360 audience membership life span</strong></td><td>How many days an entry stays in the audience. If the audience expires, greater than 0 and up to 540. With no expiration, the default is <code>10000</code>.</td></tr></tbody></table>
{% endstep %}
{% endstepper %}

Creating and activating the feed on a segment is covered in the **Audience & Activation** section, under *Activate your audiences › Send your first-party data to a destination*.

## FAQ

#### The authorisation redirect lost my code. What happened?

You were not logged in to the mediarithmics platform, so Google redirected through `auth.mediarithmics.com` and the code was dropped. Log in first, then repeat.

#### Our data push stopped working. Nothing changed on our side.

Check the Google account used for the whitelisting. If it was deleted, or lost its admin roles on the advertising accounts, Google blocks the push. It is tied to one individual account.

#### The Google authorisation app is blocked.

Confirm you have Google admin rights, then ask your IT department to unblock the app.

## Partner documentation

Display & Video 360 documents its own platform at <https://support.google.com/displayvideo/>. Use it for anything that happens on the partner side of this connector: account setup, the fields the partner expects, and its own limits.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mediarithmics.io/connectors/destinations/google/dv360.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.