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.
Location in WordPress: WP-Admin ▸ Statistics ▸ Settings ▸ General ▸ Open Debugger
The Tracker Debugger is a real-time diagnostics console built into WP Statistics. It helps you verify that the tracker.js script is loading correctly, detect configuration issues and PHP errors, and view a live feed of recent visitor hits—all without leaving your dashboard.
Use case | What you gain |
---|---|
New installation / site migration | Confirm that tracker.js is being served, that hits reach the collection endpoint, and that no caching or ad-blockers are interfering. |
Sudden drop in stats | Quickly see if PHP errors or mis-configured consent/DNT rules are preventing hits from being recorded. |
Ad-blocker or privacy-tool testing | Validate that the built-in ad-blocker bypass is working across real visitors. |
Plugin/theme debugging | Detect when a caching plugin, security layer, or custom code blocks or alters tracking requests. |
The debugger is divided into four panels, each using traffic-light colours and icons to make status checks instantly clear.
Item | Meaning | What Success looks like |
---|---|---|
Tracker.js Status | Confirms that the JavaScript file was delivered by your server and executed in the browser. | Loaded Successfully (green check) |
Hit Endpoint Status | Verifies that the browser could send a tracking request (hit) to your WordPress site and received a 200 OK response. | Successful (green check) |
If either item shows Failed or Blocked, no statistics will be recorded. Check:
These are informational flags—neither errors nor successes.
Note | Why it matters |
---|---|
Do Not Track (DNT) | Indicates whether the visitor’s browser sent the DNT header. If Enabled, WP Statistics skips tracking that visitor, so you may see lower counts than in other analytics tools. |
Consent Management is Disabled | You have not enabled WP Statistics’ consent module. If you operate in a jurisdiction that requires consent (e.g., GDPR), consider enabling it. |
Check | Details |
---|---|
Ad-blocker Bypass is Enabled | Tracker.js used its fallback endpoint to avoid known ad-block filters. |
Caching Plugins Detected | The debugger lists any caching plugins so you can exclude the tracking endpoint from caching if needed. |
No Filters or Exceptions Applied | Confirms that you have not excluded this visitor by IP, role, or custom filter. |
PHP Errors Detected in tracker.js | Displays the exact PHP warning/error captured during the most recent hit. Click to expand for stack trace and file path. |
Action required: Any PHP warning or notice can stop hit registration. Click the row, copy the error, and send it to your developer or our support team.
A live table shows the last hits with:
Use this table to:
Symptom | Likely Cause | Fix |
---|---|---|
Tracker.js Status: Failed | File missing, script blocked by CSP, or theme removed wp_head() | Check file exists at /wp-includes/js/wp-statistics/tracker.js ; ensure wp_head() is present; relax CSP for self . |
Hit Endpoint Status: Failed | REST API disabled, 403 by firewall, or nonces expired | Whitelist /wp-statistics/api/hit ; disable “REST API Off” plugins; clear cache. |
PHP error flagged | Theme/plugin conflict | Click the error → copy message → disable suspect plugin/theme or update WP Statistics. |
If issues persist, consult the full Troubleshooting Guide or contact our support team via the link at the bottom of the debugger.
/wp-statistics/api/.*
and tracker.js
.The Tracker Debugger is your quickest window into what the tracker is doing under the hood. If you still see discrepancies after following the steps above, open a support ticket and include:
These details help us diagnose conflicts and get you back on track faster.
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.