You can visualize Amazon Ads data in QlikView by connecting Amazon Ads as a data source on Kondado and choosing QlikView as the destination. Kondado reads the Amazon Ads pipelines you select, such as the Sponsored Products report, Sponsored Brands report and Amazon DSP report, and delivers them through a Via Kondado connection, with no intermediate databases and no complex setup. You set the update frequency yourself, from every 5 minutes to hourly or daily, so your QlikView apps always reflect the campaign performance your team needs to review.
Kondado connects Amazon Ads to QlikView with 27 pipelines and 1,247 fields covering impressions, clicks, cost, attributed sales, ACOS and ROAS by account, campaign, ad group, ad, keyword and search term. Marketing teams, agencies and operations teams get advertising data ready to blend with their own business figures inside QlikView, so decisions about budget, bids and targeting rest on one clear view instead of scattered spreadsheets.
Each item below is automatically replicated by Kondado from Amazon Ads into QlikView — no schema setup, no manual mapping.
27
available pipelines
1247
extractable fields
∞
Auto-refresh
Available integrations
Metadata: Amazon DSP - advertisers
Registration of Amazon DSP advertisers, with advertiser ID, name, country, currency, regional-account flag, timezone, URL, and source ad-account profile_id.
Metadata: Amazon DSP - campaigns (orders)
Registration of Amazon DSP campaigns (orders) per advertiser, with identifiers, name, state, delivery status, dates, budget caps, flights, fees, frequencies, country, marketplace, brand, and optimization settings.
Metadata: Amazon DSP - ad groups (line items)
Registry of Amazon DSP ad groups (line items), with profile, advertiser and campaign IDs, name, state, delivery status, dates, budget, bids, optimization, pacing and targeting settings.
Metadata: Advertising accounts (profiles)
Registration of an Amazon Ads advertising account (profile) visible at login, with profile_id, account data (id, marketplace, name, subtype, seller/vendor/agency type, and valid payment method), country, currency, daily budget, and timezone.
Metadata: Portfolios
Registry of each ad account's portfolios, with account and portfolio IDs, name, state, budget amount, currency, start and end dates, policy, unspent-budget sharing setting, and in-budget indicator.
Metadata: Sponsored Brands - ads
Metadata for Sponsored Brands ads, one row per ad identified by ad_key/ad_id, including account, ad group and campaign, creative, landing page, name, state, and creation/update dates and serving status.
Metadata: Sponsored Brands - campaigns
Metadata for one Sponsored Brands campaign per row, with account, campaign and portfolio IDs, name, state, start/end dates, budget and budget type, cost type, goal, KPI, bid optimization/strategy and adjustments, product location, and multi-ad-group flag.
Metadata: Sponsored Brands - ad groups
Metadata for Sponsored Brands ad groups, with profile ID, ad group ID, campaign ID, name, and advertiser-defined state.
Metadata: Sponsored Brands - keywords
Metadata for Sponsored Brands keywords, one row per keyword, with profile, ad group, and campaign IDs, keyword text, match type, bid, and state.
Metadata: Sponsored Display - product ads
Metadata for Sponsored Display product ads, with one row per ad, containing profile_id, ad_id, ad_group_id, ASIN, campaign_id, and state.
Metadata: Sponsored Display - campaigns
One row per Sponsored Display campaign, with account, campaign, and portfolio IDs, name, budget and budget type, cost type, delivery profile, start/end dates, state, tactic, and rule-based budget processing flag.
Metadata: Sponsored Display - ad groups
Metadata for Sponsored Display ad groups, with profile_id, ad_group_id, campaign_id, name, state, default bid, bid optimization, creative type, and tactic.
Metadata: Sponsored Display - targets
Metadata for Sponsored Display targets, with one row per target (audience/product/contextual), containing profile_id, target_id, ad_group_id, campaign_id, bid, expression, expression_type, resolved_expression, and state.
Metadata: Sponsored Products - product ads
Registration of a Sponsored Products product ad, with account, ad, ad group, and campaign identifiers, ASIN, and state.
Metadata: Sponsored Products - campaigns
Registry of Sponsored Products campaigns, with one row per campaign and fields for name, state, budget and budget type, bidding strategy and adjustments, start and end dates, portfolio, targeting type, tags, and off-Amazon settings.
Metadata: Sponsored Products - ad groups
Metadata for Sponsored Products ad groups, with one row per ad group, containing profile ID, ad group ID, campaign ID, default bid, name, and state.
Metadata: Sponsored Products - keywords
Registration of Sponsored Products keywords, with one row per keyword, including profile, keyword, ad group, and campaign IDs, keyword text, match type, bid, and state.
Metadata: Sponsored Products - negative keywords
Registry of Sponsored Products ad group negative keywords, with profile, keyword, ad group, and campaign IDs, keyword text, match type, and state.
Registration of one Sponsored Products campaign negative keyword per row, with profile_id, keyword_id, campaign_id, keyword_text, match_type, and state.
Metadata: Sponsored Products - targets
Registration of a Sponsored Products target (product/category/auto target), with profile_id, target_id, ad_group_id, campaign_id, bid, expression, expression_type, resolved_expression, and state.
Metadata: Sponsored Products - negative targets
Metadata registry of Sponsored Products negative targets, with one row per negative target and fields such as profile_id, target_id, ad_group_id, campaign_id, expression, resolved_expression, and state.
Metadata: Sponsored TV - campaigns
Metadata for one Sponsored TV campaign per row, with profile_id, campaign_id, name, budget and budget type, country, start and end dates, state, and portfolio id.
Sponsored Brands report
Sponsored Brands report at account/date and campaign, ad group, ad, keyword, product, and placement grain, with impressions, clicks, cost, sales, orders, purchases, and new-to-brand metrics.
Sponsored Display report
Daily rows by account, campaign, ad group, and ad for Sponsored Display, with date, country, currency, status, budget, and metrics for impressions, clicks, cost, purchases, sales, reach, and conversions.
Sponsored Products report
Rows from the Sponsored Products report by account, campaign, ad group, ad, keyword/targeting, and search term, with date, impressions, clicks, cost, sales, purchases, ACOS, ROAS, and 1-, 7-, 14-, and 30-day attribution metrics.
Sponsored TV report
Row of the Sponsored TV report by account, date, campaign, ad group, and keyword dimensions, with budget/status and metrics such as impressions, clicks, cost, CTR, CPM, reach/frequency, conversions, new-to-brand, and off-Amazon conversions.
Amazon DSP report
Each row is an Amazon DSP report record at the selected level, detail, and period, with account and advertiser identifiers, date, country, currency, third-party fees, and event/conversion metrics such as add_to_cart, ROAS, and costs.
With Amazon Ads performance data in QlikView you can build custom dashboards that compare Sponsored Products, Sponsored Brands and Sponsored Display side by side. The Sponsored Products report brings daily impressions, clicks, cost, sales, ACOS and ROAS by campaign, keyword and search term, the Sponsored Brands report adds new-to-brand metrics, and the Amazon DSP report covers programmatic reach and conversions. Marketing teams can spot keywords that spend without converting, agencies can show clients portfolio-level pacing, and operations teams can follow budget consumption against sales. Blend these pipelines with your own revenue or margin data in QlikView to see profitability by campaign.
Try out all the features for free for 14 days
How to create Amazon Ads dashboards in QlikView
Visualize your data automatically — no spreadsheet exports or custom scripts.
1
Connect Amazon Ads as a data source
Add Amazon Ads on Kondado, authorize your advertising account and pick the pipelines you want, from Sponsored Products report to Amazon DSP campaigns.
2
Select QlikView as destination
Choose QlikView as the destination and copy the Via Kondado connection details into your QlikView script. If you prefer to stage data first, you can also send it to BigQuery or Google Sheets.
3
Build dashboards and set refresh
Create your QlikView sheets with the fields you need, then set the update schedule for each pipeline and align your reload tasks so the app stays current.
Try out all the features for free for 14 days
Access Amazon Ads data in QlikView and combine it with dozens of other data sources
If the source you want is not listed, drop us a chat message. We love to add new sources!
Answers about visualizing Amazon Ads data in QlikView automatically
How do I connect Amazon Ads to QlikView?▼
Start by adding Amazon Ads as a data source on Kondado and selecting the pipelines you want, such as Sponsored Products report or Portfolios. Then choose QlikView as the destination and use the Via Kondado connection details in your QlikView script. No code and no intermediate database are required, and you can be reading advertising data in your app the same day.
Which Amazon Ads dashboards can I build in QlikView?▼
You can build any custom view your team needs, for example ACOS and ROAS by campaign, wasted spend by search term, budget pacing by portfolio, or new-to-brand orders by ad group. Because QlikView lets you associate multiple pipelines, you can move from a portfolio summary down to a single keyword in a few clicks. Agencies often build one app per client and duplicate it as new accounts are added.
How often does Amazon Ads data refresh in QlikView?▼
Each pipeline can follow its own update schedule, so a fast-moving Sponsored Products report might run every 15 minutes while metadata such as campaigns or portfolios runs daily. You then align your QlikView reload tasks with that rhythm to keep apps current. This gives you control over how fresh the numbers are without overloading your reporting routine.
Which Amazon Ads KPIs should I track in QlikView?▼
The most useful starting set is cost, clicks, impressions, CTR, CPM, attributed sales, purchases, ACOS and ROAS, all available at campaign, ad group, ad, keyword and search term level. The Sponsored Products report also includes 1-, 7-, 14- and 30-day attribution windows, so you can compare short and long conversion windows. Sponsored Brands and Sponsored TV reports add new-to-brand and reach metrics for upper-funnel analysis.
Can I combine Amazon Ads data with my own sales data in QlikView?▼
Yes. Kondado can send other business data to destinations such as Google Sheets or BigQuery, and you can bring those figures into the same QlikView app as your advertising pipelines. Associating ad spend with revenue or margin lets you see profit per campaign rather than cost alone. Many teams also pull in Amazon DSP data to compare programmatic results with sponsored ads.
Do I need to build my own Amazon Ads dashboards in QlikView?▼
Yes, you design the QlikView sheets yourself using the fields delivered by the pipelines, which gives you full freedom over layout, calculations and branding. Because 1,247 fields are available across 27 pipelines, you can start with a simple spend and ACOS overview and expand into keyword, placement and DSP views over time. Building your own sheets also means the metrics match how your business measures performance.
How can I share Amazon Ads dashboards with my team?▼
Publish the QlikView app through QlikView Server or Access Point so colleagues open the same version instead of emailing files. You can also export sheets to PDF or Excel for client reviews and weekly reports. Teams that prefer browser access often route the same pipelines to Power BI or Looker Studio alongside QlikView.
What level of detail is available for Amazon Ads in QlikView?▼
Data reaches account, portfolio, campaign, ad group, ad, keyword, target and search term granularity, with daily rows and dimensions such as country, currency and status. Metadata pipelines for campaigns, ad groups, keywords and negative keywords let you filter by state, match type, bid and budget. That combination supports both high-level executive sheets and detailed optimization work in the same app.
'%3E%3Cpath d='M51,41a9.978,9.978,0,0,0-7.857,3.835L22.648,34.588a9.69,9.69,0,0,0,0-5.176l20.5-10.247a10.1,10.1,0,1,0-1.791-3.577L20.857,25.835a10,10,0,1,0,0,12.33L41.352,48.412A9.994,9.994,0,1,0,51,41Z' fill='%23383e51'%3E%3C/path%3E%3C/g%3E%3C/svg%3E)
'%3E%3Cpath d='M33,47.645V60.71c.024-.014.05-.018.073-.033l11-7A2,2,0,0,0,45,51.992V40.012Z' fill='%23383e51'%3E%3C/path%3E%3Cpath d='M31,47.645,19,40.011V51.992a2,2,0,0,0,.927,1.688l11,7c.023.015.049.019.073.033Z' fill='%23383e51'%3E%3C/path%3E%3Cpath d='M32,21.693l12-7.634L33.076,7.086a2,2,0,0,0-2.152,0L20,14.059Z' fill='%23383e51'%3E%3C/path%3E%3Cpath d='M12,35.556,0,27.922V39.9A2,2,0,0,0,.927,41.59l11,7c.023.014.049.019.073.033Z' fill='%23383e51' data-color='color-2'%3E%3C/path%3E%3Cpath d='M52,35.556l12-7.634V39.9a2,2,0,0,1-.927,1.687l-11,7c-.023.014-.049.019-.073.033Z' fill='%23383e51' data-color='color-2'%3E%3C/path%3E%3Cpath d='M47,38.914a2,2,0,0,0-.924-1.686L38,32.074V27.922l12,7.634V48.621c-.024-.014-.05-.019-.073-.033L47,46.726Z' fill='%23383e51' data-color='color-2'%3E%3C/path%3E%3Cpath d='M13,33.821l12-7.634L14.076,19.214a2,2,0,0,0-2.152,0L1,26.187Z' fill='%23383e51' data-color='color-2'%3E%3C/path%3E%3Cpath d='M17,38.914a2,2,0,0,1,.924-1.686L26,32.074V27.922L14,35.556V48.621c.024-.014.05-.019.073-.033L17,46.726Z' fill='%23383e51' data-color='color-2'%3E%3C/path%3E%3Cpath d='M32,45.91l12-7.634L33.076,31.3a2,2,0,0,0-2.152,0L20,38.276Z' fill='%23383e51'%3E%3C/path%3E%3Cpath d='M14.076,19.214a2,2,0,0,0-2.152,0L1,26.187l12,7.634,12-7.634Z' fill='%23383e51' data-color='color-2'%3E%3C/path%3E%3Cpath d='M49.924,19.214a2,2,0,0,1,2.152,0L63,26.187,51,33.821,39,26.187Z' fill='%23383e51' data-color='color-2'%3E%3C/path%3E%3Cpath d='M26,27.922,14,35.556V48.621c.024-.014.05-.019.073-.033L17,46.726V38.914a2,2,0,0,1,.924-1.686L26,32.074Z' fill='%23383e51' data-color='color-2'%3E%3C/path%3E%3Cpath d='M27.076,25.138A2,2,0,0,1,28,26.824V30.8l1.848-1.179A4,4,0,0,1,31,29.123V23.428L19,15.794v4.19Z' fill='%23383e51'%3E%3C/path%3E%3Cpath d='M36.924,25.138A2,2,0,0,0,36,26.824V30.8l-1.848-1.179A4,4,0,0,0,33,29.123V23.428l12-7.634v4.19Z' fill='%23383e51'%3E%3C/path%3E%3Cpath d='M33.076,31.3a2,2,0,0,0-2.152,0L20,38.276,32,45.91l12-7.634Z' fill='%23383e51'%3E%3C/path%3E%3C/g%3E%3C/svg%3E)
'%3E%3Cpath d='M50.348,42.573c0-9.411-8.691-12.336-16.348-14.416v-16.1a32.837,32.837,0,0,1,9.363,1.656l2.778,1.11,2.228-5.57L45.584,8.134A38.043,38.043,0,0,0,34,6.046V1H30V6.081c-8.213.594-16.348,4.86-16.348,13.471,0,9.036,8.841,11.732,16.348,13.744V50.074a33.591,33.591,0,0,1-12.006-2.511l-2.683-1.341-2.684,5.367,2.684,1.342c.243.121,5.7,2.792,14.689,3.152V63h4V56.065C44,55.462,50.348,50.3,50.348,42.573Zm-30.7-23.021c0-5.133,5.96-7.016,10.348-7.446V27.071C23.512,25.243,19.652,23.535,19.652,19.552ZM34,50.043V34.393c6.5,1.882,10.348,3.761,10.348,8.18C44.348,48.377,37.873,49.744,34,50.043Z' fill='%23383e51'%3E%3C/path%3E%3C/g%3E%3C/svg%3E)