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

# Amazon Ads

The two ways to send audiences to Amazon Ads, and which one to pick.

Amazon Ads is built on three core products - **Amazon DSP**, **Amazon Sponsored Ads** and **Amazon Marketing Cloud (AMC)**. mediarithmics reaches it two ways, and they answer different questions.

## Which connector to use

<table data-search="false"><thead><tr><th width="300">Connector</th><th></th></tr></thead><tbody><tr><td><a href="/connectors/destinations/amazon-ads/data-manager.md"><strong>Data Manager</strong></a></td><td><strong>Data onboarding.</strong> Upload, structure and share your audiences centrally, then use them across Amazon DSP, Sponsored Ads and AMC. First-party audiences only, currently.</td></tr><tr><td><a href="/connectors/destinations/amazon-ads/dsp.md"><strong>DSP</strong></a></td><td><strong>Activation.</strong> Plan, buy and optimise programmatic media across Amazon and third-party sites.</td></tr></tbody></table>

Amazon Ads Data Manager is the **entry point** to the ecosystem: data uploaded there can be shared across all three products. The DSP connector activates directly against one advertiser account. If you want your data available for measurement in AMC as well as activation, start with Data Manager.

## What each connector sends

<table data-search="false"><thead><tr><th width="220">Connector</th><th width="150">Type</th><th></th></tr></thead><tbody><tr><td><a href="/connectors/destinations/amazon-ads/data-manager.md">Data Manager</a></td><td>Server-side</td><td>Emails, Profile data, Mobile IDs</td></tr><tr><td><a href="/connectors/destinations/amazon-ads/dsp.md">DSP</a></td><td>Server-side</td><td>Mobile IDs, Cookies</td></tr></tbody></table>

Both authenticate through Amazon's OAuth flow, but not in the same way: Data Manager is fully self-service from the platform, while the DSP connector needs an authorisation code passed to your account manager within 5 minutes.

## Consent applies to both of them

Amazon carries user consent status in a dedicated framework, the **Amazon Consent Signal**. Both connectors rely on it exclusively, and in the EEA and the UK a valid signal is required. Users whose consent is denied are excluded from activation.

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

## Partner documentation

Amazon Ads documents its own platform at <https://advertising.amazon.com/API/docs>. 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/amazon-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.