Real-time analytics tools

What "real-time" actually means in analytics

Most analytics tools claim "real-time" but mean different things. The honest taxonomy: true real-time shows new pageviews within 1-5 seconds (server-pushed updates via WebSocket or SSE). Near real-time polls every 30-60 seconds (most cookieless SaaS tools). Batch processes events in 5-15 minute windows — this is what GA4 does, and what most "real-time" claims actually mean.

The 12 tools below all ship a real-time dashboard with explicit live-visitor counts. We grouped them by update latency. If you need to see a spike from a Hacker News submission as it happens, you want the sub-5-second tier. If you just want yesterday's number a few minutes faster than GA4 ships it, the 30-60-second tier is plenty.

The three latency tiers

Sub-5-second updates (true streaming)

Matomo ships a "Visitors in real time" widget that updates roughly every 5 seconds — fastest of the open-source heavyweights. Self-host on a $10/mo VPS for unlimited refresh. OpenPanel uses a streaming dashboard with WebSocket updates — a Mixpanel-class tool at $2.50/mo entry. Visitors built its entire product around a real-time 3D globe — visit pulses appear within 2 seconds of the pageview.

15-30-second polling (near real-time)

Plausible updates the live-visitor count every 30 seconds via dashboard polling. Fathom matches at ~30s. Umami self-hosted polls every 15s by default (configurable). Pirsch ships a live counter at the top of the dashboard, also ~30s. Rybbit includes a real-time visitors view at the same cadence. All are cookieless analytics tools with no consent banner needed.

1-5-minute batch (still useful for trend dashboards)

Simple Analytics and GoatCounter trade real-time depth for simplicity — pageviews land in the dashboard within a couple of minutes. Seline and Cabin sit in this tier too. Acceptable if you check the dashboard once a day, not if you're monitoring a campaign launch.

When you actually need real-time analytics

Three legitimate use cases:

1. Campaign launch monitoring. A new homepage goes live, an email blast sends, a paid ad campaign starts. You need to see traffic land within seconds, not minutes, to catch a 500-error or broken redirect before it eats half your budget.
2. Viral content / Hacker News submissions. Traffic spikes from social or aggregators are short-lived. Knowing within 30 seconds that you've been front-paged lets you reach for the cache config before the server falls over.
3. Live event tracking. Webinars, product launches, conference live-streams — you want a live count of viewers in the dashboard, not a 15-minute-stale number from GA4.

Outside these cases, the difference between "5 seconds" and "5 minutes" is mostly aesthetic. Don't pay extra for sub-second streaming if your dashboard gets opened twice a week.

What real-time analytics can't tell you

Real-time data is biased toward whatever just happened. A 30-second window of 50 visitors doesn't mean anything about your conversion rate, your bounce rate, or your channel mix — those need at least an hour of accumulated traffic to stabilise. Real-time is great for "did the deploy break anything?" and bad for "should I change our content strategy?". Most teams over-watch real-time and under-analyse the 30-day window.

Pick by your operational pattern

If you're a solo operator who wants the cheapest real-time dashboard: OpenPanel at $2.50/mo or Umami self-host. If you want SaaS polish: Plausible or Fathom at $9-15/mo. If you need streaming-grade for live events: Matomo self-host, Visitors, or OpenPanel. If you operate in regulated EU industries and need real-time + ISO 27001: Piwik PRO.