Amazon Ads

Amazon Ads is a powerful advertising platform for sellers and vendors on Amazon. With Coupler.io, you can automatically pull campaign performance data, search terms, targeting information, and product reports into your spreadsheets, BI tools, and databases on a schedule.

Why connect Amazon Ads to Coupler.io?

• Centralized reporting — Pull data from multiple Amazon Ads accounts into one destination

• Automated updates — Schedule daily, weekly, or monthly refreshes without manual exports

• Flexible report types — Access campaign, ad group, search term, targeting, and product performance reports

• Multi-destination support — Send data to Google Sheets, Excel, BigQuery, Looker Studio, Power BI, or AI destinations like Claude and ChatGPT

Prerequisites

Before you connect Amazon Ads to Coupler.io, make sure you have:

• An active Amazon Ads account with advertiser access

• Permission to view reports and campaign data in your Amazon Ads account

• A destination ready (Google Sheets, Excel, BigQuery, Power BI, Looker Studio, or an AI destination like Claude)

Quick start

We recommend starting with a Campaign performance by campaigns report for a single account and a 7-day date range. This gives you a quick win to test the data flow before scaling to larger date ranges or multiple accounts.

How to connect

1

Sign in to Coupler.io and create a new data flow. Select Amazon Ads as your source.

2

Authorize with Amazon. Click "Connect" and you'll be redirected to Amazon's login page. Sign in with your Amazon account and grant Coupler.io permission to access your advertising data. You'll be returned to Coupler.io once authorized.

3

Select your Amazon Ads account(s). Choose the advertiser accounts from which you want to pull data. You can select one or multiple accounts — if pulling from several, Coupler.io will append the data together.

4

Choose a report type. Select from available report types like "Campaign performance by campaigns," "Search terms report," or "Advertised products report."

5

Set your report period. Use the date pickers to define your start and end dates. Note: Amazon Ads API allows a maximum of 31 consecutive days per request. For longer periods, set a date range within this limit or use the "Totals only" split option.

6

Choose your metrics. Select which metrics to include in your report (e.g., impressions, clicks, spend, conversion value). Different report types offer different metric options.

7

Pick your destination. Choose where your data will land — Google Sheets, Excel, BigQuery, Power BI, Looker Studio, or an AI destination like Claude or ChatGPT.

8

Run your data flow. Click "Run" to execute a manual test. Once successful, you can schedule the data flow to run automatically on your preferred cadence.

A successful manual run is required before you can schedule your data flow to run automatically.

Amazon Ads data overview

Amazon Ads data flows give you access to performance metrics across different report levels and ad types. Understanding what data is available helps you choose the right report type for your analysis.

Report types and data levels

Report Type	Data Level	Account Coverage	Best For
Campaign performance by campaigns	Campaign	Single or multiple accounts	Comparing campaign-level ROI
Campaign performance by ad groups	Ad group	Single or multiple accounts	Finding underperforming ad groups
Campaign performance by campaign placement	Placement	Single or multiple accounts	Understanding ad placement effectiveness
Targeting report	Keyword/target	Single or multiple accounts	Optimizing bids and match types
Search terms report	Search query	Single or multiple accounts	Discovering new keywords and negative keywords
Advertised products report	Product	Single or multiple accounts	Identifying top and bottom product performers
Sponsored products purchased product report	Product (post-purchase)	Single or multiple accounts	Attributing sales to advertised products
Sponsored brands purchased product report	Product (post-purchase)	Single or multiple accounts	Measuring branded campaign ROI

Available metrics

Performance metrics

Metric	Description	Report Types
Impressions	Number of times your ads were shown	All
Clicks	Total clicks on your ads	All
Spend	Total advertising spend in the period	All
Sales	Total sales from attributed conversions	Campaign, ad group, placement, product reports
Units sold	Number of units sold from ad clicks	Campaign, ad group, product reports
ACoS	Advertising Cost of Sale (spend / sales)	Campaign, ad group, placement, search terms
CTR	Click-through rate (clicks / impressions)	Campaign, ad group, placement, targeting
CPC	Cost per click (spend / clicks)	Campaign, ad group, placement, targeting
Conversion rate	Conversions as % of clicks	Campaign, ad group, search terms
New ASIN purchases	Sales from products not previously purchased	Campaign, ad group

Engagement and efficiency metrics

Metric	Description	Report Types
Impressions share	Your share of impressions in a category	Campaign, ad group
Conversion value	Total monetary value of conversions	Product reports
Attributed conversions	Conversions linked to your ads	Search terms, product reports
Units ordered	Total units ordered from your ads	Purchased product reports

Targeting and query metrics (search terms & targeting reports)

Metric	Description	Report Types
Match type	Keyword match type (exact, phrase, broad)	Targeting report
Bid	Current bid amount for the keyword/target	Targeting report
Search term	Customer's exact search query	Search terms report

