Deprecating Server-Side Tracking

TL;DR
We are retiring the Server-Side tracking method. Please switch to Client-Side tracking for better accuracy, fewer conflicts with caching, and the same privacy guarantees. Our client script is cookie-free by default and does not collect PII by default.

What is changing

Server-Side tracking will be removed very soon.
Client-Side tracking becomes the single method. It has been the default for years.

Your old reports stay in your database. Only new visits will be tracked with the client method.

Why we are doing this

Accuracy
Client-Side tracking runs in the visitor’s browser, so it sees what actually loaded. Server-Side tracking happens before or outside the browser view and often miscounts due to:
- full-page caching or CDN edge caching
- preloading and warm-up crawlers
- reverse proxies and load balancers
- redirects that never render the final page on the server
- missing browser signals (screen, JS events, timing)
Compatibility and performance
Server-Side conflicts with many caching setups. The lightweight client beacon works well with cache, CDN, and modern performance stacks.
Simpler codebase
Maintaining one reliable method lets us ship improvements faster and keep the plugin stable.

Important clarification: this is not “server log analytics”

Some users think our Server-Side mode reads raw Apache or Nginx access logs. It does not.

WP Statistics’ Server-Side mode recorded hits when WordPress generated a page.
True “log analytics” parses the web server’s access log files directly, with no JS on the page and no call from the browser.

If your goal is a pure log-file workflow, you need a dedicated log analytics tool. WP Statistics focuses on privacy-friendly, cookie-free client tracking inside WordPress.

Privacy and compliance

No cookies by default.
No PII by default.
Integrates with Consent Plugins and respects Do Not Track.
Use the built-in Privacy Audit page in WP Admin → Statistics → Privacy Audit to verify your setup and turn off optional fields that may be sensitive in your region.

Compliance depends on what you collect and how you use it, not only on where code runs. If in doubt, check the Privacy Audit and your local guidance.

What you gain with Client-Side tracking

Better accuracy on cached and CDN sites
Fewer conflicts with cache and security plugins
Ability to capture real browser signals and client timing
Same privacy-first approach as before

How to switch (takes about a minute)

Go to WP Admin → Statistics → Settings → General.
Set Tracking Method to Client-Side Tracking.
Save.
Open your site in a private window and check:
- Real-Time/Online Visitors shows your visit.
- Browser dev tools → Network shows a small request from the page to WP Statistics’ tracking endpoint.
Visit Statistics → Privacy Audit and confirm there is no PII and cookies are off (unless you intentionally enabled something).

That is it. No template changes are required on most sites.

Common questions

Will I lose historical data?
No. Existing reports stay. Only new visits use Client-Side tracking.

Does Client-Side use cookies?
No. WP Statistics is cookie-free by default.

Is consent required?
Requirements vary by region and by the fields you collect. Use the Privacy Audit page to review your configuration and follow local guidance.

What about visitors with JavaScript disabled?
Most modern sites require JS. If your audience includes non-JS devices like some screen readers or text-only browsers, you will see fewer of these visits than with a raw log solution. If non-JS coverage is mission-critical, consider supplementing WP Statistics with a server log analytics tool.

Will this affect performance?
The client beacon is small and loads asynchronously. It plays well with caching and CDNs.

Can I keep using Server-Side for now?
If it is still present in your current version, it will be removed in a future major update. We recommend switching now to avoid surprises.

Migration checklist

Switch Tracking Method to Client-Side
Verify in Real-Time/Online Visitors
Review Privacy Audit
Keep your current data; no export is required
If you relied on Server-Side for non-JS traffic, decide whether you need an additional log-file tool

Glossary

Client-Side tracking: a small script runs in the browser and sends a hit to WordPress.
Server-Side tracking (WP Statistics): WordPress records a hit when rendering a page on the server. Not the same as parsing raw server logs.
Log analytics: processing web server access log files outside WordPress.

Need help?

If you have questions about your setup or your region’s requirements, open a ticket with a short note about your caching/CDN and we will guide you to the best client configuration.

Let’s get started

Take your business to next level

Become part of our growing family of +600,000 users and get the tools you need to make smart choices for your website. Simple, powerful insights are just a click away.

Get WP Statistics Now