Amazon DSP Integration

Amazon DSP gives you access to an audience nobody else has at the same scale: real shoppers with real Amazon purchase history, reachable both on Amazon's owned properties (Prime Video, IMDb, Fire TV, Twitch) and across the open web through Amazon Publisher Services. The targeting depth that first-party shopper data enables is genuinely unique, and that's why DSP often performs above its CPM for ecommerce and retail-adjacent offers.

The reporting story is the harder part. Amazon's reporting is rich but siloed — DSP performance lives in the Amazon Advertising console, conversion data tied to non-Amazon purchases lives wherever you're tracking it, and tying the two together usually means manual stitching. The Routy integration with Amazon DSP pulls spend and performance data into Routy on a continuous schedule so DSP stops being a black box and starts showing up in the same reports as the rest of your media.

After connecting, the following becomes available in your Routy reports:

• Spend at the order, line item, and creative level, so the full DSP hierarchy is measurable in the same place as your other media
• Impressions, clicks, view-through rate, click-through rate, and the format-specific engagement metrics Amazon DSP exposes
• Conversion attribution that ties every conversion Routy tracks back to the DSP order, line item, and creative behind the click or view, with view-through credit handled where applicable
• Cross-channel reporting that puts DSP alongside search, social, native, and other programmatic spend on consistent terms

Note that for conversions happening on Amazon itself (Amazon retail purchases), Amazon's own attribution model is the source of truth — Amazon DSP reports those internally and Routy surfaces what Amazon returns. For non-Amazon conversions (your own site, affiliate offers), Routy's attribution applies as normal.

You connect your Amazon Advertising account through Amazon's standard OAuth flow. Once connected, performance data pulls from the Amazon Advertising API on a regular schedule, and Routy reconciles it with the conversions you're already tracking.

A few things worth knowing before you connect:

• Amazon DSP requires either a direct account or an agency seat to access. There's also typically a minimum spend commitment to maintain DSP access, which is set by Amazon's sales team and varies by region and account type.
• View-through attribution is a significant part of how DSP performance is measured, more so than on most click-driven platforms. Amazon's default view-through windows can extend up to 14 days; the integration respects whatever windows your account has configured.
• Some Amazon DSP data is aggregated or modelled to protect shopper privacy, particularly when reporting drills down to small audience segments. This is an Amazon-side behaviour driven by Amazon's privacy commitments, not an integration limitation.

Amazon DSP is one of those channels that tends to be either over-invested in (because the shopper data is genuinely good and the early results look promising) or under-invested in (because the reporting is hard and nobody on the team is confident defending the spend at the quarterly review). Both outcomes are usually a function of measurement rather than performance. The campaigns themselves are often doing fine; the visibility into what they're producing relative to everything else is what's missing.

Connecting Routy fixes the visibility side. DSP spend, performance, and downstream attribution end up in the same view as your other channels, on the same terms. The cross-channel media planning conversation can include DSP without requiring twenty minutes of context, and the budget defending becomes a matter of reading the numbers rather than constructing them from scratch. For operations running Amazon DSP alongside non-Amazon channels, this tends to be the most useful single thing you can do to make the DSP line item defensible.