Understand page views, visitors and estimated sessions
Read the labels literally
| Metric | What it represents | What it does not establish |
|---|---|---|
| Page views | Retained accepted public-page observations | Every request or every human view |
| Daily visitor total | Sum of rotating daily identifiers | Unique people across a multi-day range |
| Estimated sessions | Fixed 30-minute hashed buckets | True visits, logout boundaries or engagement duration |
| Device | User-agent estimate | Verified hardware |
| Channel/referrer | Available browser referrer hostname/category | Search keywords or first-touch attribution |
| Goal hit | Observed selected destination path | Completed purchase, paid order or registration |
Only supported successful public GETs are eligible, after the visibility/consent checks. Logged-in traffic is deliberately limited to generic public landings; detailed signed-in pages are skipped. The daily identity derives from the existing session; the addon does not add its own tracking cookie or local-storage visitor ID. It does not store raw IP, member ID, email, search query or a fingerprint.
The signed collection ticket lasts 30 minutes and collection is capped per session bucket. Hidden-at-load pages, suspected bots, DNT and consent restrictions can cause gaps. Consent changes require the intended reload behaviour. Do not compare these privacy-limited figures with server logs as if they must agree.
Date filters use UTC. A partial current day, collection start and retention can make a previous-period comparison misleading. A zero says no retained matching observation, not necessarily no real audience.