From Amazon Ads to PostgreSQL: managed, scheduled, no code.
Creating a pipeline that sends data from Amazon Ads to PostgreSQL databases takes only a few minutes with Kondado. And the whole integration from Amazon Ads to PostgreSQL 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 PostgreSQL database
To send Amazon Ads data to PostgreSQL, you connect your Amazon Ads account as a data source in Kondado and select the pipelines you need, such as Sponsored Products report or Sponsored Brands campaigns. Kondado then replicates that data to your PostgreSQL database on a configurable schedule, from every 5 minutes to daily. You can choose from metadata pipelines for accounts, portfolios, campaigns, ad groups, keywords, and targets, plus report pipelines for performance metrics. This gives you direct access to campaign performance, keyword metrics, and advertising metadata inside your own database.
Kondado replicates Amazon Ads data to PostgreSQL automatically on a schedule you set, covering 27 pipelines and 1,247 fields across Sponsored Products, Sponsored Brands, Sponsored Display, Sponsored TV, and Amazon DSP. You get impressions, clicks, cost, sales, ACOS, ROAS, and campaign metadata in your PostgreSQL, ready for custom analysis and reporting.
The Sponsored Products report pipeline delivers daily rows by campaign, ad group, ad, keyword, and search term, with impressions, clicks, cost, sales, and ACOS. The Sponsored Brands report pipeline provides campaign, ad group, ad, keyword, product, and placement metrics including new-to-brand orders. The Amazon DSP report pipeline brings advertiser-level event and conversion metrics such as add_to_cart and ROAS. With this data in PostgreSQL, you can build custom dashboards that combine ad spend with sales data from your ecommerce platform, or join keyword performance with inventory levels to optimize bids.
Try out all the features for free for 14 days
Replicated to PostgreSQL
Amazon Ads data available for PostgreSQL
Tables Kondado writes into your PostgreSQL, on a schedule you control.
27
available pipelines
1247
extractable fields
PostgreSQL
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 as a data source
In Kondado, add Amazon Ads as a data source and authenticate with your advertising account. This grants Kondado access to your profiles, campaigns, and reports.
2
Configure your PostgreSQL destination
Provide your PostgreSQL connection details, including host, port, database, user, and password. Kondado will write data to the schema you specify.
3
Select pipelines and set schedule
Choose the Amazon Ads pipelines you need, such as Sponsored Products report or Sponsored Brands campaigns, and set the update frequency from every 5 minutes to daily. Kondado then replicates the data to PostgreSQL on that schedule.
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 PostgreSQL automatically
How does Kondado send Amazon Ads data to PostgreSQL?▼
Kondado connects to your Amazon Ads account as a data source, extracts the pipelines you select, and writes the data to your PostgreSQL database on a configurable schedule. You authenticate once, choose the pipelines, and set the update frequency. The data lands in PostgreSQL as structured rows, ready for SQL queries.
What Amazon Ads data can I replicate to PostgreSQL?▼
You can replicate 27 pipelines and 1,247 fields, including metadata for advertising accounts, portfolios, Sponsored Products campaigns, keywords, and targets, plus performance reports for Sponsored Products, Sponsored Brands, Sponsored Display, Sponsored TV, and Amazon DSP. The reports include metrics like impressions, clicks, cost, sales, ACOS, ROAS, and attribution windows. This covers both campaign structure and performance data.
How often does Kondado update Amazon Ads data in PostgreSQL?▼
Kondado updates data on a configurable schedule, from every 5 minutes to daily, depending on your needs. You can set different schedules for different pipelines if you want. This ensures your PostgreSQL database stays current with the latest Amazon Ads performance.
What format does the Amazon Ads data take in PostgreSQL?▼
Each pipeline writes to its own set of rows in PostgreSQL, with columns matching the fields defined in the pipeline. For example, the Sponsored Products report pipeline includes columns for date, campaign_id, ad_group_id, keyword, impressions, clicks, cost, sales, and ACOS. You can query these rows directly with SQL and join them with your own data.
Can I combine Amazon Ads data in PostgreSQL with other sources?▼
Yes, you can replicate data from other sources like Google Analytics or your ecommerce platform into the same PostgreSQL database and join them with Amazon Ads data. You can also send Amazon Ads data to BigQuery, Google Sheets, or Power BI for further analysis. This lets you build a unified view of your advertising and business performance.
Do I need to know SQL to use Amazon Ads data in PostgreSQL?▼
While SQL knowledge helps, you can also connect PostgreSQL to visualization tools like Looker Studio or Power BI to build dashboards without writing queries. Kondado handles the data replication, so you can focus on analysis. Many users start with basic SQL to explore the data and then move to dashboards.