Kondado connects your Amazon Ads account to Microstrategy through a Via Kondado connection, so your campaign, keyword, and sales data lands directly in the dashboards your team already uses. You pick the pipelines you need, choose how often they update, and Kondado keeps your Microstrategy reports current on a configurable schedule. Marketing and operations teams can then explore spend, ACOS, ROAS, and attributed sales without writing a single line of code.
Kondado brings 27 Amazon Ads pipelines and 1,247 fields into Microstrategy through a Via Kondado connection, with no intermediate databases and no complex setup. You decide the update frequency, from every 5 minutes to daily, and your Microstrategy dashboards stay aligned with advertising performance across Sponsored Products, Sponsored Brands, Sponsored Display, Sponsored TV, and Amazon DSP.
Each item below is automatically replicated by Kondado from Amazon Ads into Microstrategy — 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 the Sponsored Products report pipeline in Microstrategy, you can follow ACOS and ROAS by campaign, keyword, and search term, and spot the terms that quietly drain budget. The Sponsored Brands report pipeline adds new-to-brand orders and purchases, so brand campaigns can be judged on more than clicks. The Amazon DSP report pipeline brings add_to_cart and conversion metrics together with third-party fees, letting you compare programmatic spend against retail media results on one dashboard. Combine them with the Metadata: Portfolios pipeline to see budget pacing across accounts.
Try out all the features for free for 14 days
How to create Amazon Ads dashboards in Microstrategy
Visualize your data automatically — no spreadsheet exports or custom scripts.
1
Connect Amazon Ads as a data source
Sign in to Kondado, add Amazon Ads as your data source, and authorize the advertising accounts you want to report on. Pick the pipelines that match your reporting goals, from campaign metadata to Sponsored Products performance.
2
Select Microstrategy as your destination
Choose Microstrategy as the destination and connect it through the Via Kondado connection. No intermediate database is needed, so your Amazon Ads data becomes available to Microstrategy after the first load.
3
Build dashboards and configure data refresh
Create your dossiers and visualizations in Microstrategy, then choose how often Kondado refreshes the data: every 5 minutes, hourly, daily, or another interval. Share the finished dashboards with your marketing and operations teams.
Try out all the features for free for 14 days
Access Amazon Ads data in Microstrategy 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 Microstrategy automatically
How do I connect Amazon Ads to Microstrategy with Kondado?▼
Start by signing in to Kondado and adding Amazon Ads as your data source, then authorize the advertising accounts you want to track. Choose the pipelines that match the questions your team asks, such as the Sponsored Products report or the Metadata: Sponsored Products - campaigns pipeline. Kondado then makes that data available to Microstrategy through a Via Kondado connection, so you can start building visualizations without any code.
Which Amazon Ads metrics can I track in Microstrategy dashboards?▼
You can chart impressions, clicks, cost, attributed sales, orders, ACOS, and ROAS by account, campaign, ad group, ad, keyword, and search term. The Sponsored Products report pipeline also carries 1, 7, 14, and 30-day attribution windows, which is useful for comparing short and long conversion cycles. Sponsored TV and Amazon DSP pipelines add reach, frequency, new-to-brand, and add_to_cart metrics for upper-funnel views.
How often does my Amazon Ads data update in Microstrategy?▼
You set the refresh frequency yourself when you configure the connection, choosing from every 5 minutes, every 15 minutes, hourly, daily, or another interval that fits your reporting rhythm. Metrics that move during the day, like spend and clicks, can refresh more often, while slower metadata pipelines can run once a day. Your Microstrategy dossiers then show the latest available numbers on that schedule.
Are there ready-made Microstrategy dashboards for Amazon Ads?▼
Kondado does not include pre-built Microstrategy dashboards for this source, so you design the dossiers and visualizations around your own questions. A common starting point is a campaign performance dashboard with ACOS and ROAS by campaign, plus a second page that ranks search terms by spend and sales. Because every field from the 27 pipelines is available, you can shape each view around the decisions your team actually makes.
Can I share Amazon Ads dashboards with clients or teammates in Microstrategy?▼
Yes. Once your dossiers are built, you publish them through Microstrategy's own sharing and distribution options, so account managers, media buyers, and clients see the same numbers. Many teams schedule a weekly performance summary and keep an interactive dossier open for day-to-day checks. If a stakeholder prefers spreadsheets, the same Amazon Ads data can also be sent to Google Sheets from Kondado.
What is the Via Kondado connection and why does it matter for Microstrategy?▼
Via Kondado is the direct path Kondado uses to deliver Amazon Ads data to your Microstrategy environment, with no intermediate database to maintain. That means fewer moving parts for your team and a shorter path from a new pipeline to a working visualization. You simply select the pipelines you need, and Microstrategy reads from the Via Kondado connection.
Which Amazon Ads pipelines should I start with for a first dashboard?▼
Most teams begin with the Sponsored Products report pipeline for keyword and search term performance, then add the Metadata: Sponsored Products - campaigns pipeline to group results by budget and bidding strategy. If brand campaigns matter, add the Sponsored Brands report pipeline for new-to-brand orders. From there you can layer in the Metadata: Portfolios pipeline to compare budget pacing across accounts.
Can I combine Amazon Ads data with other sources in Microstrategy?▼
Yes. Kondado can also deliver data to BigQuery, PostgreSQL, or Power BI, and teams often blend advertising spend with sales or inventory figures in Microstrategy to see return on ad spend against actual revenue. Keeping Amazon Ads next to those numbers turns campaign metrics into business results.
'%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)