Who is on your site right now.

A five-minute live window, refreshed every fifteen seconds, with countries, pages and sources behind it. When nothing is happening it says so rather than smoothing the gap.

What is realtime analytics?

Realtime analytics shows who is on your site at this moment rather than what happened yesterday. Mrkr counts anyone who sent an event in the last five minutes, refreshes every fifteen seconds, and shows where those people are, what they are reading, and which source brought them.

It is the one view whose value is entirely about latency. A launch, a post that took off, a broken deploy: all of them are visible here while you can still act, and invisible in a daily report until it is history.

live window: anyone active in it counts as on the site
5 min
live window: anyone active in it counts as on the site
refresh interval on the realtime view
15s
refresh interval on the realtime view
most recent raw events kept in the live feed
100
most recent raw events kept in the live feed
after which a cached range including today is treated as stale
10s
after which a cached range including today is treated as stale

Ranges that include today carry a write timestamp and are refreshed once they are more than ten seconds old, so live views stay current instead of being pinned to a cache floor. Historical ranges are immutable and cached longer.

A count, a map, and what they are reading.

The live count sits above a map, or a list, of current visitors with country, device and source where those are known, plus breakdowns of the most recent activity by country, path and device.

There is no historical fallback and no smoothing. If nobody is on the site, the page says nobody is on the site. That sounds obvious and it is not universal: plenty of tools quietly widen the window until the number stops being zero.

Mrkr realtime view showing visitors on the site right now, by country and page.
The realtime view: live visitors, where they are, and what they are looking at. Open it in the live demo.

What realtime is actually for.

Watching a launch land

Whether it moved anything, which page people go to first, and whether the traffic came from where you expected.

Catching a break in minutes

A bad deploy shows as traffic collapsing on one path while everything else holds. Five minutes, not next morning.

Seeing a mention first

An unfamiliar referrer climbing the live source list is usually somebody talking about you somewhere.

Sharing the moment

A public live link or an embeddable counter, both scoped to a token you can revoke at any time.

Watch it live

The live demo runs the realtime view on real demo traffic, refreshing on the same fifteen-second cadence. No signup, no card.

Open the live demo
Mrkr realtime view showing visitors on the site right now, by country and page.

Three surfaces, three cadences.

Not everything in Mrkr refreshes at the same speed, and the differences are deliberate rather than accidental.

SurfaceWindowRefreshWhat it answers
RealtimeLast 5 minutesEvery 15 secondsWho is here now, and where from
Events live feedMost recent 100 eventsEvery 5 secondsWhat is firing, event by event
OverviewYour selected rangeEvery 30 secondsHow today compares to the period
Embedded counterLast 5 minutesEvery 15 secondsA public live count on your own page

Why the numbers are trustworthy live.

Bots are the most punctual visitors

An unfiltered live count is largely scraper activity. Nine filter layers run before anything is written.

Measured, not assumed

On one live site, 30 days held about four times as many bot hits as human pageviews. That is how wrong a raw count would be.

Caching that gets out of the way

Any range including today is stale after ten seconds, so a live view is never pinned to a cache floor.

Questions, answered.

Keep reading

Your first visitor is already here.

Drop in the script and watch them land. It takes about a minute.