Skip to main content

​
Why can’t I change the report type after connecting?

The report type is chosen when the Amazon ADSP data source is created and is fixed for the life of that data source. Each report type — Topline Performance, Untargeted Audiences, Targeted Audiences, Creative Performance, or Products Performance — stores its data in its own isolated table with fields that are specific to that report, so the type cannot be switched later without changing the shape of the stored data. To work with a different report, connect a new Amazon ADSP data source and select the wanted report type at creation. Multiple ADSP data sources can run side by side, one per report type. See the Amazon ADSP data reference for what each report type covers.

​
Can I combine multiple report types in one data source?

No. Because each report type is stored in its own isolated table, a single Amazon ADSP data source only exposes the metrics and breakdowns of the one report type it was created with, and report types cannot be joined within that data source. The supported approach is to connect a separate data source for each report type and place their widgets on the same dashboard. Each widget then reads from the report type that fits the question it answers.

​
Why don’t my Amazon DSP and Amazon ADSP numbers match?

Amazon ADSP and Amazon DSP are two different connectors that reach different Amazon-side reports through different paths. The Amazon ADSP connector reads the ADSP reporting interface at advertising.amazon.com, while the Amazon DSP connector pulls from Amazon’s DSP reporting API. Because the underlying reports, columns, and roll-ups differ, totals from the two sources are not expected to reconcile line for line. For programmatic DSP reporting, pick the connector that matches the report being compared against, rather than treating the two as interchangeable. For Sponsored Products, Sponsored Brands, and Sponsored Display, see the separate Amazon Ads data reference.

​
Why aren’t ad accounts, campaigns, or line items available as breakdowns?

Amazon ADSP does not import a separate hierarchy of ad accounts, campaigns, or line items. The selected report type defines the full shape of the data source, so the available breakdowns are the ones that belong to that report — for example, Account and Proposal for Topline Performance, audience segment for the audience reports, Creative for Creative Performance, and Product for Products Performance. If a breakdown from a different report type is needed, connect a data source for that report type instead. The report-type breakdown tables in the Amazon ADSP data reference list what each report exposes.

​
Why did my first sync take longer than expected, and why does data occasionally pause?

Amazon ADSP reads its data from the ADSP reporting interface rather than a direct API. The first sync signs in to that interface and navigates to the selected report before the first snapshot can be stored, so initial data can take longer to appear than it would for an API-based source. Once the first snapshot is stored, dashboards read from the cached data. Because the data path depends on the ADSP reporting interface, an unexpected change on Amazon’s side can briefly interrupt a sync until the next scheduled refresh recovers it. This is expected behavior for a UI-based source; the connector resumes on its own. Refresh timing lives in the Amazon ADSP data reference.

​
How much historical data is available?

When an Amazon ADSP data source is first connected, Adriel imports the history the ADSP report exposes for the selected report type. Because Adriel caches what it retrieves, the longer the data source stays connected, the more historical data accumulates in the cache over time. There is no separate back-fill step beyond this initial import and the growing cache. To retain a longer history, keep the data source connected rather than disconnecting and reconnecting it.