Real-time analytics for operating a live product
Understand active visitors, live journeys, launches and incidents with continuously updating reports that preserve privacy and system stability.
Real-time analytics is most valuable when the next few minutes can change an action. It can confirm that a launch is receiving qualified traffic, show whether a checkout is failing, reveal where active users are located at country-level precision, or help an operator distinguish a product incident from an acquisition change.
It is less useful as theatre. A glowing dot on a globe can be visually satisfying while saying little about value. The live view should use the same event definitions, traffic-quality rules and authorization boundaries as the historical dashboard.
What “active now” should mean
MetricFold defines active visitors within a short rolling window. A recent accepted event keeps a visitor or privacy-safe session active; silence moves it out of the count. The window is visible in the report because a five-minute active count is not comparable with a thirty-minute active count.
The collector does not create a permanent anonymous user to power this number. It uses bounded session evidence and discards raw network identifiers. Signed-in products may send an approved pseudonymous subject hash through a trusted integration when account-level analysis is needed.
Stream changes instead of reloading the page
The dashboard uses Server-Sent Events for live reports. SSE is a simple HTTP stream from server to browser: it supports ordered messages, browser reconnection and ordinary infrastructure without requiring a bidirectional socket for a read-only feed. MetricFold also includes a timed refresh fallback for browsers, proxies or mobile clients that cannot maintain the stream.
Every live endpoint is site- and workspace-scoped. Connections are bounded in duration and snapshot count so a forgotten tab cannot hold an unbounded worker. Reconnection resumes from a fresh authorized report rather than trusting client state.
A useful real-time map
A proper map uses real world geometry, not placeholder polygons. MetricFold renders country shapes from a versioned geographic dataset and places active markers at country centroids. It does not claim city, building or precise-person location. The accompanying table remains the exact source of the counts and is accessible without interpreting color.
Country detection should happen at the trusted edge where a privacy-preserving country code can be derived and the raw IP discarded. If a proxy supplies geo headers, only headers from explicitly trusted infrastructure should be accepted. Client-supplied country values are not trustworthy.
Live launch and incident questions
During a launch, watch the sequence rather than only the top-line count:
- Which campaigns and referrers are arriving now?
- Are visitors reaching the intended landing page?
- Are CTA impressions turning into clicks?
- Are signups starting and completing?
- Are errors, slow interactions or validation failures rising?
- Are verified checkouts or payments appearing after the expected delay?
During an incident, compare the live pulse with a recent baseline. A sudden fall in accepted page views may be collector delivery, edge configuration or traffic. Stable visits with rising action failures points toward product behavior. Stable conversions with delayed payment webhooks may be a provider or queue issue.
Bot traffic belongs in a separate stream
Search, preview, monitoring and AI crawlers can arrive in bursts. Mixing them into active visitors creates misleading launch numbers. MetricFold classifies known automation before the human report and keeps legitimate crawler observations in an AI and crawler view. Excluded totals and reasons remain available for diagnostics.
No user-agent list is perfect. Behavioral quality signals and edge rate controls complement the registry, while uncertain traffic remains labelled instead of being quietly transformed into “human.”
Live data still needs bounded queries
Real-time does not mean querying an unlimited raw event table on every message. Maintain bounded aggregates for the active window, cap recent-event lists and precompute expensive dimensions. The stream should carry a concise snapshot or invalidation signal, not every private event to every open browser.
MetricFold's wallboard uses the same principle at portfolio level. It refreshes the selected metrics from all authorized sites and external API connections without exposing connector tokens or endpoints to the display.
APIs for mobile and office displays
The live contract is useful beyond the web dashboard. A future native application can authenticate with a scoped API key, request the same bounded reports and subscribe to site-level streams. An office display can use wallboard mode with only the chosen metrics. MCP clients receive read-only evidence summaries instead of an uncontrolled database query surface.
Real-time analytics should shorten the time between a meaningful change and an informed response. It should not weaken privacy, query bounds or commercial event trust to create motion on a screen.
Design a realtime operating protocol
Define the action threshold
State which change deserves attention: checkout failure above a count, accepted traffic falling outside an expected launch band, verified payments delayed, or a key source sending the wrong landing page. Without a threshold and owner, a live display becomes ambient motion rather than an operating tool.
Keep historical context beside the pulse
Show a short rolling baseline, reporting-window definition and last successful update. “12 active” means little without the active window and normal range. Preserve the historical report as the source for analysis; a live snapshot can change while a team discusses it.
Record the response
When the team acts, create an annotation with time, observation, change and owner. Later compare the incident window with the same report definitions. This turns the realtime surface into evidence instead of a disappearing screen.
The browser Server-Sent Events API supports one-way updates and reconnection. MetricFold sends full bounded snapshots with a monotonic cursor and falls back to timed report refresh. It does not stream an unlimited raw event feed to the browser.
Validate live behavior before a launch
| Scenario | Expected dashboard behavior | Failure to detect |
|---|---|---|
| Accepted event arrives | Count/table/map updates without a page reload | Buffered or stale stream |
| Event comes from known bot | Human active count stays unchanged; crawler/exclusion moves | Polluted launch traffic |
| Stream is unavailable | State says retrying, then bounded polling | Frozen data presented as live |
| Tab is hidden | Unnecessary refresh work is suppressed | Worker/query waste |
| User loses site access | Stream/report authorization fails closed | Cross-tenant disclosure |
| Country is unknown | Event remains countable without a false coordinate | Invented location precision |
Plausible's realtime dashboard documentation is a useful benchmark for a clear active view. MetricFold extends the operating question into semantic actions, friction, trusted outcomes and the customer journey while retaining country-level rather than precise-person geography.
Frequently asked questions
Does the dashboard update automatically?
Yes. It opens an authenticated SSE connection and applies bounded realtime snapshots. If the stream is unsupported or does not open, the UI identifies the fallback and refreshes the authorized report on a timer.
Is the location marker precise?
No. MetricFold stores a coarse country code derived at trusted infrastructure and places the marker at that country's centroid. The table is the exact count; the map is a geographic summary.
Why can active users differ from the daily visitor total?
Active users use a short rolling window. Daily visitors use the report's identity and calendar boundary. They answer different questions and should not be reconciled as the same metric.
Can an office wallboard show several products?
Yes. A workspace can select site and external numeric metrics for a portfolio wallboard. The current builder is selection-based; it is not a free-form panel canvas with arbitrary queries and sizing.
Where should bot bursts appear?
Recognized crawlers belong in the separate crawler surface and rejected automation in traffic-quality diagnostics. The bot filtering guide defines accepted, excluded, validated and unknown labels. A live launch count must not increase merely because a search, preview or AI crawler executes the collector.
How is a live map release-tested?
Use real country geometry, seed multiple known country events, assert marker and table counts, check label collisions, and inspect desktop/mobile plus dark mode screenshots. Post another accepted event while the view is open and prove the marker changes without reload. Also test empty, retrying and polling states.
Retain the screenshot, event fixture and stream-state assertions with release evidence. A map that merely contains an SVG or a stream endpoint that merely returns 200 is not a meaningful visual or live-behavior gate.