> ## Documentation Index > Fetch the complete documentation index at: https://docs.adriel.com/llms.txt > Use this file to discover all available pages before exploring further. # FAQs > Common questions, expected behaviors, and troubleshooting for the Amazon Ad Server data source. ## Why is my Amazon Ad Server data slower to refresh than other data sources? Every Amazon Ad Server fetch runs two separate reports — one for standard performance metrics and one for conversions — which are generated on the platform's side and then combined before the data is normalized. Reports are also served from a cache rather than fetched on demand, so a dashboard composes its numbers from the most recent cached snapshot. Both factors mean fresh figures land on the next scheduled sync rather than the instant a report is requested. For the exact refresh schedule and initial import window, see the [Amazon Ad Server data reference](/data-sources/a-f/amazon-ad-server-sizmek/data-reference). ## Why does part of my Amazon Ad Server data appear while the rest is missing? Because each fetch combines two independent reports, a partial result can appear when one report returns data and the other does not. Performance metrics come from the basic report; conversions come from a separate conversions report and are matched onto their performance rows by advertiser, campaign, ad, and day. When the two reports don't line up for a given slice — for example, a conversion row with no matching performance row — that slice can be dropped from the merged result. The gap typically resolves on the next successful sync, once both reports return complete data for the same period. ## Why do reach and unique-user metrics look inflated over long date ranges? Report data is served from cached daily snapshots. Uniqueness-based metrics such as Unique Impressions, Unique Clicks, and reach count a distinct user only once within a single day's snapshot, but the same user seen across several days is counted in each day. As a result, these metrics can be overvalued when a widget spans a date range longer than one day, and the overcount grows with the range. Counting-based metrics such as Impressions, Clicks, and Ad spend aggregate cleanly and are not affected. For a single-day view of a uniqueness metric, narrow the widget's date range to one day. ## Why don't Unique Clicks and Unique Impressions show at the ad-account level? Unique Clicks and Unique Impressions are only returned when the request includes at least one of the Ad, Campaign, or Placement breakdowns. At the ad-account level none of those are present, so both metrics are excluded and the widget shows no value. To see them, add an Ad or Campaign breakdown to the widget, or drill into a campaign. The same requirement applies to widgets built directly at the ad-account level — elevating the breakdown restores the metrics. ## Why is the Placement breakdown unavailable in my dashboard? The Placement (Site) breakdown is enabled only for specific workspace configurations and is not part of the default breakdown set. Where it isn't enabled, Amazon Ad Server still supports the standard hierarchy breakdowns — Ad account, Campaign, Ad set, and Ad — along with Creative type, Geographic, Status, and the time-grouping breakdowns. For the full list of breakdowns available for this data source, see the [Amazon Ad Server data reference](/data-sources/a-f/amazon-ad-server-sizmek/data-reference). ## Related Metrics, breakdowns, refresh cadence, and limits for the data source. Step-by-step setup for the Amazon Ad Server connection. How Adriel schedules syncs and caches data source data. Fields and limits for the related Amazon DSP data source.