What It Is
The dashboard is the board where StatelessID shows every aggregate it has counted for your domain — page views, top pages, referrers, countries, languages, screen sizes, load speed, and errors — for any date range you choose, without identifying a single visitor.
One board, one domain, one range
Every screen under the dashboard belongs to a single domain at a time. The domain selector in the sidebar lets you switch between every domain registered to your account. When the board loads, it defaults to the last seven days. You change that window with the range pills across the top of the page: today, yesterday, last 7 days, last 30 days, this cycle, or a custom date pair you type in.
The board does not show a person. It shows counts grouped by the two-segment path class of the URL, the host of the referring site, the screen resolution band, the two-letter language code reported by the browser, the country inferred from the request, the load-speed band, and the error class. Every cell in every table is a whole number — not a name, not an identifier, not a cookie value.
StatelessID counts page views from a single event beacon that fires once per page load on your site. One load, one count. There is no session stitching, no return-visit join, and no cross-request chain that requires recognising the same browser twice. The board is built entirely from those individual, unlinked counts.
What the board shows
At the top, four metric tiles give you the headline numbers: total page views for the selected range, today's count so far, the count from the last 15 minutes, and how much of your monthly quota is still available. These tiles always reflect the full unfiltered range, even when you switch the event filter below them.
The area chart below the tiles draws visits by day across the selected range and overlays the equivalent prior period so you can see whether trend is up or down at a glance. Below the chart, a quota bar shows how much of your monthly cap has been consumed this cycle.
Two side-by-side cards show the top page groups and the top referrer hosts for the range. A four-card strip below them covers countries, languages, screen resolutions, and load bands. If script errors were recorded in the range, an error-classes card appears just below the strip.
A collapsible drawer near the bottom of the board holds the less-frequently-needed tools: page-value assignments, extended languages and load-band tables, error classes, period compare, filter impact, and the fix list. Collapsing them keeps the top of the board clean without hiding anything permanently.
What the board does not show
The board does not show sessions, bounce rate, or time on page. Those metrics require joining one request to the same browser's next request — a behavioural identity join. StatelessID's architecture cannot make that join and will not attempt it. What the board calls "page views" is a raw count of accepted beacons, not a cross-request deduplicated count. That is what stateless means in practice.
There is no live-people widget, no funnel, no replay, and no device fingerprint. A visit from the same browser to the same page on two separate days counts as two page views. That is the correct answer to the question "how many times was this page loaded?" — and it is the only question StatelessID answers.
Privacy floor and the Other bucket
Each ranked table on the board has a minimum count threshold. If a row has fewer than five events, it does not appear as a named row. Rows below that floor are folded into an Other entry at the bottom of the table. This prevents the board from acting as a side channel when only one or two requests hit a rare path or arrive from a rare country in the selected range.
The Other bucket still counts toward the page view total shown in the metric tiles. No visit is silently discarded from the overall total — the floor only affects table display. If you are in a quiet period or a new installation with very few page views, most path and referrer rows may show only as Other. That resolves on its own as traffic grows.
Filtering by event type
The metric pill row just below the date range pills lets you filter the board by event type. Switching from Page views to a specific event code reruns all counts and tables for only that event type — the chart, the pages table, the referrers table, and the main count tile all update in place. The Cycle left tile stays on the full monthly count regardless of the event filter, because quota is always the total across all event types.
You can export the board's data to a CSV file at any time using the Export CSV button in the board header. The file contains path groups, referrers, countries, languages, resolutions, load bands, and error classes as aggregate counts. There is no row in the export that identifies a visitor.
Troubleshooting
If the board shows zero for every metric, the script may not be installed or the domain name in your account may not match the host where the script runs. Work through the no-data-yet checklist before changing anything else.
If a page group you expect to see is missing, confirm that path had at least five page views in the selected range, and that the URL did not contain a query string — query strings are stripped before the path class is stored, so two different query strings on the same path merge into one row.
If the range selector does not appear, reload the page. It is rendered in the response and does not depend on a separate request.