Reading your dashboard

Unique visitors

Atriqo identifies a visitor with a hash — never a cookie — built from their IP and browser, mixed with a salt that rotates every day at midnight UTC. That's what makes the hash privacy-preserving: it can't be used to link the same visitor across two different days.

Within a single UTC day, the same browser on the same network counts once. If the IP address or the browser changes, the hash changes too; and if your site uses another time zone, your "today" spans two UTC days — so the same person can count more than once. Across a multi-day range, the hash changes every day. Treat unique visitors as an estimate — all the more so the longer the period.

Sessions and bounce rate

A session boundary in Atriqo is a fixed, clock-aligned 30-minute window — not a countdown that resets every time a visitor does something (the way GA4's inactivity-timeout model works). Every session hash is computed by flooring the event's timestamp into a 30-minute bucket aligned to the clock, not to that visitor's own first event.

That has a consequence worth knowing: two events 90 seconds apart can still land in different sessions if a bucket boundary falls between them. A visit from 10:29:30 to 10:30:30 — a single minute — crosses the 10:30 boundary and counts as two sessions. A common inactivity-timeout model would count that same visit as one continuous session. This is one of the reasons your session and bounce-rate figures won't match GA4 one-to-one.

Bounce rate is sessions with exactly one pageview, divided by sessions with at least one pageview. A session with zero pageviews (only a custom event, say) isn't counted on either side.

Visit duration

Average visit duration is the gap between a session's first and last event, in seconds. A session with only one event — the visitor left before triggering anything else — counts as a 0-second duration; it isn't excluded from the average.

Realtime

The realtime count is active visitors in roughly the last 5 minutes — a live, moving number, not a historical metric.

Comparing periods

Turn on comparison mode to see the current period against the equivalent previous one (this week vs. last week, and so on) side by side.

Filters and segments

Filter the dashboard by dimension — page, referrer, country, device, and more — to narrow any view down to the traffic you care about. Save a filter combination as a segment to reapply it later without rebuilding it.

Why the numbers won't match GA4

Two things above explain most of the gap: sessions use a fixed 30-minute clock window instead of a rolling inactivity timeout, and multi-day unique-visitor counts are an estimate rather than an exact figure. Different measurement models will always produce different numbers — that's expected, not a bug in either tool.