FAQ

chevron-rightCan I pull data from multiple Amazon Ads accounts in one data flow?hashtag

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.

chevron-rightWhat's the maximum date range I can pull?hashtag

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.

chevron-rightWhy is my data different from the Amazon Ads dashboard?hashtag

Small differences (up to 5%) 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.

chevron-rightWhy am I seeing "The requested report is currently being generated" error?hashtag

This means Amazon is still processing your report. It's temporary and usually resolves in 2–5 minutes.

What to do:

  • Wait a few minutes and retry

  • Reduce your date range (shorter ranges process faster)

  • Schedule during off-peak hours (early morning or late evening)

This error will eventually resolve on its own.

chevron-rightCan I pull Sponsored Brands or Sponsored Display campaign data?hashtag

Currently, only Sponsored Products campaigns are supported. Sponsored Brands, Sponsored Display, and Sponsored Video campaigns are not available through the Amazon Ads API integration.

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

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

chevron-rightHow often should I schedule my data flow?hashtag

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.

Avoid scheduling during peak hours (9 AM–5 PM) when Amazon's API is busiest. Off-peak hours (early morning or late evening) are more reliable.

chevron-rightCan I combine Amazon Ads data with other ad channels (Google Ads, Facebook, etc.)?hashtag

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.

circle-info

See the Best Practices section for setup recommendations.

chevron-rightWhat permissions do I need in my Amazon account?hashtag

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.

chevron-rightCan I use macros for dynamic date ranges?hashtag

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.

circle-info

Learn more about macros in the Coupler.io help centerarrow-up-right.

chevron-rightHow long does the first data pull typically take?hashtag

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 API load — During busy hours, processing takes longer

First pulls can take 5–30 minutes. Subsequent scheduled pulls are usually faster. If a pull times out, reduce your date range or number of metrics and try again.

chevron-rightWhat's the difference between "Campaign performance by campaigns" and "Campaign performance by ad groups"?hashtag

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.

chevron-rightCan I send Amazon Ads data to AI tools like Claude or ChatGPT?hashtag

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.

chevron-rightWhy does my data flow keep failing?hashtag

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, or retry during off-peak hours

  4. "Report is being generated" — Wait a few minutes and retry

circle-info

See Common Issues for detailed troubleshooting steps.

Last updated

Was this helpful?