Common metric combinations

Campaign ROI analysis: Spend, sales, ACoS, CTR (shows profitability and efficiency)

Ad group optimization: Impressions, clicks, CPC, conversion rate, units sold (helps find underperformers)

Search term discovery: Search term, impressions, clicks, spend, conversions (identify new keyword opportunities)

Product performance: Advertised product, units sold, conversion value, ACoS (which products drive revenue)

Placement effectiveness: Campaign placement, impressions, clicks, CTR, spend (compare placement channels)

Use cases by role

PPC Managers

Track campaign and ad group performance across multiple Amazon Ads accounts. Pull daily campaign reports to identify underperforming ad groups, monitor ACoS trends, and analyze search term queries to refine bidding and negative keyword strategies. Use Append transformations to combine data from multiple accounts, or Join to correlate campaign performance with your product data.

E-commerce Operations

Monitor product-level performance using the Advertised products and Sponsored products purchased product reports. Track which products drive sales versus which consume budget. Use Aggregate transformations to roll up product metrics by category or SKU family, then compare against your inventory data to optimize product mix and promotional spend.

Finance & Analytics

Generate weekly or monthly ROI summaries by pulling campaign performance reports with ACoS and conversion metrics. Use BigQuery or Looker Studio as your destination to build dashboards showing spend trends, campaign profitability, and budget allocation across accounts. Schedule monthly pulls to automate financial reporting.

Marketing Executives

Use Coupler.io to feed Amazon Ads data into Power BI or Looker Studio for executive dashboards. Pull monthly campaign summaries showing top campaigns by spend and sales. Combine Amazon Ads data with your other ad channel data (Google Ads, Facebook Ads) using Append transformations for a unified multi-channel view.

Platform-specific notes

• 31-day maximum: The Amazon Ads API limits date ranges to 31 consecutive days. If you need longer periods, either schedule weekly pulls or use "Totals only" split mode for a single aggregated record.

• Account coverage: When you select multiple Amazon Ads accounts, data is pulled separately for each and appended together in your destination. Add an "account" or "profile" column to distinguish between accounts.

• Report generation time: Amazon generates reports asynchronously, and processing can take anywhere from a few minutes up to about 3 hours depending on report size and Amazon's own queue. If you see a "report is currently being generated" message, this is expected — re-running the data flow doesn't start a new report, it continues checking the one already in progress.

• Sponsored Brands and Display coverage: Coupler.io supports Sponsored Products campaigns (all report types) and Sponsored Brands campaigns via the "Sponsored brands purchased product report." Sponsored Display campaigns are not yet included; this is a known limitation with Amazon's API availability.

• Data refresh latency: Amazon Ads data is typically available within 24–48 hours of ad activity. Schedule your data flows accordingly if you need near-real-time reporting.

Amazon Ads common issues

Connection issues

"No accounts" showing after connecting

If you see "No accounts" or your Amazon Ads accounts aren't appearing in the account selector:

1. Verify your Amazon account permissions — Make sure your Amazon user account has advertiser access and is not restricted to read-only roles.

2. Re-authorize the connection — Disconnect and reconnect your Amazon Ads account. Click the gear icon next to your connection, select "Revoke," then create a new connection and re-authenticate.

3. Check account country codes — If you operate in multiple Amazon regions (US, EU, etc.), each region may require a separate account setup. The connector now includes country code support; ensure each account has the correct country designation.

4. Wait after account setup — If you recently created a new Amazon Ads account, it can take a few hours to appear in Coupler.io. Try reconnecting later.

If accounts still don't appear, reach out to support with a screenshot of your Amazon Ads dashboard showing your accounts.

401 Unauthorized error after successful connection

If you see a 401 error when running a data flow:

1. Your access token has expired — Reconnect your Amazon Ads account. Go to your data flow, click the connection settings, and re-authenticate with Amazon.

2. Check account permissions — Verify that the Amazon user account you connected still has advertiser access. If permissions were recently changed, re-authenticate.

3. Try a manual run first — Before scheduling, always run the data flow manually to ensure the connection is fresh.

Missing data

Sponsored Display campaigns aren't appearing in Coupler.io

Coupler.io supports Sponsored Products campaigns (all report types) and Sponsored Brands campaigns via the "Sponsored brands purchased product report." Sponsored Display campaigns are not yet available through the Amazon Ads API integration. This is a limitation of Amazon's API, not Coupler.io.

Workaround: If you need Sponsored Display data, export reports manually from your Amazon Ads dashboard and upload them to your destination, then use Append transformations to combine with Coupler.io data.

We're tracking requests for expanded campaign type support—reach out if this is critical for your workflow.

