Daily numbers look shifted compared to source platforms.
Where to Check in PassiveWP
WordPress Admin -> PassiveWP -> Amazon Earnings -> Overview
Step-by-Step Fix Walkthrough
Fix Step 1: Confirm WordPress timezone in site settings.
Go here WordPress Admin→PassiveWP→Amazon Earnings→Overview
Do this In Amazon Earnings, set date range first, then review cards/tables and open deeper views for anomalies.
Confirm Imported/report totals should align with the selected date window from your source file.
Fix Step 2: Use consistent start/end windows across systems.
Go here WordPress Admin→PassiveWP→Amazon Earnings→Overview
Do this In Amazon Earnings, set date range first, then review cards/tables and open deeper views for anomalies.
Confirm Imported/report totals should align with the selected date window from your source file.
Fix Step 3: Document timezone used for team reporting.
Go here WordPress Admin→PassiveWP→Amazon Earnings→Overview
Do this In Amazon Earnings, set date range first, then review cards/tables and open deeper views for anomalies.
Confirm Imported/report totals should align with the selected date window from your source file.
Fix Step 4: Reconcile a known 7-day window for validation.
Go here WordPress Admin→PassiveWP→Amazon Earnings→Overview
Do this In Amazon Earnings, set date range first, then review cards/tables and open deeper views for anomalies.
Confirm Imported/report totals should align with the selected date window from your source file.
Most Common Causes
- WordPress site timezone differs from reporting expectations.
- Comparing UTC exports to local dashboard windows.
- Cross-platform report windows not aligned.
How to Prevent It Next Time
- Standardize reporting timezone company-wide.
- Annotate dashboards and exports with timezone context.
- Avoid mixed timezone comparisons in one report.
When to Contact Support
- You completed every fix step and still get the same error.
- The issue impacts revenue-critical pages or high-volume campaigns.
- You can share timestamps, affected link/product IDs, and screenshots of the exact error state.
