> ## 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 Ads data source. ## Why is my Amazon Ads data source empty? The most common cause is a region mismatch. Amazon Ads accounts are split across three regions — North America, Europe, and Far East — and each region is served by a different Amazon endpoint. A region is chosen when the data source is connected, and it is locked to the connection after that. If the account's ad profiles live in a different region than the one selected, the connection authenticates but returns no data. The region cannot be changed on an existing connection. To report on an account in another region, connect a new Amazon Ads data source and select the correct region during setup. See [How to connect Amazon Ads to Adriel](/data-sources/a-f/amazon-ads/how-to-connect). ## Why don't my older campaigns appear right after I connect? When an Amazon Ads data source is first connected, Adriel imports up to the last 60 days of performance history. Campaigns and reporting older than that initial window are not backfilled at connection time. Because Adriel caches the data it imports, the longer the data source stays connected, the more historical data accumulates in the cache. Coverage therefore grows over time from the connection date forward, so recently connected sources show a shorter history than ones that have been connected for a while. ## Why does a metric show blank on some campaigns? Amazon Ads unifies three ad surfaces — Sponsored Products, Sponsored Brands, and Sponsored Display — and each surface reports a different metric set. A metric only returns a value on the surface that produces it. Requesting a metric on a campaign from a different surface returns an empty value rather than a zero. The metric set breaks down roughly like this: * **Sponsored Products** has the largest set, including ASIN-level sales, units sold, ACOS, and ROAS. * **Sponsored Brands** adds video and brand-awareness metrics such as branded searches and detail page views. * **Sponsored Display** adds view-through and engagement metrics such as viewable impressions and view-through add-to-cart. When a widget mixes campaign types, splitting by a campaign or objective breakdown makes it clear which rows can carry the metric. For the full per-surface metric list, see the [Amazon Ads data reference](/data-sources/a-f/amazon-ads/data-reference). ## Why is my reach higher than expected over a long date range? Reach and other uniqueness-based metrics are computed per daily snapshot rather than deduplicated across the whole date range. A user reached on more than one day is counted once per day, so summing reach over a multi-day window can overstate the true number of unique users. For an accurate unique figure, view reach one day at a time, or treat the multi-day total as an upper bound rather than a precise count. Additive metrics such as impressions, clicks, and spend are not affected and aggregate normally. ## Why don't my Amazon Ads numbers match Amazon's console exactly? Small differences usually come down to how conversions are attributed. Amazon reports conversions across four click-attribution windows — 1-day, 7-day, 14-day, and 30-day — and Amazon's console often defaults to the 7-day window. A dashboard widget can show a different figure simply because it references a different attribution variant. Matching the window on both sides gives a like-for-like comparison. The attribution variants are listed in the [Amazon Ads data reference](/data-sources/a-f/amazon-ads/data-reference). Two other factors contribute. Dashboard values read from Adriel's most recent cached snapshot, so figures Amazon has restated since that snapshot are not yet reflected. And the connector does not return deleted elements, so removed campaigns, ad groups, or ads can be absent from reports that still include them on Amazon's side. ## How do I report on Amazon Ads accounts in more than one region? Each Amazon Ads connection covers a single region, and a region can contain a different set of ad accounts than the others. To bring more than one region into Adriel, connect a separate Amazon Ads data source for each region and select that region during setup. Once each region is connected, its metrics and breakdowns are normalized to the same reporting format, so a single dashboard widget can aggregate across all of them without extra configuration. ## Related Metrics, breakdowns, attribution windows, and limits for Amazon Ads. Authorize an account and choose the correct region during setup. Separate connector for Amazon's programmatic display and video buying. Separate connector for the Amazon DSP self-service (ADSP) surface.