Data Accuracy Problems

If a number looks wrong, it’s usually explained by an order-status difference, the free limits, your timezone, or a cached report. Here’s how to check each.

Revenue or totals don’t match WooCommerce

Customer History and WooCommerce can count slightly differently — for example in how they treat on-hold, cancelled, or refunded orders, and partial refunds. To confirm the figures:

• On Pro, open the Data Integrity Checker. It reconciles Customer History’s revenue against WooCommerce and shows a clear Verified or Mismatch status, so you know whether to trust a number or investigate it.
• Check you’re comparing the same date range, and that refunds in the period are accounted for.

“Missing” customers or history

On the free version, two limits explain most “where did my data go?” questions:

• The customer list shows up to 100 customers, and analytics cover the most recent 90 days. The data is still being recorded — Pro unlocks the full list and full history.
• If “Hide users with no orders” is enabled in Settings, customers who haven’t purchased won’t appear in the list. Turn it off to see everyone.

Session counts look off

Remember what’s excluded: logged-in admins are not recorded by default, and on Pro, bots and crawlers are detected and kept out of the analytics. If counts seem low, you may be testing while logged in; if they seem high on free, bot traffic isn’t being filtered (that’s a Pro feature). See Tracking Not Working for full-page caching, which can also affect counts.

Wrong times or date ranges

Timestamps use your WordPress timezone (Settings → General). If activity seems to land on the wrong day or hour, confirm that setting is correct for your store — date-range reports group by it.

Numbers look stale

The heavier reports are cached so pages stay fast, so a figure can lag shortly after new orders or activity until its cache refreshes. If you use an object-cache or page-cache plugin, clearing its cache will also refresh these views.

The same shopper appears twice

A visitor who browses as a guest and later creates an account (or checks out with a different email) can show up as more than one record — guest activity isn’t automatically merged into a later account. This is expected behaviour, not a bug; the plugin reports what it observed rather than rewriting history.