The summary tiles across the top of the dashboard — two rows of four. This page says exactly what each one counts.
Views
Every page view. A page load counts one, and each in-app navigation in a single-page app counts one more.
Not unique — a visitor who reads four pages contributes four views.
By default this counts human views only, because the "Hide bots" filter is on. The tile's subtitle tells you which state you are in: Human only or All traffic.
Revenue
Only appears once you connect a payment provider. Until then the tile is absent rather than showing zero — nothing is being measured, and a zero would say your revenue was nothing.
It sits second, right after visitors, because it answers the question the rest of the dashboard is building towards: which channel brought the money.
The figure is what settled into your payment account, so it matches your Stripe dashboard. Refunds are shown separately rather than subtracted, for the same reason Stripe lists them separately.
See Revenue for how to connect one.
Unique visitors
Distinct visitors in the selected range.
How a visitor is identified depends on your site's identity mode, and it changes what this number means:
| Mode | A visitor is |
| First-party cookie (default) | One browser, recognised across days. A reader who returns next week is one visitor, not two. |
| Rotating hash | One browser, recognised within a calendar day (UTC). The same person on Monday and Thursday is two visitors. |
| Strict cookieless | One rough population bucket, within the hour. Everyone behind a shared connection on similar devices merges into one. |
See Identity and cookieless mode for the mechanism and the trade-offs.
Why this differs from Google Analytics. GA identifies a visitor with a long-lived client-side identifier and stitches sessions together with more signals than we collect. TrueStat deliberately collects fewer. On the default mode the numbers are comparable; on the two cookieless modes TrueStat's will be higher over long ranges (the same person recounted) and its returning-visitor figures unavailable. Both are correct answers to different questions.
A note on adding up. Unique visitors over a 30-day range is not the sum of the 30 daily figures. A person who visits on five days is one visitor in the month and five in the daily sum.
AI crawler views
Page views from AI assistants and AI training crawlers — the ones ChatGPT, Claude, Perplexity and their peers make.
This tile ignores the "Hide bots" filter. It counts crawler traffic unconditionally, because it exists to report the traffic the human view filters out. Turning bots on and off changes the first two tiles and leaves this one alone.
Crawler views and human views are counted separately and do not add up to a total. They are two populations, drawn on two scales on the traffic chart for that reason.
This number currently undercounts. Crawlers that request raw HTML without running JavaScript never reach a browser script, so they are invisible to it. How reliable is it explains by how much and what is being done about it. Read it before you quote this number.
Verified crawlers
Of those crawler views, the share that could be confirmed against the operator's published IP ranges rather than merely claimed by a user-agent string.
A dash (—) means no crawler has visited yet. It does not mean 0%.
Those are opposite findings and must not look alike: 0% means crawlers came and not one could be verified, which is a spoofing signal worth looking at. A dash means nothing arrived.
Some operators publish no IP ranges at all, so their traffic can never be verified and always sits in the unverified share. See Which crawlers are recognised for which ones can be verified and which cannot.
The traffic chart
Below the tiles.
| Series | What it is |
| Solid area | Views over time, on the left scale |
| Dashed line | Unique visitors over time, on the left scale |
| Second series | AI crawler views, on the right scale |
The right scale exists because crawler traffic and human traffic are usually orders of magnitude apart. Drawn on one scale, whichever is smaller would be invisible.
They do not sum. The chart shows two populations side by side, not a stacked total.
The AI crawler series is hidden when you turn the bot filter off, because in that state human views already include crawlers and a second series would be the same data drawn twice.
Bounce rate
The share of visits that saw one page and left.
A visit with a single page view counts as a bounce whatever its length — there is no time threshold. That means a reader who spent four minutes on one article and left satisfied counts the same as someone who closed the tab immediately. Bounce rate answers "did they go further", not "was it any good".
Session time
How long a visit lasted, from its first event to its last.
This is a median, not an average, and visits under five seconds are left out. Both choices exist for the same reason: one person leaving a tab open overnight drags an average into the hours, and a median over every visit lands on the zero-second ones, because roughly half of all visits are a single page. Excluding the shortest visits and taking the middle of the rest gives a number that describes actual reading.
The tile also shows how many sessions that median covers, since a median over nine visits means something different from one over nine thousand.
Drawing either one over time
Both tiles can be clicked. The chart then shows that one figure across the range and switches the traffic series off.
The two cannot share an axis with the visitor count: one is a share of sessions, the other a duration, and neither is a number of people. A chart carrying both would be comparing quantities that have nothing in common. Clicking the tile again brings back whatever was on before.
The line follows the same rules as the tile above it — the same median, the same five-second threshold — so the two can never disagree about a day.
Online
Visitors active in the last ten minutes, refreshed every thirty seconds.
It ignores the date range above it — "right now" is the same question whether you are looking at today or at last quarter.
What is not here
Pages per visit — computed and used inside channel quality, but not shown as a headline tile.
New vs returning — only under the cookie identity mode, and not yet surfaced as its own metric.
AI-vs-human split
At the bottom of the dashboard, a stacked bar showing page views classified by user agent. Like the AI crawler tile, it always includes bots regardless of the filter above.