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

# DSP

Push audiences to Amazon DSP for programmatic buying on and off Amazon.

The Amazon DSP connector pushes your audiences to the Amazon Demand Side Platform, so you can run media campaigns against them.

<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, Cookies</td></tr><tr><td><strong>Authentication</strong></td><td>OAuth authorisation code, passed to your account manager</td></tr></tbody></table>

## Description

### What is Amazon DSP?

Amazon DSP, a solution from Amazon Ads, enables programmatic buying of display, video, audio and in-app ads, both on and off Amazon. It gives access to audiences and insights from shoppers across Amazon's website and physical stores.

With Amazon DSP you can:

* Reach relevant audiences, and use insights to inform how you reach them.
* Activate your first-party data within Amazon DSP to run more relevant campaigns.
* Access services from the Amazon group such as Fire TV, IMDb TV and Twitch.
* Deliver ad experiences across preferred touchpoints such as video and audio, and measure the outcome of your media investment.

### Which identifiers are sent

* **Mobile IDs**
* **Cookies**

Amazon Ads is reached by several connectors and they behave differently - [the comparison is on the Amazon Ads page](/connectors/destinations/amazon-ads.md).

## Connector setup

### Prerequisites

* An Amazon user account with access to the Amazon DSP accounts to be managed through the API.
* The target **Advertiser ID**.

{% hint style="warning" %}
Cookie matching must be activated on your organisation. Contact your account manager to confirm.
{% endhint %}

### Authentication

Grant mediarithmics access through Amazon's OAuth flow. The authorisation URL differs by region:

<table data-search="false"><thead><tr><th width="120">Region</th><th></th></tr></thead><tbody><tr><td><strong>NA</strong></td><td><code>https://www.amazon.com/ap/oa?client_id=amzn1.application-oa2-client.aedce04c891143ab9aab8246f48754d1&#x26;scope=advertising::audiences&#x26;response_type=code&#x26;redirect_uri=https://navigator.mediarithmics.com</code></td></tr><tr><td><strong>EU</strong></td><td><code>https://eu.account.amazon.com/ap/oa?client_id=amzn1.application-oa2-client.aedce04c891143ab9aab8246f48754d1&#x26;scope=advertising::audiences&#x26;response_type=code&#x26;redirect_uri=https://navigator.mediarithmics.com</code></td></tr><tr><td><strong>FE</strong></td><td><code>https://apac.account.amazon.com/ap/oa?client_id=amzn1.application-oa2-client.aedce04c891143ab9aab8246f48754d1&#x26;scope=advertising::audiences&#x26;response_type=code&#x26;redirect_uri=https://navigator.mediarithmics.com</code></td></tr></tbody></table>

{% hint style="danger" %}
The authorisation code expires after **5 minutes**. Repeat the steps to generate a new one.
{% endhint %}

### Setup steps

{% stepper %}
{% step %}
**Open the authorisation URL for your region in your browser.**
{% endstep %}

{% step %}
**Sign in with an Amazon user account that has access to the Amazon DSP accounts to be managed through the API, and allow the access grant.**
{% endstep %}

{% step %}
**Copy the `code` parameter from the redirect URL and send it to your account manager, within 5 minutes.**

The result URL looks like `https://navigator.mediarithmics.com/?code=…&scope=advertising%3A%3Aaudiences#/…`
{% endstep %}

{% step %}
**Select the Amazon DSP 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 within the platform.</td></tr><tr><td><strong>Advertiser ID</strong></td><td>The target Amazon audience advertiser ID.</td></tr><tr><td><strong>Region</strong></td><td>The target geolocalisation.</td></tr><tr><td><strong>Data source country</strong></td><td>The source country of your audience, as an ISO code - <code>FR</code>, <code>UK</code>, <code>IN</code>.</td></tr><tr><td><strong>Amazon consent - User personal data processing</strong></td><td>Whether the user consented to Amazon processing personal data, such as an advertising identifier, for advertising purposes. See <a href="/connectors/destinations/amazon-ads/consent-management.md">Amazon Ads - Consent management</a>.</td></tr><tr><td><strong>Amazon consent - Advertising cookies read and write</strong></td><td>Whether the user consented to Amazon reading or writing advertising cookies or similar technologies on their device. See <a href="/connectors/destinations/amazon-ads/consent-management.md">Amazon Ads - Consent management</a>.</td></tr><tr><td><strong>Identifying resources</strong></td><td>The identifier types to send to Amazon.</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*.

## Good to know

{% hint style="warning" %}
Following CNIL guidance on cookies and trackers, make sure that:

1. the partner is correctly named when you collect user consent for targeting purposes, or the equivalent;
2. the partner is named in your cookie policy - these partners may drop a cookie on your users' browsers from your websites.
   {% endhint %}

## FAQ

#### The authorisation code stopped working.

It expires after 5 minutes. Repeat the authorisation steps and send the new code straight away.

#### Which authorisation URL should I use?

The one matching your region: NA, EU or FE.

## 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/dsp.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.