Updated on 2026-03-16 00:00:00 UTC
Status Page View Analytics
StatusPage.me includes built-in privacy-friendly view analytics for public status pages.
These metrics are designed for operational visibility (for example, during incidents), not marketing profiling. We intentionally avoid cookies, persistent identifiers, and third-party trackers.
What We Measure
We currently track four metrics:
Total Views
- How many times your status page was loaded for a day/period.
Approximate Unique Visitors (Daily)
- An estimate of distinct visitors for a given day.
- This is approximate by design because we do not use persistent user IDs.
Incident-Period Views
- Views that happened while an incident or maintenance window was active.
Incident-Period Unique Visitors (Daily)
- An approximate count of unique visitors seen during an incident or maintenance window for that day.
- Like the general unique visitor metric, this is privacy-friendly and intentionally approximate.
Where You Can See These Metrics
You can access built-in view analytics from the user dashboard in a few different ways.
Quick 30-Day Snapshot on the Status Pages List
On Status Pages, each page has a small Analytics button.
That quick view gives you a compact 30-day summary, including:
- Uptime
- Average response time
- Incident count
- Total downtime
- Approximate unique visitors
This is useful when you want a fast operational snapshot without leaving the status pages list.
Deeper Analytics Workflows
The quick snapshot links into the broader analytics workflow for that status page.
For uptime and longer-range operational breakdowns, also see:
Privacy Principles
StatusPage.me view analytics are built around strict privacy guarantees:
- No cookies for this analytics feature
- No localStorage identifiers
- No persistent cross-day visitor IDs
- No browser fingerprinting
- No cross-site tracking
- No raw IP address storage
- No third-party analytics service required for these counters
How Page Views Are Counted
When a status page finishes loading, the browser sends a small beacon request to StatusPage.me.
The request only includes minimal data needed to count the event safely. The server then places that event into an internal queue and processes it asynchronously.
This means:
- Status page rendering stays fast
- Analytics processing does not block page delivery
- Events can be retried safely if background processing is delayed
How Daily Unique Visitors Work
To estimate daily unique visitors without cookies, we compute a daily anonymous hash.
The hash input combines:
- status page ID
- day bucket (UTC date)
- truncated IP prefix
- normalized user-agent category
- rotating daily salt
The combined value is hashed with SHA-256.
Because the day bucket and salt rotate daily, the hash changes every day. This prevents cross-day visitor tracking.
Why Unique Visitors Are Approximate
Unique visitors are approximate because we deliberately choose privacy over persistent identity tracking.
For example:
- A person using different devices may count more than once.
- Different people behind the same network may occasionally be grouped.
For incident impact and operational trends, this tradeoff is intentional and privacy-preserving.
What Data Is Stored
We store aggregated daily counters and anonymous daily deduplication hashes.
Stored fields include totals such as:
- total views
- approximate unique visitors
- incident views
- incident unique visitors
We do not store raw IP addresses or persistent per-visitor profiles.
Reliability and Performance
The analytics pipeline is built to be lightweight and resilient:
- quick beacon endpoint response
- queue + background worker processing
- retry logic for transient failures
- graceful degradation under load (analytics can be dropped, status pages still load)
This keeps status pages available even during high-traffic incidents.
Troubleshooting
I see uptime and response data, but visitor numbers are approximate
That is expected. Unique-visitor counting is intentionally privacy-friendly and avoids persistent identifiers.
My quick analytics button shows less detail than I expected
The quick snapshot is designed for a compact 30-day operational view. Use the linked analytics pages when you need longer-range or more detailed uptime analysis.