> For the complete documentation index, see [llms.txt](https://docs.roivenue.com/roivenue-resources/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roivenue.com/roivenue-resources/roivenue-training/roivenue-app/data/connectors-overview/list-of-connectors/amazon-dsp.md).

# Amazon DSP

How to connect Amazon DSP to Roivenue, what the default setup downloads, and how the figures are put together.

Amazon DSP programmatic display. The Roivenue connector downloads daily impressions, clicks and cost down to creative level, plus the off-Amazon purchases attributed to them.

## Setting up the connector

Add a Amazon DSP connector in Roivenue and choose Connect to Amazon DSP. Roivenue sends you to Amazon DSP to sign in and approve access. There are no keys to copy.

### Setup options

| Option                    | Default            | What it does                                          |
| ------------------------- | ------------------ | ----------------------------------------------------- |
| Conversion type name      | `purchase`         | What Amazon DSP purchases are called inside Roivenue. |
| Web source and Web medium | `amazon` and `cpc` | How Amazon DSP traffic should be recognised.          |

## What the default setup downloads

Three jobs. One brings impressions, clicks and cost per creative and day, a second brings purchases and product sales, and a third downloads the feed behind synthetic impressions.

### Where the values land

| Amazon DSP field        | Roivenue column |
| ----------------------- | --------------- |
| `orderName`             | adCampaign      |
| `lineItemName`          | adGroup         |
| `creativeName`          | adName          |
| `impressions`           | impressions     |
| `clicks`                | clicks          |
| `totalCost`             | cost            |
| `offAmazonPurchases`    | conversions     |
| `offAmazonProductSales` | conversionValue |

Amazon DSP's vocabulary maps onto Roivenue's as order to campaign, line item to ad group, and creative to ad.

Conversions are off-Amazon purchases, meaning sales on your own site rather than on Amazon. Sales that happened on Amazon itself are not in these figures.

The jobs reprocess the last three days on every run.

## Available columns

The table above is what the recommended template downloads. Every column this connector can bring back is listed on [Amazon DSP - Supported Columns](/roivenue-resources/roivenue-training/roivenue-app/data/connectors-overview/list-of-connectors/amazon-dsp/amazon-dsp-supported-columns.md).

Adding one means editing the connector in the Advanced Editor, which stops that connector receiving template updates.

## Synthetic impressions

Alongside the daily figures, this connector downloads a conversion feed that Roivenue uses to build synthetic impressions.

Ad platforms report conversions that Roivenue never saw as a web session, because of ad blockers, cross-device journeys or conversions uploaded from a CRM. Left alone those orders look like they came from nowhere, and paid media gets undercounted. The synthetic impression stands in for the missing visit so path analysis and attribution see a complete journey.

There is nothing to configure. It comes with the connector, and it is why the setup creates more than one job.

## How far back the data goes

The connector will request up to three years of history. How much arrives depends on what the platform holds for the account.

## Troubleshooting

<details>

<summary>Conversions look low for a retail campaign</summary>

The connector reads off-Amazon purchases, which are sales on your own site. Purchases made on Amazon are not counted here.

</details>

<details>

<summary>Campaign names look like order names</summary>

That is expected. Amazon DSP calls a campaign an order, and the order name is what arrives in the campaign field.

</details>