Dashboard tour

The dashboard fits in three screens: Statistics, AI traffic and Settings. They sit in the top bar (on a phone, in the bottom bar). No side menu: each screen reads from top to bottom.

#The three screens

In bar order. You land on Statistics by default.

1. Statistics — your visit statistics on a single page: visitors, pages, sources, places, devices, events and sales (detail below).
2. AI traffic — two things, never added together. AI robot hits, per vendor, per robot, per page and per day, as each robot declares itself and counted to the exact number (you need the WordPress plugin or the server module to see them). And visitors sent by an AI assistant, which are a minimum: most AI apps don't pass on where the visitor came from. Those human visitors stay under a threshold that protects small numbers. The screen's only tool generates your robots.txt. See How AI traffic is measured.
3. Settings — managing your sites, installing the code and privacy, gathered in three sections.

The three sections of Settings:

• Sites — the selector order, pausing collection, renaming, the client note, archiving and erasure, plus the client report emailed every week. See Settings › Sites.
• Installation — the Snorklee code, verification, troubleshooting, platform guides, the server module that catches robots, the WordPress plugin, blocker bypass, Search Console & Bing, API keys and the sensitive zone.
• Privacy — your international privacy file, a status banner worked out for you, the electronic DPA signature, retention periods, export and erasure, and the data protection contact.

#Statistics — a single page

At the top, four numbers: unique visitors, pageviews, average duration and engagement rate, then the traffic chart. Just below, the honest warnings (too little traffic, privacy threshold reached) where they apply.

What these four numbers mean exactly:

• Unique visitors — different people, counted day by day. The anonymous fingerprint that recognises a visitor changes every day (that is what protects their privacy): a person who comes back on another day counts again. Over a period of several days, the number therefore adds up each day's visitors. It is an estimate, accurate to about 1 %.
• Pageviews — every page load by a human, robots excluded.
• Average duration — the average time of a visit, visits with no measured time included. A page's time stops the first time it goes to the background (tab switch, phone locked) and is capped at 30 minutes per page.
• Engagement rate — the share of visits where at least one page was scrolled halfway down, or stayed on screen for 30 seconds or more. Clicks are not part of the calculation. The bounce rate (weekly report, export, API) is its complement, 100 % minus engagement: so it is not "a single pageview".

With no completed visit in the period, duration and engagement show "—", never a 0.

Then come five blocks, each with its own tabs:

Clicking a row filters the whole page on that value; clicking the same row again removes the filter. Active filters show as chips above the numbers. Rows in the Downloads and Outbound links tabs do not filter. See Filters.

AI robot hits are not on this screen: they are on AI traffic.

#At the top of the dashboard

• The site selector, whose order is set in Settings › Sites.
• The period picker — the "Filter" button. See Filters. The AI traffic screen has its own period (24h / 7d / 28d / 90d), limited by how long we keep the detailed data.
• The comparison — the "Compare" button. See Period comparison.
• The "Download all data (CSV ZIP)" button, at the top of the Statistics screen. See Export and erasure.

#Each block stands on its own

Each block is self-contained: it loads its own data, manages its own display, and applies the same privacy rule to everyone, the site owner included. A simple list (one single piece of information) is exact for all. But as soon as you cross two pieces of information (a country and a browser, say, or a list viewed under a filter), we hide the very small numbers: cells below the threshold are grouped or hidden, never shown as "1".

One deliberate exception: robots are counted to the exact number, with no masking. That masking exists to protect a person, and there is nobody behind a GPTBot. In return, the rule is strict: anything that counts humans stays protected, and we never mix robots and humans in one total — otherwise you could work the human count back out by simple subtraction.

If one block breaks, the others keep showing.