Skip to main content

Your dashboard

The metrics

Four tiles across the top of the dashboard.

Four tiles across the top of the dashboard. This page says exactly what each one counts.

screenshot coming

The four summary tiles across the top of the dashboard, populated with realistic non-round numbers — e.g. Views 12,483 / Unique visitors 3,912 / AI crawler views 1,247 / Verified crawlers 62%. Light theme, cropped to the tile row, desktop width.

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.

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:

ModeA visitor is
First-party cookie (default)One browser, recognised across days. A reader who returns next week is one visitor, not two.
Rotating hashOne browser, recognised within a calendar day (UTC). The same person on Monday and Thursday is two visitors.
Strict cookielessOne 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.

SeriesWhat it is
Solid areaViews over time, on the left scale
Dashed lineUnique visitors over time, on the left scale
Second seriesAI 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.

What is not here

  • Bounce rate — not built.

  • Average session duration — not built.

  • Pages per session — not built.

  • Conversion rate — there is no goals model on the dashboard yet.

  • Revenue — not built, and not planned.

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.

screenshot coming

The "AI-vs-human split" stacked bar card at the bottom of the dashboard, populated with several crawler families and a human segment. Light theme.

Was this page helpful?

Last updated August 28, 2026