Server-side tracking records a visit during a server request. In SlimStat, Server mode runs when WordPress executes PHP. It can record eligible pageviews without a browser tracking script, but it misses visits served entirely by a page cache or CDN.
Which mode should I choose?
| Your site | Recommended starting point | Reason |
|---|---|---|
| Full-page cache or CDN cache | Client | The browser can send a tracking request even when WordPress does not render the page |
| No full-page cache, pageviews are the priority | Server | WordPress can record eligible page requests during PHP execution |
| Clicks and browser interactions matter | Client | A server request alone cannot observe what someone clicks after the page loads |
Client mode also stores SlimStat analytics in your configured database. Browser collection does not automatically mean third-party storage. Neither mode records every possible visit: consent, filters, bots, network failures and caching affect the result.
What does Server mode collect?
The tracker can use request information such as the page URL, referrer, timestamp and user agent. IP protection, geolocation, consent and exclusion settings determine which fields are retained. Server mode does not record scroll depth or video engagement. WooCommerce orders are covered below.
Choose SlimStat → Settings → General → Tracking Mode, save, and follow the server-side setup guide. Keep the tracker endpoint available when using Client mode, and review cache exclusions.
What about WooCommerce orders?
WooCommerce orders do not depend on the tracking mode. Once Ecommerce is set up, SlimStat 6 reads orders and refunds on your server from WooCommerce’s own hooks, in Client and Server mode alike, so an ad blocker cannot drop an order from your revenue totals. Add-to-cart actions are recorded on the server too, against the visit SlimStat already tracked.
The tracking mode still matters for credit. An order takes its channel and UTM campaign from the visit SlimStat recorded before checkout, matched through SlimStat’s tracking cookie when the buyer’s consent allows it. If no visit was recorded, for example a cached page served while Server mode was on, SlimStat uses the attribution WooCommerce stored on the order, or lists the order as Unassigned. It still counts in your totals. How WooCommerce sales attribution works covers the rules, and WooCommerce analytics shows the reports.
Does it improve performance?
Server mode moves collection work into the WordPress request. Client mode sends a browser request. Both still have processing and database costs. Measure page delivery and report queries separately, using the same traffic and database size.
The SlimStat 6 development benchmark demonstrates reduced database operations for a specific chart query. It does not establish a universal page-speed improvement or make Server mode the right choice for a cached site.
Does it remove the need for consent?
Changing where code runs does not determine what you may collect. Configure consent integration, IP protection and retention for your site. SlimStat’s GDPR Compliance Mode, IP anonymization and IP hashing are not enabled by default in the v6 target.
How do I check the setup?
- Open a test page in a private browser window and follow your site’s consent flow.
- Confirm the pageview appears with the expected URL and time.
- Repeat with a warm page cache, then with JavaScript disabled if testing Server mode.
- Test consent rejection and configured exclusions as well as successful collection.
- Compare equivalent periods before interpreting changes in traffic or conversion rate.
Server logs include requests that analytics may intentionally exclude. Use them to investigate differences, rather than expecting identical totals.
Start with the report you need
SlimStat Free provides traffic reports and one conversion goal inside WordPress. Pro adds tools such as funnels, click heatmaps and scheduled email reports. Install Free, compare Free and Pro, or activate a purchased Pro add-on.