Amazon DSP Destination
Send server-side conversion events to Amazon DSP to measure how your programmatic campaigns drive purchases, sign-ups, and other conversions.
Use this page to connect Ours Privacy to Amazon DSP (also called the Amazon Conversions API). Each conversion you forward is matched against your Amazon DSP campaigns so you can measure how your programmatic ads drive purchases, sign-ups, and other outcomes. Identity fields are hashed before they leave Ours Privacy.
Before you start
- An Amazon Ads account with a DSP Advertiser ID (DSP Entity IDs are not supported).
- A conversion definition created in Amazon's Events Manager. Each one represents a conversion type and has its own ID.
- The connected Amazon Ads account must have the Event Manager edit permission on the target DSP advertiser.
Setup
- In Ours Privacy, add the Amazon DSP destination.
- Click Connect and sign in with the Amazon account that manages your DSP advertiser.
- Enter your DSP Advertiser ID (find it in the Amazon DSP console under the advertiser's settings).
- In the event mapping, set the Conversion Definition ID for the conversion you're tracking.
- Map at least one identity field (such as email, phone, or postal code) and the user's country so Amazon can match the conversion.
The mapping UI documents every available field with inline tooltips, so use it as the source of truth when configuring your events.
Event types
Map each of your events to the conversion you want to record in Amazon DSP. Revenue events can carry a value, currency, and units sold; identity fields (email, phone, name, city, state, postal code, and mobile advertising ID) strengthen matching. The mapping UI shows the full set of available fields.
Note: Amazon DSP does not accept backfilled (historical) events. Only conversions sent as they happen are processed.
Limited Data Use (LDU)
Amazon calls its version limited data use, and it behaves differently from every other destination that offers this flag: Amazon does not process an event marked for limited data use at all. Where Facebook or Nextdoor restrict a flagged event to reporting only, Amazon excludes it entirely, so the conversion will not appear in Amazon reporting, attribution, or optimization.
One field in the destination mapping controls it:
- Limited Data Use: set to true and Amazon drops the event. Map it to the opt-out signal you already collect, such as a consent choice or a Global Privacy Control signal.
Because a flagged event is discarded rather than restricted, do not map this field expecting Facebook-style behavior — every event you flag is a conversion you will not see in Amazon. Amazon does not offer a middle option that restricts processing while preserving measurement. If that is what you need, withhold the events instead using Global Data Governance rules or your consent configuration.
Leave the field unmapped and your events go out with no restriction requested, which is the default.
See Limited Data Use for every destination that supports a flag like this and what each platform calls it.
Next steps
Need help? Contact support@oursprivacy.com.
How is this guide?