# Failing to accurately compare in-app data to console

Before attributing data discrepancies to a real issue, keep in mind that Amazon uses slightly different [conversion windows](https://docs.advertisingbeast.com/getting-started/understanding-the-essentials/data-considerations), so sales and orders for sponsored products may be slightly higher (usually observed values are between 1% and 2% higher). The click invalidation process can also introduce small discrepancies in traffic data, typically less than 1%.

Data delays can also be due to system indexing — databases are indexed before showing data to provide you with a faster front-end experience. Wait a few hours to see if the data catches up. If these discrepancies remain considerably higher after a period of 24 hours, please check each of the subsections below to identify the one most relevant to your current scenario.

### No data

If the reported values are equal to 0 in all metrics:

* [ ] Verify that the selected account is the correct one (the same marketplace may have more than one account, such as login with Amazon, shipping accounts, etc.).
* [ ] Confirm that the account is [set up for advertising](https://docs.advertisingbeast.com/getting-started/onboarding/enabling-accounts-for-advertising).

### Partial data

If the data shown is partial and/or does not match the Amazon console or Amazon's bulk reports:

* [ ] Ensure the [date ranges](https://docs.advertisingbeast.com/getting-started/understanding-the-essentials/data-considerations#date-ranges) are identical to those selected in Amazon, keeping in mind that 'TODAY' is not reported in the app.
* [ ] Filter the data by campaign type to potentially identify which segments are experiencing 

{% hint style="info" %}
If none of the solutions above work, contact support and provide them with a clear explanation of the issue you are experiencing. Include screen captures, videos, error messages or codes, Amazon data downloads (for the same date range you are troubleshooting, indicating the exact dates reported), and/or anything else you think might be valuable in identifying the issue more quickly.
{% endhint %}