Understand why session data may differ between Amazon and Intentwise and learn how to compare reports accurately.
Suppose you see differences in session numbers between Amazon Seller Central and Intentwise (for example, in the product_summary table). In that case, it’s usually due to how Amazon reports sessions across different report types and time ranges.
Why This Happens
1. Different Report Definitions
-
Sales and Traffic by ASIN includes all ASINs with at least one page view, even if there were no sales.
-
Sales and Traffic by SKU includes only SKUs with at least one sale.
Because of this, the ASIN-level report often shows higher total sessions than the SKU-level report for the same date range.
2. Daily vs. Monthly Report Behavior
-
Daily SKU reports count sessions only on days when a sale occurred.
-
Monthly SKU reports include all days with traffic, even if no sales occurred.
As a result, summing daily SKU sessions may not match the monthly SKU or ASIN-level totals.
How Intentwise Handles Sessions
Intentwise sources session data in the product_summary table from the Sales and Traffic by SKU report.
To ensure accurate comparisons:
-
Use the same report type (SKU vs. ASIN) on both sides.
-
Match date ranges and reporting frequency.
-
Remove duplicates if exporting manually from Seller Central.
Common Scenarios
| Situation | Likely Cause | Tip |
|---|---|---|
| Seller Central total doesn’t match Intentwise | Comparing ASIN-level data with SKU-level data | Compare SKU-to-SKU |
| Summed SKU sessions < brand total | Daily reports omit no-sale days | Use monthly SKU or ASIN report |
| Product Summary slightly off from API data | Different report endpoints used | Validate using “Sales and Traffic by SKU” |
Key Takeaway
Session discrepancies are expected when comparing across Amazon’s report types. Intentwise aligns with Sales and Traffic by SKU data to ensure SKU-level accuracy.
For best results, always compare like-for-like data, same report, same level, same time range.