> ## Documentation Index
> Fetch the complete documentation index at: https://docs.openrevenue.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Realtime

> Understand how OpenRevenue counts active visitors and powers realtime website analytics.

## How realtime works

The tracker sends lightweight `ping` heartbeats every 15 seconds while the tab is visible. These heartbeats keep the live count, country list, sparkline, and realtime map fresh.

> [!NOTE]
>
> If a visitor switches tabs, closes the page, or their browser throttles background work, OpenRevenue stops treating that tab as actively engaged until it becomes visible again.

## Active users

The main realtime number is an event-window “active users in the last 30 minutes” count. A visitor is counted when they have a pageview in that window plus a heartbeat at least 10 seconds after the pageview, or when their pageview is fresh enough that the engagement heartbeat is still pending.

OpenRevenue also keeps a stricter recent window internally. That window uses at least 2 heartbeats in 5 minutes, or the same fresh 90-second pageview grace.

The small per-minute chart is pageview-based and uses fixed minute buckets: the newest bar starts at 0 when a minute begins, fills as users register pageviews during that minute, then shifts left when the next minute starts.

## Accuracy

Realtime tools do not all count active visitors the exact same way. OpenRevenue avoids counting every one-off pageview for a full 30 minutes, because that can inflate the live number when visitors bounce quickly.

Compared with Google Analytics, OpenRevenue's number should be close but not always identical. Differences can come from blocked scripts, background tabs, browser throttling, ad blockers, bot filtering, network latency, and deploy timing for the latest tracker script.

## Storage

Realtime presence is stored in Redis. Heartbeat pings are not written to the analytics event stream in ClickHouse and are not written to Postgres analytics tables.

Monthly usage counts pageviews and custom events only. Pings, outbound links, transactions, and performance events stay out of billing usage.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.