> 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.md).

# Google

The five Google connectors, which Google product each one reaches, and the consent rules common to all of them.

Google is the only vendor mediarithmics reaches across more than one kind of platform: a buying platform (Google Ads), an ad server and exchange (Google Ad Manager), a DSP (DV360), and a cloud data warehouse (BigQuery, in [Sources](/connectors/sources/google-bigquery.md)). This page is the map.

## Which connector to use

<table data-search="false"><thead><tr><th width="290">Connector</th><th width="200">Reaches</th><th></th></tr></thead><tbody><tr><td><a href="/connectors/destinations/google/ads-customer-match.md"><strong>Ads - Customer Match</strong></a></td><td>Google Ads</td><td>Server-side, offline hashed data. Reaches identified visitors, and is the only route that can <strong>exclude</strong> existing customers from acquisition campaigns.</td></tr><tr><td><a href="/connectors/destinations/google/ads-pixel.md"><strong>Ads - Pixel</strong></a></td><td>Google Ads</td><td>Client-side. Reaches visitors who are not logged in. The audience grows only from setup onwards.</td></tr><tr><td><a href="/connectors/destinations/google/ad-manager-audience-api.md"><strong>Ad Manager - Audience API</strong></a></td><td>Ad Exchange, Ad Manager, DV360 Advertiser, DV360 Partner</td><td>The Google Audience API partner connector, shown as <strong>DDP connector</strong> in the interface. The broadest reach of the five.</td></tr><tr><td><a href="/connectors/destinations/google/ad-manager-batch-upload.md"><strong>Ad Manager - Batch Upload</strong></a></td><td>Google Ad Manager</td><td>File upload. The only route that carries <strong>PPIDs</strong>.</td></tr><tr><td><a href="/connectors/destinations/google/dv360.md"><strong>DV360</strong></a></td><td>YouTube, Gmail, and Search when shared to Google Ads</td><td>DV360 Customer Match, server-side.</td></tr></tbody></table>

{% hint style="info" %}
For Google Ads, setting up **both** Customer Match and the Pixel is the recommendation - they reach different people.
{% endhint %}

## What each connector sends

<table data-search="false"><thead><tr><th width="290">Connector</th><th width="180">Type</th><th></th></tr></thead><tbody><tr><td><a href="/connectors/destinations/google/ads-customer-match.md">Ads - Customer Match</a></td><td>Server-side</td><td>Mobile IDs, Hashed emails (SHA-256), Hashed phone numbers (SHA-256), Profile data</td></tr><tr><td><a href="/connectors/destinations/google/ads-pixel.md">Ads - Pixel</a></td><td>Client-side (pixel)</td><td>None</td></tr><tr><td><a href="/connectors/destinations/google/ad-manager-audience-api.md">Ad Manager - Audience API</a></td><td>Server-side</td><td>Cookies, Mobile IDs, TV IDs (Android, Apple, Amazon, Roku)</td></tr><tr><td><a href="/connectors/destinations/google/ad-manager-batch-upload.md">Ad Manager - Batch Upload</a></td><td>Server-side</td><td>Mobile and TV advertising IDs, network IDs, PPIDs, user account IDs</td></tr><tr><td><a href="/connectors/destinations/google/dv360.md">DV360</a></td><td>Server-side</td><td>Mobile IDs, Hashed emails (SHA-256), Profile data</td></tr></tbody></table>

## Consent applies to all of them

Since March 2024 Google requires a confirmation of user consent status whenever audiences are shared to its advertising products. What you must set depends on your datamart's region **and** on the connector - including one case where the fields must be left **empty**.

<a href="/connectors/destinations/google/consent-management.md" class="button primary">Read the consent rules</a>

## Beyond advertising

**Google BigQuery** is not an advertising connector. It connects a BigQuery project to mediarithmics for data warehouse synchronisation, and lives under [Sources](/connectors/sources/google-bigquery.md).

## Partner documentation

Google Ads documents its own platform at <https://support.google.com/google-ads/>. 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.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.