> 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/ads-customer-match.md).

# Ads - Customer Match

Send offline hashed data to Google Ads Customer Match, for targeting or for exclusion.

Google Ads Customer Match sends offline hashed data from mediarithmics to Google Ads. Being server-side, it pushes the audience every time the segment is updated.

<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), Hashed phone numbers (SHA-256), Profile data</td></tr><tr><td><strong>Authentication</strong></td><td>Authorisation code generated in Google Ads, passed to your account manager</td></tr></tbody></table>

## Description

### What you can do with this connector

* Retarget your identified - logged-in - visitors on Google Ads.
* **Exclude** your subscribers or existing customers from acquisition campaigns.

### Which identifiers are sent

* **Mobile IDs**
* **Email identifiers** - hashed email in SHA-256
* **Phone numbers** - hashed phone number 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.

Google is reached by several connectors and they behave differently - [the comparison is on the Google page](/connectors/destinations/google.md).

## Connector setup

### Prerequisites

* **Whitelisting is mandatory.** The conditions are in [Google's Customer Match policy](https://support.google.com/adspolicy/answer/6299717).
* Your **Google Ads account ID**, given to your account manager.

{% hint style="warning" %}
**Google Ads accounts are hierarchical.** To send audiences to an account that is **not** a master account, mediarithmics needs the ID of the **parent (master) account** as well as the ID of the destination sub-account. Without it, Google rejects any attempt to create a segment in the sub-account.
{% endhint %}

### Authentication

Generate an authorisation code in Google Ads and transfer it to your mediarithmics account manager.

{% hint style="danger" %}
**The authorisation code is valid for 15 minutes.** Schedule a call with your mediarithmics account manager and your Google Ads admin so it is done in one sitting.
{% endhint %}

### Setup steps

{% stepper %}
{% step %}
**Confirm you meet Google's whitelisting conditions.**
{% endstep %}

{% step %}
**Generate the authorisation code with your Google Ads admin, and pass it to your account manager within 15 minutes.**

Give them your Google Ads account ID at the same time - and the master account ID if the destination is a sub-account.
{% endstep %}

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

<table data-search="false"><thead><tr><th width="380">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 Ads account id</strong></td><td>The account to synchronise the audience to. Requires the prior authorisation. Format <code>123-456-7890</code>.</td></tr><tr><td><strong>Compartments to use</strong></td><td>The compartments the CRM data comes from.</td></tr><tr><td><strong>Upload key Type</strong></td><td>The type of identifiers used to synchronise the audience.</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="380">Field</th><th></th></tr></thead><tbody><tr><td><strong>AdWords user list ID</strong></td><td>An existing Google Ads user list to enrich.</td></tr><tr><td><strong>AdWords user list integration code</strong></td><td>A specific integration code. Unset, the feed uses the standard format <code>datamart_id:segment_id</code>.</td></tr><tr><td><strong>AdWords user list membership life span</strong></td><td>How many days a user's cookie stays in the Google Ads user list after its most recent addition. Between 0 and 540 inclusive, or <code>10000</code> for no expiration. Defaults to <code>10000</code>.</td></tr><tr><td><strong>AdWords user list eligible for search</strong></td><td>Marks the list eligible for the Google Search Network. Defaults to <code>false</code>.</td></tr><tr><td><strong>Data source type</strong></td><td>Defaults to <code>FIRST_PARTY</code>.</td></tr><tr><td><strong>AppId</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 a CrmBasedUserList to upload mobile advertising IDs.</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

#### Google rejects the segment creation on my sub-account. Why?

Because mediarithmics also needs the **parent (master) account ID**. Without it Google refuses the creation in a sub-account.

#### The authorisation code stopped working.

It expires after 15 minutes. Regenerate it with your Google Ads admin and pass it on immediately.

#### How do I get the best match rate?

Send the hashed email - it is the identifier with the highest match rate. Adding mobile IDs and profile data raises it further.

## 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/ads-customer-match.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.