Search terms or keyword data is incomplete or missing

If your search terms report is showing fewer rows than expected:

1. Check your date range — Amazon only returns search term data for the last 95 days. If your date range is older, you'll see no results.

2. Verify you have query volume — Search term reports only show terms that generated clicks or impressions. If you have very low traffic in your date range, results may be sparse.

3. Use the correct report type — Ensure you've selected "Search terms report," not "Targeting report" (which shows keywords you've bid on, not actual customer searches).

Product-level data not matching Amazon Ads dashboard

If your "Advertised products report" numbers don't match the Amazon Ads UI:

1. Verify the report type — Ensure you're pulling "Advertised products report" (product-level metrics) vs. "Sponsored products purchased product report" (post-purchase attribution).

2. Check your date range — Confirm your Coupler.io date range matches the Amazon dashboard. The Amazon Ads UI may show data in a different timezone.

3. Filter matching — If you applied advanced filters in Coupler.io, the filtered data will naturally be lower than the dashboard total. Review your filters.

4. Contact support — If metrics still don't align after checking above, provide a side-by-side screenshot of both your Coupler.io report and the Amazon Ads dashboard for the same date range and ad group.

Permission errors

"Access denied" or "Insufficient permissions" error

If you see permission-related errors:

1. Verify advertiser role — Your Amazon account must have at least the "Advertiser" role to access reports. Campaign managers with read-only access cannot pull data via API.

2. Check account status — Ensure your Amazon Ads account is active and not suspended or in dispute status.

3. Re-authenticate — Disconnect and reconnect your Amazon Ads account. Old tokens may have permission issues.

If you manage accounts on behalf of clients, make sure you're logged in with the account that has delegated access to those client accounts.

Data discrepancies

Data in Coupler.io doesn't match Amazon Ads dashboard

Small differences are normal due to report processing delays. If you see larger discrepancies:

1. Check data freshness — Amazon Ads data takes 24–48 hours to finalize. If you're pulling data from yesterday or today, the numbers may change as Amazon processes transactions.

2. Verify date range — Ensure your Coupler.io date range exactly matches the dashboard (same timezone, same start/end dates).

3. Compare report types — Different report types (campaign vs. ad group) may show slightly different totals due to data aggregation differences.

4. Run a manual test — Run your data flow manually, then immediately check the Amazon Ads dashboard for the same period to compare.

If discrepancies persist, contact support with screenshots showing both the Coupler.io data and the Amazon dashboard for comparison.

Rate limits and API errors

"The requested report is currently being generated" error

This error means Amazon is still processing your report request. Amazon's own processing time varies — it's usually done within a few minutes, but can take up to about 3 hours for large or complex reports.

What to do:

1. Wait and retry — Re-running the data flow doesn't create a new report request; Coupler.io recognizes the same request and continues checking the report already in progress.

2. Reduce your date range — If this happens frequently, try pulling shorter date ranges (7–14 days instead of 31 days) to reduce processing time.

This is not a permanent error and should resolve once Amazon finishes generating the report.

"Date range exceeds maximum (31 days)" error

Amazon Ads API has a strict 31-day maximum for any single request.

How to fix:

1. Reduce your date range — Set your date range to 31 days or fewer.

2. Use "Totals only" split — Instead of daily breakdown, select "Totals only" for a single aggregated row. This works with longer date ranges if you pull weekly.

3. Schedule weekly pulls — Create a data flow that pulls the last 7 days weekly. You'll get a continuous history without hitting the 31-day limit.

If you absolutely need historical data beyond 95 days, export it manually from Amazon and append it in your destination.

"Request to Amazon Ads API has failed" error

This is a general API failure, usually temporary. Possible causes:

1. Amazon API downtime — Check the Amazon Ads service status. Try again in a few minutes.

2. Timeout on large reports — If you're pulling a very large report (thousands of rows, long date range), the API may timeout. Reduce your date range or number of metrics.

3. Network connectivity — Ensure your Coupler.io account has stable internet.

4. Retry the data flow — Click "Run" again. Many temporary API issues resolve on retry.

If the error persists after 2–3 retries, contact Coupler.io support with your data flow URL and the error message.

Amazon Ads FAQ

Can I pull data from multiple Amazon Ads accounts in one data flow?

Yes. During setup, select multiple accounts in the "Accounts" step. Coupler.io will pull data from all selected accounts and append them together in your destination. To keep account data separate, add an "account" or "profile" ID column so you can filter by account in your destination.

What's the maximum date range I can pull?

The Amazon Ads API allows a maximum of 31 consecutive days per request. If you need longer periods:

• Create a data flow with a 31-day range, or

• Use "Totals only" split and schedule weekly pulls to build rolling history

Historical data beyond 95 days is not available via the API and must be exported manually from your Amazon Ads account.

