Data reference - Adriel Knowledge Base

Introduction

Amazon Ad Server (formerly Sizmek) is a third-party ad-serving platform used to deliver, measure, and verify display, video, and rich-media creatives across the open web. The connector pulls delivery, engagement, video, cost, and conversion data across the ad account, campaign, ad set, and ad hierarchy. 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 Ad Server to Adriel.

Data refresh strategy

Architecture data

Architecture covers ad accounts, campaigns, ad sets, and ads. It refreshes twice daily at 4:00 PM UTC and 5:00 AM UTC.

Reports data

Reports include daily performance for ad accounts, campaigns, ad sets, and ads. Cache-only. Report data comes from cached daily performance snapshots. When a dashboard loads, data is composed from the last snapshot rather than fetched on demand, so uniqueness-based metrics such as reach may be overvalued across date ranges longer than one day. Initial fill. On data source creation, the cache fills with 365 days of historical data at the ad account, campaign, ad set, and ad levels. Refresh schedule. Reports refresh on two overlapping schedules:

9:00 PM and 9:00 AM UTC daily — syncs the last 9 days for ad account, campaign, ad set, and ad
6:00 PM UTC every 2 days — syncs the last 17 days for ad account, campaign, ad set, and ad

Data is considered reliable within the cache sync window. Older data may be incomplete or inaccurate due to legacy caching behavior.

Architecture levels

Ad account → Campaign → Ad set → Ad

Date range limits

Breakdown	Max range
Daily	93 days
Weekly	1 year
Monthly	2 years

Metrics

How to read the API Key columnCode style like Impressions (Net) is the literal Amazon Ad Server metric name requested from the platform. Italic text describes how a value is produced when it doesn’t map cleanly to a single platform field (Adriel-computed rates or values aggregated internally).

Performance

Metric	Description	Data type	API Key
Impressions	Total ad serves.	Number	`Impressions (Net)`
Clicks (all)	Total clicks recorded.	Number	`Clicks (Net)`
CTR	Click-through rate (clicks ÷ impressions).	Percentage	Adriel-computed
CPM	Cost per thousand impressions.	Currency	Adriel-computed
CPC	Cost per click.	Currency	Adriel-computed
Ad spend	Total amount spent during the reporting period.	Currency	`Total Media Cost`
Unique impressions	Distinct users served an impression. Requires an ad, campaign, or placement breakdown.	Number	Requested from the platform when a supported breakdown is present
Unique clicks	Distinct users who clicked. Requires an ad, campaign, or placement breakdown.	Number	Requested from the platform when a supported breakdown is present

Video performance

Metric	Description	Data type	API Key
Video played to 25% (rate)	Share of video plays reaching 25% of length.	Percentage	`Video 25% Played Rate`
Video played to 50% (rate)	Share of video plays reaching 50% of length.	Percentage	`Video 50% Played Rate`
Video played to 75% (rate)	Share of video plays reaching 75% of length.	Percentage	`Video 75% Played Rate`
Video fully played	Plays reaching 100% of video length.	Number	`Video Fully Played`
Video fully played (rate)	Share of video plays reaching 100% of length.	Percentage	`Video Fully Played Rate`

Conversion performance

Conversions are fetched in a separate report and merged into row data. Each conversion event surfaces its own count and value, along with derived CPA, ROAS, and CVR. Metric names below follow the pattern for each event, where [Conversion event] is the event’s name.

Metric	Description	Data type	API Key
`[Conversion event]`	Conversion count for the event.	Number	`Total Conversions` (resolved per conversion report row)
`[Conversion event]: Conversion value`	Monetary value of the conversion event.	Currency	`Conversion Revenue` (resolved per conversion report row)
`[Conversion event]: CPA`	Cost per acquisition (spend ÷ conversions).	Currency	Adriel-computed
`[Conversion event]: ROAS`	Return on ad spend (value ÷ spend).	Ratio	Adriel-computed
`[Conversion event]: CVR`	Conversion rate (conversions ÷ clicks).	Percentage	Adriel-computed

Breakdowns

Standard hierarchy

Breakdown	Description	API Key
Ad account	Group by Amazon Ad Server advertiser account.	`adAccount`
Campaign	Group by campaign within the account.	`campaign`
Ad set	Group by placement or ad set within the campaign.	`adSet`
Ad	Group by individual creative.	`ad`

Creative & placement

Breakdown	Description	API Key
Creative type	Group by creative format (display, video, rich media).	Resolved from creative metadata
Placement	Group by placement label assigned in Amazon Ad Server.	Resolved from placement metadata

Geographic

Breakdown	Description	API Key
Geographic	Group by country or region of delivery.	Resolved from geo metadata

Overview & status

Breakdown	Description	API Key
Status	Group by active or paused state.	Resolved from architecture
Starts / Ends	Group by flight start and end dates.	Resolved from architecture

Time & date grouping

The platform returns daily records; Adriel groups them into these views for reporting. All time-grouping breakdowns are Adriel-side aggregations of the same underlying daily data.

Breakdown	Description
Auto Time Breakdown	Automatically picks the best granularity for the date range.
Daily	Split reports by day.
Weekly	Split reports by week.
Monthly	Split reports by calendar month.

Limitations

Based on the current connector, Amazon Ad Server has the following limits:

Cache-only data — all report data is served from scheduled daily snapshots. Uniqueness-based metrics such as reach may be overvalued when viewed across date ranges longer than one day, and data outside the cache sync window may be incomplete.
Unique metrics need a breakdown — Unique Clicks and Unique Impressions require at least one of Ad, Campaign, or Placement as a breakdown. They are unavailable at the ad-account level, where none of these are present.
Total Custom Interactions conflict — Total Custom Interactions cannot be requested at the same time as conversions, so it is excluded from the default request set.
Placement breakdown availability — the Placement (Site) breakdown is limited to specific workspaces and is not enabled by default.
Two parallel reports — every fetch fires a basic performance report and a conversions report in parallel, merged before normalization. This makes the connector slower to refresh than single-report integrations, and a partial result may appear if one report fails while the other succeeds.
Architecture volume cap — ad discovery reads pages of 500 ads and stops with an error if it exceeds roughly 50,000 ads without completing.

API references

Amazon Ad Server SAS API (adapi.sizmek.com/sas/) — architecture data and authentication
Amazon Ad Server Report Builder API (api.sizmek.com/rest/ReportBuilder/reports/) — asynchronous report generation

​Introduction

​Data refresh strategy

​Architecture data

​Reports data

​Architecture levels

​Date range limits

​Metrics

​Performance

​Video performance

​Conversion performance

​Breakdowns

​Standard hierarchy

​Creative & placement

​Geographic

​Overview & status

​Time & date grouping

​Limitations

​API references

​See also

Introduction

Data refresh strategy

Architecture data

Reports data

Architecture levels

Date range limits

Metrics

Performance

Video performance

Conversion performance

Breakdowns

Standard hierarchy

Creative & placement

Geographic

Overview & status

Time & date grouping

Limitations

API references

See also