> For the complete documentation index, see [llms.txt](https://docs.dinmo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dinmo.io/integrations/destination-platforms/google-ad-manager.md).

# Google Ad Manager

Sending data to Google Ad Manager: Step-by-Step Guide

## Supported Destination Services

DinMo supports the following destination services:

* [Export Segments (GAM Key/Values) via Firestore](/integrations/destination-platforms/google-ad-manager/export-segments-via-firestore.md)
* [Export Segments (GAM Audiences) via Batch Upload](/integrations/destination-platforms/google-ad-manager/export-segments-via-batch-upload.md)

Please select the corresponding option when setuping the destination, and refer to their dedicated documentation page for more information.

## Authentication to Google Ad Manager

Regardless of the selected destination service, DinMo will always connect to Google Ad Manager using OAuth2 authentication. Please ensure that the user who connects Google Ad Manager on DinMo has the required permissions on the target Google Ad Manager account.

You will need to specify the Network Code of your Google Ad Manager account.

*Note: If the Network Code you seek is not listed, it means that the user who connected DinMo to Google Ad Manager does not have the permissions for this account. Refer to this* [*Google Documentation*](https://support.google.com/admanager/answer/7674889?hl=en) *for more information about Network Code*

## Destination Configuration

Once authenticated, select the option that matches the service you want to use. Detailed configuration steps are provided in the links listed above.


---

# 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.dinmo.io/integrations/destination-platforms/google-ad-manager.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.