Real-time analytics in WordPress means visitor data appears in wp-admin within seconds of the visit, not the next morning. SlimStat records each hit into your own database as it happens, and its admin-bar widget refreshes at the top of every wall-clock minute, so the worst-case gap between a pageview and its appearance is under 60 seconds.
That immediacy is the whole point, and it is also where the confusion lives. “Real time” describes a delay, not a feature, and two tools using the phrase can mean very different delays by it. Here is what each live surface actually shows on a WordPress site running SlimStat.
| Real-time surface | SlimStat free | SlimStat Pro |
|---|---|---|
| Access log of individual hits | Full, filterable | Full, filterable |
| Online visitors count | Live figure | Live figure |
| Sessions today, in the admin bar | Live figure | Live figure |
| Last 30 minutes chart | Blurred preview | Full chart |
| Views and referrals today | Placeholder figures | Live figures |
Both the last-30-minutes chart and the admin-bar widget arrived in version 5.4, so an install older than that will not show either one regardless of licence.
What “real time” actually means on a WordPress site
Three steps sit between a visitor loading your page and you seeing them, and each one contributes a slice of the delay.
Collection. In Server mode, PHP records the visit while WordPress is building the page, so the row exists before the HTML reaches the browser. In Client mode, a small script fires after the page loads and posts the hit back over the REST API, admin-ajax, or the ad-blocker bypass transport. Client mode costs a fraction of a second more, and it is the mode to pick if you run a full-page cache: a cached page never executes PHP, so server-side recording never sees it. Both modes are in the free plugin, and the choice matters more for accuracy than for speed — see server-side tracking for the trade-off in full.
Storage. The hit is written straight into a table in your own WordPress database. There is no queue, no external pipeline and no third-party endpoint between the visit and the record, which is the structural reason a self-hosted tool can be live at all. A hosted analytics service has to ship your event to its own infrastructure, process it, and serve it back.
Display. The access log shows rows the moment you load or refresh it. The 30-minute chart buckets hits by wall-clock minute and refetches at :00 of each new minute. The online count is not “people with a tab open” — nothing can know that — it counts visitors active within the last 30 minutes, which is a rolling window by design rather than a live headcount.
Live data answers a different question, not a faster one
It is tempting to think of real-time as your monthly report with the latency removed. It is not. The two answer different questions, and the mistake that wastes the most time is asking one of them the other’s question.
Historical reporting answers what happened: which channel converts, which posts hold attention, whether this quarter beat the last. Those answers need aggregation, and aggregation needs volume and time. A live view answers what is happening: is the campaign that went out four minutes ago landing, did the post go anywhere, is anyone hitting the page I just broke. You will never identify your best-performing channel from a live view, and you will never learn from a monthly report that checkout stopped working ten minutes ago.
The practical consequence: real-time is an operational instrument, closer to a dashboard warning light than to a business report.
Why live data helps small sites more than large ones
The instinct is that live dashboards are for sites with thousands of concurrent visitors. The opposite is closer to true. Large organisations analyse in batches because their volume makes individual sessions meaningless; small sites operate close enough to the ground that a single session is legible.
- Every session is interpretable. At twenty visitors an hour you can see the actual path someone took, where they hesitated, and what they ignored. That granularity disappears into an average once traffic grows.
- Publishing becomes a live signal instead of a wait. You see whether a new post reached anyone within minutes of it going out, which turns a headline or an internal link into a decision you can revisit today rather than next month.
- Breakage surfaces while it is still cheap. A form that stopped submitting, a redirect loop after a plugin update, a page returning errors to half your traffic — all of these look like a sudden flat line in a live view and like nothing at all until the next report.
- Unexpected traffic arrives with a source attached. A surge from a forum or a newsletter is only actionable while it is happening. Watching the referrers update live tells you where it came from in time to do something about it.
- The feedback loop shortens. Small teams can change copy, navigation or a call to action the same afternoon. Live data is what makes that a measurable change rather than a guess.
None of this requires staring at a dashboard. The value comes from short, frequent checks — a glance at the admin bar while you are already in wp-admin — not from leaving a live view open on a second monitor.
How to set it up on WordPress
SlimStat is a WordPress-native plugin with 70,000+ active installs and a 4.8 rating from 817 reviews, and the real-time surfaces work on the free version. Five decisions get you a live view that is worth trusting.
- Install the free plugin and let it collect. Tracking begins on activation; the reports have nothing to show for the first few minutes, which is normal rather than a misconfiguration.
- Pick your tracking mode. Server mode if you do not run a full-page cache and want every request recorded, including ones that never execute JavaScript. Client mode if you do.
- Exclude yourself. This is the step people skip and then wonder why their live view is so busy. The free exclusion filters let you drop visits by IP, by user role, or by logged-in status, so the traffic you are watching is not your own reloads of a draft.
- Choose a transport if ad blockers are a problem. The free ad-blocker bypass transport routes the tracking request through a path filter lists do not recognise, which matters most on technical audiences where a double-digit share of visits otherwise never registers.
- Turn on geolocation if you want a location on live hits. Also free, with the provider configurable, and useful mostly when you are trying to work out whether a traffic spike is a real audience or a single scraper.
Then know where to look. The admin bar carries online visitors and today’s sessions on every wp-admin screen, so you do not have to navigate anywhere to check. The access log is the raw stream — one row per hit, filterable, and the surface to reach for when you are diagnosing rather than monitoring. The last-30-minutes chart is the shape of the current half hour at a glance.
Unblurring that chart and putting your real Views and Referrals figures into the admin-bar widget is what the Pro add-on does for this particular workflow. Pro also adds scheduled email reports, additional goals and funnels beyond the single goal free allows, click heatmaps, Excel export, the User Overview report, an external database option and network-wide analytics for Multisite — none of which are required to watch traffic arrive.
What live data will not tell you
Real-time is easy to over-read, and the failure modes are consistent.
Small numbers move violently. Three visitors instead of one is a 200% increase and means nothing. Live views invite pattern-matching on noise, which is exactly what a threshold or a longer window exists to prevent.
Not every spike is an audience. A bot sweep, a scraper, or an uptime monitor produces a shape indistinguishable from a genuine surge until you look at the referrer, the user agent and the pages hit. Check before you celebrate.
Aggregate questions still need aggregate data. Whether your content holds attention is a question about bounce patterns across weeks; whether visitors follow the route you designed is a question about user journeys across many sessions. Neither is visible in a half-hour window, no matter how carefully you watch it.
A flat line at 3am is not an outage. The most common false alarm is simply a quiet hour on a site whose audience lives in one timezone.
Common questions
Do I need real-time data on a low-traffic site?
Usually yes, and for a different reason than a large site would. At low volume individual sessions are readable, so a live view tells you something specific rather than something averaged.
How fresh is the data, exactly?
Individual hits land in your database as they occur and appear in the access log on the next load. The live chart and admin-bar figures refresh at the top of each minute. The online count covers the last 30 minutes.
Will real-time tracking slow my site down?
The write is a single insert into a local table on the same server, so the cost is negligible on a normally configured site. Client mode moves it off the page render entirely.
Does the free version include real-time reporting?
Yes, with limits. The access log, the online count and today’s sessions are live on free. The last-30-minutes chart is shown as a blurred preview, and the admin bar’s Views and Referrals tiles display placeholder figures until Pro is active.
Can I get live data without cookies?
Largely, yes. SlimStat sets one session cookie by default so a visitor’s pageviews group into a single visit, and that cookie can be switched off or withheld until consent is granted. Pageviews are recorded and appear live either way; what you lose without it is the stitching of several pageviews into one visit.
Why does my live view show fewer visitors than I expect?
Two usual causes: a full-page cache combined with Server mode, so cached responses are never recorded, and ad blockers dropping the tracking request. Switching to Client mode addresses the first, and the ad-blocker bypass transport addresses the second.