> For the complete documentation index, see [llms.txt](https://docs.devtodev.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devtodev.com/3rd-party-sources/cohort-export/google-ads.md).

# Google Ads

Export devtodev cohorts to Google Ads to create remarketing audiences

## **Setup**

1. Go to: `Settings → 3rd Party Sources → Cohort Export`
2. Click the ✎ icon next to **Google Ads**
3. Fill in the fields:
   * **Account ID** – your 10-digit Google Ads Customer ID (format: `123-456-7890`)

{% hint style="info" %}
**Where to find Google Ads Customer ID**

* Log in to [Google Ads](https://ads.google.com/home/)
* Look in the top-right corner of the interface next to your account name

For help finding your Customer ID, [see Google documentation](https://support.google.com/google-ads/answer/1704344).
{% endhint %}

4. Click `Sign in with Google` to authorize.

<figure><img src="https://2105883905-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LnGcP_ZeRJ1ipj9O8dF%2Fuploads%2F2ByqZcY5OMp04aSsPgmy%2FScreenshot%202025-07-23%20at%2012.49.59.png?alt=media&amp;token=339a1eb9-71a2-408d-ab08-a91915f8c407" alt=""><figcaption></figcaption></figure>

*To disable the integration, turn off the toggle.*

### **User Identifier**

Google Ads cohort export in devtodev uses only the **Advertising ID** to match users:

* For Android: **GAID** (Google Advertising ID)
* For iOS: **IDFA** (Identifier for Advertisers)

Make sure the [SDK is integrated properly](/integration/integration-of-sdk-v2/sdk-integration.md) and **Advertising ID** is available in the user profile before the cohort is exported.&#x20;

## How to prepare cohorts

Check out the **Tuning section** to learn [how to export the cohorts](/reports-and-functionality/project-related-reports-and-fuctionality/tuning.md#cohort-export).&#x20;


---

# 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.devtodev.com/3rd-party-sources/cohort-export/google-ads.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.