For the complete documentation index, see llms.txt. This page is also available as Markdown.

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.

Last updated

Was this helpful?