Checked for accuracy and updated on August 14, 2026.
Most WooCommerce stores get set up around products, payment gateways, and shipping — analytics gets left as an afterthought. A few weeks in, sales notifications start arriving, but the questions pile up faster than the answers: which products actually drive revenue, where does the traffic come from, are those discount codes helping or quietly eating into profit? Analytics either gets switched on and ignored, or never properly configured at all — both lead to the same outcome: decisions made on gut feel instead of data.
Turning On WooCommerce’s Built-In Analytics
No extra plugin needed — under WooCommerce → Analytics there’s Overview, Revenue, Orders, Products, Categories, Coupons, and Customers. If the dashboard looks empty on a store with existing order history, run Import Historical Data under WooCommerce → Analytics → Settings first; without it, older orders simply don’t appear anywhere. Worth knowing if a store recently switched to High-Performance Order Storage (the default for new stores since WooCommerce 8.2, storing orders in dedicated database tables rather than the old wp_posts structure): Analytics reads from the same underlying order data either way, but if numbers look off right after a storage-mode switch, re-running the historical import is worth checking before assuming something’s genuinely broken.
The Reports Worth Actually Reading
Overview gives a quick snapshot — total sales, net revenue, orders, average order value over a chosen date range — the first place to check whether a store is trending up or down before digging further. Revenue goes deeper: gross sales, net sales, refunds, taxes, shipping — this is where unusually high refunds or shipping costs quietly cutting into apparently-healthy revenue actually surface.
Products shows top-sellers, revenue per product, quantity sold — a small handful of products almost always generate most of the revenue in practice, and that’s where marketing budget should concentrate rather than spreading evenly across a whole catalogue. Customers shows new versus returning, lifetime value, purchase frequency — if most customers never come back, that points to a follow-up or email-marketing gap; strong returning-customer numbers point toward retention and upselling as the better focus instead. WooCommerce’s built-in customer accounts makes this repeat-purchase behaviour easier to track and encourage from the start.
Coupons, under WooCommerce → Analytics → Coupons, shows usage and revenue generated per discount code — answering a question most store owners never actually check: are discounts increasing sales, or just reducing profit on orders that would have happened anyway? A coupon not clearly earning its keep is worth retiring rather than leaving running out of habit.
Connecting Google Analytics for Traffic Context
WooCommerce’s own reports don’t show where traffic actually comes from — that needs Google Analytics. Search Console and Analytics setup covers the basics if that isn’t done yet; the Google Site Kit plugin is the simplest route from there, connecting a Google account and enabling GA4. Once connected, confirm ecommerce tracking is genuinely switched on — Google’s own GA4 ecommerce documentation covers the detail, though WooCommerce integration plugins and Site Kit usually handle most of it automatically. With this live, product views, add-to-cart events, and purchases show exactly where customers actually drop off before completing an order — data WooCommerce’s own reports can’t provide on their own.
Check analytics weekly rather than daily — daily numbers fluctuate too much on their own to mean anything, and reacting to single-day swings usually does more harm than good. Watch conversion rate alongside traffic, since more visitors doesn’t automatically mean more sales; a traffic spike with flat conversion often points to the wrong audience arriving, not a genuine win. If traffic drops unexpectedly, custom traffic alerts catch it faster than waiting to notice in a weekly review. Once a product consistently outperforms the rest, build content and ad spend around it specifically rather than splitting attention evenly across everything.
Only looking at total sales misses what’s actually working — product and traffic-source data are what turn a number into an actual decision. Ignoring refunds and shipping costs hides real profit problems behind apparently-healthy sales figures. Never connecting Google Analytics leaves no visibility into which channels bring in paying customers, or which carts get abandoned before checkout entirely. Checking data too often produces overreactions to normal noise instead of steady, evidence-based improvement; collecting data but never acting on it means the reports were never actually worth setting up in the first place.
WooCommerce Analytics paired with Google Analytics covers what the vast majority of small-to-medium stores genuinely need — clear reporting without extra cost or complexity. Larger stores with real segmentation or multi-channel funnel needs may eventually outgrow this and look at dedicated ecommerce analytics platforms or CRM systems, but for most stores that tooling adds overhead well before it adds insight. If the store’s basics aren’t fully in place yet, the step-by-step guide to building a WordPress website is worth working through first, before analytics becomes the actual priority.
Etienne Basson works with website systems, SEO-driven site architecture, and technical implementation. He writes practical guides on building, structuring, and optimizing websites for long-term growth.