Troubleshooting

Most reports fall into one of four categories. Start by working out which one you have.

The number here differs from Amazon

Usually a reporting window or an attribution difference rather than an error. Amazon restates advertising data after the fact, which is also why a rule ignores the most recent days by default — see Data Window.

Data is missing or late

Check whether the account is still loading its history, whether the Amazon connection is healthy, and whether the entity is inside marketplace scope.

A rule reached a conclusion I did not expect

Almost always the Data Window or the decision scope. Check both before checking the criteria.

A change did not reach Amazon

Check in this order: has anybody applied it, do you have permission to apply, and did Amazon accept it. See Preview Changes.

In this section

• Understanding data differences — why a number here differs from Amazon’s.
• Missing or delayed data — what to check, in order.
• A change was not applied — the four points it can stop at.
• Connection problems — including the ones that fail quietly.
• Known limitations — what Vendlen does not do today.

Still stuck?

Documentation cannot cover everything, and some problems need somebody to look at the account. If you have worked through the relevant page and it is still wrong, get in touch — with the entity, the date range, and what you expected to see. A concrete example is far quicker to diagnose than a general report.

Contact Vendlen