From Amazon Ads to SQL Server: managed, scheduled, no code.
Creating a pipeline that sends data from Amazon Ads to SQL Server databases takes only a few minutes with Kondado. And the whole integration from Amazon Ads to SQL Server is managed and executed by our platform. With Kondado, you can focus on extracting value from Amazon Ads data and combining it with other data in your SQL Server database
To send Amazon Ads data to SQL Server, connect your Amazon Ads account on Kondado, choose the pipelines you need, and set SQL Server as the destination. Kondado handles the extraction and loading, so campaign, keyword, ad group, and performance data arrive in your database on a schedule you configure. You can select Sponsored Products, Sponsored Brands, Sponsored Display, Sponsored TV, and Amazon DSP pipelines, then query the replicated data directly in SQL Server for custom reporting and analysis.
Kondado replicates Amazon Ads data to SQL Server on a user-configured schedule. It connects the Amazon Ads data source, lets you select from 27 pipelines and 1,247 fields, and loads the data into SQL Server so your team can build custom dashboards, join advertising data with other business data, and keep analysis current.
Use the Sponsored Products report pipeline to bring impressions, clicks, cost, sales, purchases, ACOS, ROAS, and attribution metrics into SQL Server for keyword and search term analysis. The Sponsored Brands report pipeline adds campaign, ad group, ad, keyword, product, and placement performance, so you can compare brand campaigns against product campaigns in custom queries. Metadata: Sponsored Products - campaigns gives you budget, bidding strategy, start and end dates, and portfolio context, which helps you build budget pacing and campaign health views alongside your performance data.
Try out all the features for free for 14 days
Replicated to SQL Server
Amazon Ads data available for SQL Server
Tables Kondado writes into your SQL Server, on a schedule you control.
27
available pipelines
1247
extractable fields
SQL Server
Destination
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.
Sync data automatically — no code, no manual exports.
1
Connect Amazon Ads on Kondado
Add your Amazon Ads account as a data source in Kondado and select the advertising profiles you want to replicate.
2
Configure SQL Server destination
Enter your SQL Server host, database, and credentials, then test the connection so Kondado can write the replicated Amazon Ads data to your database.
3
Select pipelines and update schedule
Choose the Amazon Ads report and metadata pipelines you need, then set the replication schedule that fits your reporting cycle. After the first load, connect SQL Server to Power BI or Looker Studio to build custom dashboards.
Try out all the features for free for 14 days
Hundreds of data-driven companies trust Kondado
Why Kondado?
Focus on extracting value from your data and leave the rest to us
Answers about sending Amazon Ads data to SQL Server automatically
How does Kondado move Amazon Ads data into SQL Server?▼
Kondado connects to your Amazon Ads account, reads the pipelines you select, and writes the resulting rows to your SQL Server destination. You provide the SQL Server connection details and choose which pipelines to include, then Kondado runs the replication on the schedule you set. This keeps your advertising data available for SQL queries without manual exports.
Which Amazon Ads pipelines can I replicate to SQL Server?▼
You can replicate performance pipelines such as the Sponsored Products report, Sponsored Brands report, Sponsored Display report, Sponsored TV report, and Amazon DSP report. You can also replicate metadata pipelines for campaigns, ad groups, keywords, targets, portfolios, and advertising accounts. This mix supports both performance analysis and campaign configuration review in SQL Server.
How often does Kondado update Amazon Ads data in SQL Server?▼
Updates run on a schedule you configure, with options such as every 5 minutes, every 15 minutes, hourly, or daily. The schedule controls when Kondado checks the selected Amazon Ads pipelines and loads new or changed data into SQL Server. You can align the cadence with your reporting needs and SQL Server processing windows.
What format does Amazon Ads data have in SQL Server?▼
Kondado writes the selected Amazon Ads data as structured rows in your SQL Server database, with fields that match each pipeline's schema. Performance pipelines include date, account, campaign, ad group, keyword, and metric columns, while metadata pipelines include IDs, names, states, budgets, bids, and dates. You can query those fields directly with T-SQL and join them to your own SQL Server data.
Can I combine Amazon Ads data with other sources in SQL Server?▼
Yes. Once Amazon Ads data is in SQL Server, you can join it with CRM, ERP, inventory, or finance data that you also store there. You can also send other source data to PostgreSQL or BigQuery for separate analysis, but SQL Server remains the place where the combined queries run. This helps you compare ad spend with revenue, margin, or stock levels.
Can I build custom dashboards from Amazon Ads data in SQL Server?▼
Yes. You can connect SQL Server to Power BI or Looker Studio and build custom dashboards from the replicated Amazon Ads data. Use the report pipelines for performance trends and the metadata pipelines for campaign, budget, and targeting context. You can also export query results to Google Sheets for sharing.
'%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)
