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.
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
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.
Live activity
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.
Breakdowns
Active pages, Arriving from and Countries each list the top five over the last thirty minutes, ranked by the number of people.
Delivery
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.
Questions it answers
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 you can see whether the link you shared is climbing the list.
41
people from news.ycombinator.com, last 30 minutes
Who it’s for
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.
Source: the client’s website
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
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
Spec sheet
from the product
FAQ
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. A saved segment of people or a property filter narrows the live view the same way, and Compare to yesterday shows how the same time looked a day earlier.
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.
Install one script tag and see your first report in minutes.
About 5 KB · pageviews, clicks and scroll depth, automatically