Browse Analytics
Overview dashboard
The Overview is the first dashboard to open. It answers how much traffic the site had, who it was and what they read, on one page with no tabs.
Use it for a daily or weekly check. When a number looks off, the other dashboards go deeper: Acquisition for where visits came from, Engagement for what they did, and Trend and anomaly for what changed.
Good to know
- Every tile reads page views, so it fills as soon as the website tag is on your site.
- Active users and Stickiness keep their own 90-day range and ignore the filters.
- Visitors are devices, from a first-party cookie, and Safari clears that cookie after 7 days without a visit, so returning Safari visitors can count as new.
At a glance
Traffic, active users and content for this site.
- Tabs: none, one page
- Charts and numbers: 15
- Built on: the Page views explore
Filters
The filters across the top apply to every tile they can, unless a tile says it has its own range.
- Date range: the last 30 days, today included.
- Allowed origin: set to true, so tiles count only the origins your property allows. Clear it to see every origin the tag ran on.
Tiles
| Tile | Kind | What it shows |
|---|---|---|
| Unique visitors | Number | Distinct device cookies in range. Optimistic on Safari, which clears the device cookie after 7 days, so a returning visitor can count as new each week. |
| Sessions | Number | Visits, on a 30-minute sliding idle window shared across tabs. Not a count of page loads. |
| Page views | Number | Every page view in range, including client-side route changes. Bot traffic and visitors who declined consent are already left out. |
| New visitors | Number | Devices whose first-ever page view fell in range. Over several days this overlaps Returning visitors, so the two do not sum to Unique visitors. |
| Pages per session | Number | Page views divided by sessions. A depth measure, not an engagement one: a visitor who reads one long page scores 1. |
| Signed-in users | Number | Distinct application user ids, from pageTracker.identify. Zero on a site that never calls it, which is the normal state for a public page rather than a tracking failure. |
Active users
| Tile | Kind | What it shows |
|---|---|---|
| Active users (last 90 days) | Line chart | Distinct devices active on the day, in the trailing 7 days, and in the trailing 28, on the site's allowed origins. Rolling windows, so they do not reset on a calendar boundary. This tile has its own 90-day range and does not follow the dashboard's filters. |
| Stickiness (last 90 days) | Line chart | Daily actives as a share of the trailing 28-day actives, on the site's allowed origins. Volatile at low volume: read it alongside the counts it divides. This tile has its own 90-day range and does not follow the dashboard's filters. |
| New vs returning visitors | Stacked columns | Devices seen for the first time, against devices seen on an earlier day. New is an upper bound: a visitor whose device cookie Safari dropped returns as new. |
| Sessions and page views | Line chart | Visits and the pages they viewed, by day. Page views are on the right-hand axis because they run several times sessions. |
Content
| Tile | Kind | What it shows |
|---|---|---|
| Top pages | Table | Most-viewed pages in range. Paths are decoded and redacted, so high-signal segments read as |
Audience
| Tile | Kind | What it shows |
|---|---|---|
| Visitors by device | Pie chart | Bucketed from browser window width, not from the User-Agent, so a narrow desktop window reads as mobile. |
| Top countries | Bar chart | Visitors by country, from their IP address. IP Geolocation by DB-IP, licensed CC BY 4.0. |
| Sessions by channel | Bar chart | How each visit arrived, from its first page view, so every visit is counted in exactly one channel. |
| Top referrers | Table | Registrable domain of the referrer, so subdomains of one site collapse into it. Blank means direct, or a referrer with no public suffix such as localhost. |
About this dashboard
The date range at the top moves every tile except Active users and Stickiness, which are written in SQL and carry their own 90-day window.
Bot traffic and visitors who declined consent are already excluded. Visitor counts come from a first-party cookie, so a browser that clears it counts the same person twice - Safari does this weekly.