Why isn't my Amazon Ads data loading?

If your Amazon Ads Optimiser dashboard is not displaying data — or is showing incomplete, stale, or missing metrics — this article covers the most common causes and how to resolve each one.

Work through the sections below in order. Most issues are resolved by the first three fixes.

Waiting screen stuck on 'Processing'

Amazon reports take time to generate, and the first fetch after connecting an account can feel especially slow. A typical first-time fetch completes in roughly four minutes, but on busy days it can take up to 45 minutes.

This is normal behaviour. The page auto-reloads once data is ready.

1. Leave the browser tab open and wait at least 30 minutes.
2. If you closed the tab, open your dashboard again — if the data has arrived, it will display immediately.
3. Do not disconnect or reconnect the account while the initial fetch is still in progress. Give it a full 45 minutes before taking further action.

If data still has not loaded after one hour, move to the next section.

Dashboard shows no data after one hour

Three things can cause a completely empty dashboard after the initial waiting period has passed.

OAuth token expired or revoked

When you first connect your Amazon Advertising account, 1smart.link receives an OAuth token that grants access to your advertising data. This token can expire or be revoked if you changed your Amazon password, adjusted third-party app permissions, or if Amazon's auth service encountered an error.

1. Click the account dropdown in the top-right corner of the dashboard.
2. Select Connect another account.
3. Choose the same Amazon Advertising profile you originally connected.
4. Complete the authorisation flow. This refreshes the OAuth token.
5. Return to the dashboard and wait a few minutes for data to begin loading.

Amazon report generation failed

On rare occasions, Amazon's own reporting service fails to generate the report that 1smart.link requested. This is outside the platform's control.

1. Reconnect the account using the same steps listed above. Reconnecting triggers a fresh report request.
2. If the dashboard remains empty after another hour, contact support (details at the bottom of this article).

No advertising activity in the last 30 days

The Optimiser pulls data from the most recent 30-day window. If your account had no active campaigns, no impressions, and no spend during that period, there is simply no data to display.

1. Confirm in Amazon Seller Central or the Amazon Ads console that you have at least one campaign that ran within the last 30 days.
2. If you recently launched your first campaign, wait for the next daily data cycle (described below) and check again.

Dashboard shows Ad Spend but Total Sales, Sessions, or Buy Box show dashes

This means your Amazon Advertising account is connected, but your Seller Central (SP-API) account is not. Ad Spend and other advertising metrics come from the Advertising API, while Total Sales, Sessions, Buy Box percentage, and TACoS come from the SP-API via Seller Central.

1. Click the account dropdown in the top-right corner of the dashboard.
2. Select Connect Seller Central.
3. Complete the SP-API OAuth authorisation flow.
4. Return to the dashboard. TACoS, Sessions, Buy Box, and organic metrics should populate within a few minutes.

Note: For a detailed walkthrough of the SP-API connection process, see Article #38.

Data is stale (older than 24 hours)

1smart.link refreshes your advertising and seller data on a daily schedule using a two-stage process:

Stage	What happens	When it runs
Stage 1	Creates report requests with Amazon	06:00 IST
Stage 2	Downloads and processes the reports	Hourly from 07:00 to 12:00 IST

Under normal conditions, your dashboard data is refreshed by midday IST every day.

If your data is more than 24 hours old, one of these daily jobs may have failed.

1. Reconnect the account (account dropdown → Connect another account → re-authorise the same profile). This triggers an immediate fetch outside the normal schedule.
2. Wait 30–45 minutes for the new data to arrive.
3. If the data remains stale after reconnecting, contact support. The backend team can inspect the cron log for your account and identify the failure.

New campaigns or keywords not showing up

Campaign and keyword data is synced during the daily Stage 2 run, not in real time. If you created a new campaign, added new keywords, or restructured ad groups earlier in the day, those changes will not appear until the next day's data cycle completes.

1. Wait until after midday IST the following day.
2. Open the dashboard and confirm the new campaigns or keywords are now visible.
3. If they still do not appear after two full daily cycles, reconnect the account to force a fresh sync. If that does not help, contact support.

Suggestions not updating after accepting or rejecting

When you accept or reject a suggestion, the backend processes the change immediately. However, the dashboard UI sometimes retains its previous state until the page is refreshed.

1. Press F5 (or Cmd + R on Mac) to reload the page.
2. Check the suggestion list again — it should now reflect your most recent actions.

This is a display issue only. Your accepted changes have already been sent to Amazon, and rejected suggestions have already been logged.

'No pending suggestions' message on every tab

Seeing this message does not necessarily indicate a problem. There are three common reasons.

All suggestions have been actioned

If you have already accepted, rejected, or snoozed every suggestion the engine generated, the queue is simply empty. This is a sign that your account is well-tuned. New suggestions will appear after the next daily data cycle if the engine identifies further optimisation opportunities.

Very low ad spend

The engine needs a minimum volume of click and spend data to produce statistically meaningful suggestions. If your account has very low daily spend, it may take several data cycles before enough evidence accumulates.

1. Continue running your campaigns at your current budget.
2. Check back after a few daily cycles to see if suggestions have appeared.

Active rules are filtering out suggestions

If you have configured rules in the Rule Engine that conflict with potential suggestions, those suggestions are automatically suppressed to avoid contradictions.

1. Review your active rules under the Rule Engine section of the dashboard.
2. Consider whether any rules are overly broad and might be filtering out useful suggestions.
3. If you have moderate spend and no suggestions have appeared for several consecutive days despite active campaigns, contact support to check for a misconfiguration.

Error when clicking Accept on a suggestion

When you accept a suggestion, 1smart.link sends the change to Amazon's API. Occasionally, Amazon returns an error. The specific error code tells you what went wrong.

401 — Token expired

Your OAuth token has expired. Reconnect the account:

1. Click the account dropdown → Connect another account → re-authorise the same profile.
2. Return to the suggestion and try accepting it again.

425 — Duplicate negative already exists

Amazon is reporting that the negative keyword or negative target you are trying to add already exists in the campaign. The suggestion is stale.

1. It is safe to reject this suggestion — the negative is already in place.
2. No further action is needed.

500 — Amazon server error

This is a transient error on Amazon's side, not a problem with your account or 1smart.link.

1. Wait 10 minutes.
2. Try accepting the suggestion again.
3. If the error persists after several attempts spread over an hour, contact support.

Tip: You can check the change log in the dashboard for a detailed record of every suggestion you have accepted, rejected, or attempted. The log includes the specific error code Amazon returned, which is helpful if you need to contact support.

Still stuck?

If none of the fixes above resolved your issue, contact the support team at support@1smart.link. To help the team investigate quickly, include the following in your message:

• Your 1smart.link account email address.
• The Amazon marketplace affected (e.g. amazon.in, amazon.com).
• A screenshot of the dashboard or the error message you are seeing.
• A brief description of when the issue started and which section of this article you have already tried.

Related articles

• Article #32
• Article #33
• Article #38