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

Accounts missing specific campaigns (Sponsored Brands, Display, Video)

If you can see campaigns in Amazon Ads but they're not appearing in Coupler.io:

Currently, Coupler.io supports Sponsored Products campaigns only. Sponsored Brands, Sponsored Display, and Sponsored Video 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 Brands or 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 (within 5%) 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. It's temporary and usually resolves within a few minutes.

What to do:

1. Wait and retry — Wait 2–5 minutes, then manually run your data flow again.

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

3. Schedule off-peak — If scheduling, run your data flow during off-peak hours (late evening or early morning) when Amazon's API is less busy.

This is not a permanent error and should resolve on its own.

"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.