How to Set Up WooCommerce Analytics in SlimStat

SlimStat Free 6 includes an opt-in WooCommerce dashboard under SlimStat → Ecommerce. It connects order summaries with the traffic SlimStat can validly associate, so you can examine sales, products, channels and an observed purchase journey inside WordPress. WooCommerce remains the source of order data. For an overview of what the store reports answer, see WooCommerce analytics.

What is included

Pro is not required for the core dashboard. Guest/account segments mean whether an order used a registered account, not whether a customer is new or returning.

Requirements and access

Use Free 6, WooCommerce 8.3+, WooCommerce’s Action Scheduler and a 64-bit PHP runtime. WooCommerce’s own WordPress/PHP requirements still apply even though SlimStat’s general minimums are WordPress 5.6 and PHP 7.4. Both HPOS and legacy WooCommerce order storage are supported.

Viewing requires SlimStat report access plus view_woocommerce_reports or manage_options. Setup also requires manage_woocommerce or manage_options. This is a report for one store at a time, not a Multisite-wide revenue total.

Set up and verify

1. Back up the WordPress and analytics databases, including an external analytics database if configured.
2. Open SlimStat → Ecommerce → Set up Ecommerce.
3. Let the background import finish. The dashboard marks incomplete imports as provisional; keep scheduled actions running.
4. Choose a currency and date range, then compare the order cohort with WooCommerce using the definitions below.
5. Test a consented shopping journey and review the coverage before drawing traffic-to-purchase conclusions.

Setup creates SlimStat’s Ecommerce table and an analytics visit index; it does not change WooCommerce order tables. A large index build needs time and storage. If the server cannot perform the required online operation, the Ecommerce page shows Setup did not finish with the reason and a Try setup again action rather than switching to a blocking table copy. When a MyISAM analytics table is the cause, it is named: convert the table to InnoDB and retry. The migration kill switch also prevents setup.

Understand the numbers

• Orders: distinct standard orders created in the selected site-calendar period, with status processing, completed or refunded. Fully refunded and zero-value orders still count. Processing is not proof that a payment gateway settled funds.
• Net sales: the included orders’ current value after discounts and recorded refunds, excluding tax and shipping as defined in the report. Fees remain included. Refunds adjust the original order’s period, even when made later; historical totals can change.
• Average order value: net sales divided by included orders; unavailable when there are no orders.
• Products: line totals and quantities after explicit line refunds. An amount-only refund cannot be assigned to a product without evidence, so unallocated adjustments are shown separately.
• Currency: one order currency at a time, without exchange-rate conversion. Traffic counts have no currency.
• Purchase rate (tracked visits): distinct eligible visits with an associated included order divided by eligible visits in the same period. Several orders in one visit count once. The buying and eligible visit counts are printed beside the rate, and small samples are shown as measured, so read a rate from a few hundred visits with care.

These are reporting definitions, not profit, cash flow or coupon ROI. Check the dashboard’s Definitions when reconciling an apparent difference with another WooCommerce report.

Explore trends and coverage

Select Net sales, Orders, Average order value or Purchase rate (tracked visits) to change the chart. Daily, weekly and monthly views use the site calendar; partial periods and missing history are identified. Rates and distinct visits are recalculated per interval, so do not add daily rates to get a weekly rate.

Use the Acquisition, Shopping, Audience and Landing pages tabs to inspect available rankings. Full report opens more results with exact values. Native dates, supported filters and saved segments remain available. Pro exports carry the same scope, with up to 1,000 ranking rows.

The order-to-visit link needs an existing verified, unexpired tracking cookie, a retained eligible human pageview and current consent/exclusion permission. It does not match people by IP or email, create a new tracking identifier, or reconstruct historical visit associations. Guest checkout can be associated when those conditions hold.

Where no SlimStat association exists, already recorded WooCommerce attribution may supply a separately labeled source. Missing evidence is shown as Unassigned. Landing page and device need a linked visit, so WooCommerce attribution cannot fill them. Traffic filters select orders associated with matching retained visits and exclude unlinked orders. In Pro, View sales in Ecommerce on the channel and campaign reports likewise needs store-report permission and does not include every store order.

The purchase journey shows an observed sequence, not a reconstructed historical funnel. Express checkout can skip stages; a missing stage does not prove abandonment. The coverage panel explains what was recorded and what is unavailable.

Freshness, recovery and privacy

Order synchronization runs in bounded background jobs, not a historical scan during checkout. New orders, status changes and refunds can take time to appear. For a stalled import, inspect WooCommerce → Status → Scheduled Actions and the Ecommerce status panel. Fix the underlying error, then use Rebuild reports. Deactivation/reactivation or a reporting-timezone change may also require reconciliation. Do not drop tables to troubleshoot: erased flags and historical associations cannot simply be recreated.

Ecommerce follows SlimStat retention and erasure rules. Its projection adds no billing addresses, names, emails, IPs or new browser identifiers. Order identifiers remain for reconciliation and authenticated privacy export, not aggregate report CSV. Order-access keys are removed from newly stored analytics URLs and referrers; older records are not rewritten automatically.

Review consent, set retention or configure Pro email reports.