Introduction
Amazon DSP is Amazon’s demand-side platform for programmatic display, video, audio, and over-the-top advertising across Amazon properties (for example, IMDb, Twitch, and Fire TV) and third-party publishers. The connector integrates with the DSP Reports v3 API through an asynchronous request, poll, and download pipeline to surface advertiser, order, line item, and creative performance, with a wide set of viewability, video, conversion, and cost metrics. As a marketing connector, metrics, breakdowns, and currencies are standardized so widgets can aggregate across sources without additional configuration. To connect this data source, see How to connect Amazon DSP to Adriel.Data refresh strategy
Architecture data
Architecture covers advertisers, orders, line items, and creatives. It refreshes twice daily, at 9:00 PM UTC and 9:00 AM UTC.Reports data
Reports include daily performance for advertiser, order, line item, and creative. Cache-only. Report data comes from cached daily performance snapshots. Dashboard values are composed from the last snapshot, so the most recent few hours of activity are not yet reflected, and metrics based on uniqueness (such as reach) can be overvalued across date ranges longer than one day. Initial fill. On data source creation, the cache fills with 89 days of historical data at the advertiser, order, line item, and creative levels. Refresh schedule. Reports refresh at 7:00 PM UTC, syncing the last 7 days for order, line item, and creative. Data is considered reliable within the cache sync window. Older data may be incomplete or inaccurate due to legacy caching behavior.Architecture levels
Advertiser → Order → Line item → CreativeDate range limits
Metrics
How to read the columns
Data type uses this vocabulary: Number, Currency, Percentage, Ratio, Duration, Date, Text, URL, Array, Boolean.
API Key in code style like
impressions is the literal Amazon DSP API field name. Italic text describes how a value is produced when it doesn’t map cleanly to a single API field.Performance
Viewability
Each vendor family exposes viewable and measurable impression counts and a viewability rate. Field names extend the listed prefix, for example
dvViewableImpressions.Video performance
Conversions
Every conversion metric uses Amazon DSP’s fixed 14-day attribution window and carries a
14d suffix. There is no API-level support for shorter or longer windows (Amazon DSP reporting docs).Custom conversion events
For each pixel or conversion event configured in the DSP account, the connector auto-generates a metric family.Brand store engagement
Amazon DSP exposes seven brand store engagement slots that customers configure based on their store layout. All seven are surfaced as metrics; their names follow the store configuration.Cost accounting
Breakdowns
Standard hierarchy
Creative attributes
Delivery & inventory
Audience & environment
Time grouping
Amazon DSP returns daily records; Adriel groups them into these views for reporting. Each grouping has its own maximum date range (see Date range limits).
Limitations
- Fixed 14-day attribution window — every conversion metric uses Amazon DSP’s 14-day window. Comparisons with platforms that use a different default (for example, Meta’s 7-day click) will show differences that come solely from the attribution-window mismatch.
- ASIN restatement within 28 days — if ASINs are added to or removed from a campaign after it starts, Amazon restates conversion attribution using the current ASIN set. Restatement applies retroactively and appears in reports within 28 days, so older periods can change from one refresh to the next (Amazon Ads data timing and restatement).
- ROAS is computed, not native — Amazon DSP exposes spend and sales but not native ROAS fields, so ROAS (including new-to-brand and combined variants) is computed downstream. Native CTR and ROAS fields, along with
advertiserId,advertiserName,date,entityId,intervalEnd, andintervalStart, are excluded from the request set because including them triggers DSP API errors. - Cache-only delivery — reports are served from scheduled snapshots, not on-demand pulls, so the most recent few hours of activity are not yet reflected. Reach across long date ranges can be overvalued, as with any cache-only connector.
- Post-refresh adjustments — Amazon may adjust data after the initial refresh: invalid-traffic removal for up to 72 hours, order cancellations and payment declines within 72 hours, and reach and frequency figures may be recomputed (Amazon Ads data timing and restatement).