Why is my data different from the Amazon Ads dashboard?

Small differences are normal due to report processing delays. Larger discrepancies usually mean:

1. Data latency — Allow 24–48 hours for Amazon to finalize data. Yesterday's numbers may still be changing.

2. Date range mismatch — Ensure your Coupler.io date range exactly matches the dashboard (same timezone, same start/end dates).

3. Report type difference — Campaign and ad group reports may show different totals due to data aggregation.

Run a manual refresh, then immediately check the Amazon dashboard for the same period to compare.

Why am I seeing "The requested report is currently being generated" error?

This means Amazon is still processing your report. Processing time varies — it's usually done within a few minutes, but large or complex reports can take up to about 3 hours.

What to do:

• Wait and retry — this doesn't create a new report request, Coupler.io continues checking the one already in progress

• Reduce your date range (shorter ranges process faster)

This error will eventually resolve on its own.

Can I pull Sponsored Brands or Sponsored Display campaign data?

Sponsored Products (all report types) and Sponsored Brands are both supported — use the "Sponsored brands purchased product report" for Sponsored Brands data. Sponsored Display campaigns are not yet available through the Amazon Ads API integration.

Workaround: For Sponsored Display, export reports manually from your Amazon Ads dashboard and upload to your destination, then use Append transformations to combine with your Coupler.io data for a unified view.

We're tracking requests for expanded support—let us know if this is critical for your workflow.

How often should I schedule my data flow?

It depends on your use case:

• Daily: For active campaign optimization and real-time ROI tracking. Note: data is 24–48 hours delayed, so "daily" pulls yesterday's finalized data.

• Weekly: For campaign reviews, search term analysis, and budget planning.

• Monthly: For executive summaries and financial reporting.

Can I combine Amazon Ads data with other ad channels (Google Ads, Facebook, etc.)?

Yes! Use the Append transformation to combine data from multiple sources. For example:

1. Create separate data flows for Amazon Ads, Google Ads, and Facebook Ads

2. Set them all to write to the same destination table

3. Use Append to stack the rows together

4. Add a "source" or "channel" column to distinguish between platforms

This gives you a unified multi-channel ad performance view in one table.

See the Best Practices section for setup recommendations.

What permissions do I need in my Amazon account?

Your Amazon user account must have Advertiser access (not read-only). This typically means having one of these roles:

• Account owner

• Advertising manager

• Campaign manager (with report access)

Read-only or restricted roles won't have permission to pull data via API. If you manage client accounts, ensure you have delegated advertiser access set up by the account owner.

Can I use macros for dynamic date ranges?

Yes. The Amazon Ads connector supports macros for the Start Date and End Date fields. For example:

• {{today}} — Today's date

• {{yesterday}} — Yesterday's date

• {{30daysago}} — 30 days back

Note: Allow 24–48 hours for data to finalize. For most use cases, use {{7daysago}} or later to ensure accurate, finalized data.

Learn more about macros in the Coupler.io help center.

How long does the first data pull typically take?

It depends on:

• Data volume — Large accounts with hundreds of campaigns take longer

• Report type — Search terms reports often take longer than campaign summaries

• Date range — Longer ranges (31 days) take longer than short ranges (7 days)

• Amazon's own report queue — processing time is ultimately decided by Amazon, not Coupler.io

Most first pulls complete within a few minutes to about 30 minutes, but Amazon's report generation can occasionally take longer — up to about 3 hours for large or complex reports. If a pull is still running, let it continue rather than repeatedly re-triggering it; if it times out, reduce your date range or number of metrics and try again.

What's the difference between "Campaign performance by campaigns" and "Campaign performance by ad groups"?

Campaign performance by campaigns shows metrics rolled up to the campaign level (one row per campaign)—good for high-level ROI analysis.

Campaign performance by ad groups shows metrics at the ad group level (one row per ad group within each campaign)—good for finding underperforming ad groups within campaigns.

Choose based on your analysis depth: use campaigns for executive summaries, ad groups for detailed optimization.

Can I send Amazon Ads data to AI tools like Claude or ChatGPT?

Yes! Coupler.io supports sending data to AI destinations including Claude, ChatGPT, Cursor, Gemini, Perplexity, and OpenClaw. This lets you use AI to analyze your campaign performance, summarize trends, and generate insights directly from your Amazon Ads data.

Simply select your preferred AI tool as the destination during setup.

Why does my data flow keep failing?

Common reasons:

1. Date range exceeds 31 days — Reduce to 31 days or fewer

2. 401 Unauthorized error — Re-authenticate your Amazon connection

3. API timeout — Reduce your date range or metrics, then retry

4. "Report is being generated" — Wait and retry; this can take up to about 3 hours for large reports

See Common Issues for detailed troubleshooting steps.