For the complete documentation index, see llms.txt. This page is also available as Markdown.

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.

Connection

Type

Server-side

Category

Identifiers sent

Mobile IDs, Cookies

Authentication

OAuth authorisation code, passed to your Account Manager

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.

Connector setup

Prerequisites

  • An Amazon user account with access to the Amazon DSP accounts to be managed through the API.

  • The target Advertiser ID.

Authentication

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

Region

NA

https://www.amazon.com/ap/oa?client_id=amzn1.application-oa2-client.aedce04c891143ab9aab8246f48754d1&scope=advertising::audiences&response_type=code&redirect_uri=https://navigator.mediarithmics.com

EU

https://eu.account.amazon.com/ap/oa?client_id=amzn1.application-oa2-client.aedce04c891143ab9aab8246f48754d1&scope=advertising::audiences&response_type=code&redirect_uri=https://navigator.mediarithmics.com

FE

https://apac.account.amazon.com/ap/oa?client_id=amzn1.application-oa2-client.aedce04c891143ab9aab8246f48754d1&scope=advertising::audiences&response_type=code&redirect_uri=https://navigator.mediarithmics.com

Set up the Amazon Ads - DSP connector

1

Log in to the mediarithmics platform first, so the redirect does not drop the code.

2

Open the authorisation URL for your region in your browser.

3

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.

4

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#/…

5

Select the Amazon DSP connector and fill in its configuration.

Field

Name

Identifies the feed within the platform.

Advertiser ID

The target Amazon audience advertiser ID.

Region

The target geolocalisation.

Data source country

The source country of your audience, as an ISO code - FR, UK, IN.

Amazon consent - User personal data processing

Whether the user consented to Amazon processing personal data, such as an advertising identifier, for advertising purposes. See Amazon Ads - Consent management.

Amazon consent - Advertising cookies read and write

Whether the user consented to Amazon reading or writing advertising cookies or similar technologies on their device. See Amazon Ads - Consent management.

Identifiers

The identifier types to send to Amazon. See Identifiers.

Creating and activating the feed on a segment is covered in Send your first-party data to a destination.

Good to know

FAQ

The authorisation code stopped working.

It expires after 5 minutes, and it is lost if you were not logged in to the mediarithmics platform when Amazon redirected you. 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.

Last updated

Was this helpful?