See who’s on your site right now.

A live count of the people on your site, every event as it lands, and the pages they’re on, where they came from and where they are, pushed to the page as it happens.

Start tracking free All features
window for the live count of unique people
5 min
of events behind the feed, sparkline and breakdowns
30 min
pages, referrers and countries, counted by people
Top 5
latest events in the feed, newest first
50

What it does

Realtime is the last thirty minutes of your project, kept live. The headline counts unique people seen in the last five. The feed, the sparkline and the breakdowns cover the thirty, and every new event updates all of them at once.

Right now

One honest number for “on site right now”.

The headline counts unique people seen in the last five minutes, so one visitor clicking around is still one. Beside it, a sparkline of the last thirty minutes, one point per minute, each counting unique people.

  • People, not events: a burst of clicks from one visitor doesn’t inflate it.
  • Old events leave the window on their own, even when nothing new arrives.

Live activity

Pause the feed. Nothing gets lost.

Every event appears as it lands, with the page or the text of what was clicked, who it was and where they are. Pause to read it; new events wait in a queue, the Resume button counts them, and they slot in, in order, when you resume.

  • The count, sparkline and breakdowns keep updating while the feed is paused.
  • Identified people show by their ID, everyone else as Anonymous, with city and country.

Breakdowns

Where they are, where they came from.

Active pages, Arriving from and Countries each list the top five over the last thirty minutes, ranked by how many people are there rather than how many events they fired.

  • Referrers are shown as hostnames. No referrer reads “Direct / none”.
  • Pages and referrers come from pageviews; countries from every event.

Delivery

Pushed to the page, not polled.

The Realtime page holds a WebSocket open. It gets a full snapshot when it connects, then an update for every event. If the connection drops, the status says so and it reconnects on its own.

  • Pick one source, such as the marketing site or the app, and the stream is filtered on the server.
  • Retries back off from one second to thirty, and each reconnect starts from a fresh snapshot.

Questions it answers

Ask it the way you’d ask a colleague.

How ClickClacks answers it

Open Realtime a few minutes after it goes out. Arriving from ranks referrers by the people they sent in the last thirty minutes, so the link you shared either climbs the list or it doesn’t.

41

people from news.ycombinator.com, last 30 minutes

Who it’s for

Three ways teams use it.

  • Agencies

    On a client’s launch day, keep Realtime open on their site’s source only, and show them the campaign’s referrer climbing Arriving from while it happens, not in next week’s report.

    Source: the client’s website

  • Indie developers

    Post to Hacker News, then watch the live count and the referrer list. When a custom event you just shipped fires for the first time, you see it land in the feed.

    Realtime open in a pinned tab

  • Product teams

    During a release, filter to the app’s source and pause the feed to read the first events from the new flow, without losing the ones that arrive while you read.

    Source: Web app · feed paused

How it works

Under the hood

  1. 01Events arriveEach event you send is added to your project’s live window as it’s collected. The window keeps the last thirty minutes, up to 5,000 events.
  2. 02A snapshot, then updatesWhen the Realtime page connects it gets the whole picture at once, then one update per event: the feed row, the count, the sparkline and the breakdowns.
  3. 03The window moves on its ownWhile the page is open, a fresh snapshot is sent at least once a minute, so people who have gone quiet drop out of the count even when nothing new arrives.
  4. 04Dropped connections recoverIf the socket closes, the status reads “Reconnecting…” and the page retries with back-off, up to thirty seconds apart, until it’s live again.

Spec sheet

from the product

Live count
Unique people, last 5 min
Sparkline
30 one-minute points
Feed
Latest 50 events
Breakdowns
Top 5 each, by people
Live window
30 min, up to 5,000 events
Delivery
WebSocket push
Reconnect
Automatic, 1–30 s back-off
Filter
All sources or one

Same events, different question

Works well with

All features →

FAQ

Realtime, in detail.

  • Unique people who sent any event in the last five minutes. It counts people, not events or sessions, so one visitor clicking around is one.

  • Pushed. The page keeps a WebSocket open, receives a full snapshot when it connects and then an update for every event as it’s collected.

  • The status in the filter bar changes from Live to Reconnecting…, and the page retries on its own, waiting a little longer each time, up to thirty seconds. When it reconnects it starts from a fresh snapshot.

  • No. New events queue up while you read, the Resume button shows how many are waiting, and they are added to the top of the feed in order when you resume. The count and breakdowns keep updating the whole time.

  • Yes. Pick a source in the filter bar and the live view is filtered on the server to events from that source. Pick All sources to see everything in the project.

  • Thirty minutes. The feed, the sparkline and the three breakdowns all cover that window, and the headline count covers the last five. For anything older, use the other reports.

Start hearing your clicks.

One script tag. Your first report in minutes.

Start tracking free Sign in

4.3 KB · pageviews, clicks and scroll depth, automatically