Reading Overview
Overview is the main view of a site. Almost everything on it — the hit counts, the chart, and every table below it — answers the same question for whichever date range you have selected. Change the range and the whole page moves with it. The single exception is Top pages (all time), which ignores the date filter on purpose.
The chart
Pick a range from the filter bar: Last 24 Hours, 7 Days, 30 Days, All Time, and the rest. Multi-day ranges can be grouped by day, week, month, or quarter, so a year of traffic does not turn into a wall of noise. A single day is grouped by hour instead.
Where the week begins is your choice, not ours. Week starts on in your account settings decides whether Sunday or Monday opens the week, and This week, Last week, and the weekly charts all respect it.
Two numbers sit above the chart:
- Hits are page loads. Every view counts, including the reader who refreshes three times.
- Unique hits, if you have enabled them, estimate how many different browsers those loads came from. The word estimate is doing real work in that sentence — see unique hits for what we do and do not know.
On a paid plan you can also decide which summary cards appear above the chart — lifetime views, a traffic graph, or uptime status — under Settings → Appearance → Site overview card.
The tables underneath
Every block below the chart can be hidden or reordered under Settings → Appearance → Stats sections. A dashboard you have pruned to the four things you care about is worth more than one showing everything.
Goals appears once you have defined at least one, and shows conversions and conversion rate alongside it. See goals.
Top pages ranks the most-viewed pages within the range you picked. Top pages (all time) is a separate block that answers a different question — what has done well ever — and so it deliberately ignores the date filter. New sites start with it hidden; existing sites keep whatever they had.
User journeys and Sessions are both paid features and are easy to mix up. A journey is a visitor who saw more than one page in the range, which is what you want when you are asking how people move through the site. A session is every visitor we saw, single-page visits included. Neither is a durable person: the underlying hash rotates with the day, so the same reader tomorrow is a new row. Unique hits explains why.
Referrers shows where traffic came from — Direct, external sites, and Internal, which is usually hidden by default. An AI assistants chip on that table groups human click-throughs whose Referer host is a known assistant; it is not a complete picture of AI traffic, because a stripped Referer still shows up as Direct. We record exactly what the browser tells us, and browsers have become much less forthcoming: LinkedIn, Google, and many others now send only the origin (linkedin.com, google.com) rather than the page or the search terms. That is their referrer policy, not a limitation we can code around. For search terms, use Google Search Console. On links you control, UTM parameters still work perfectly.
Sources is the utm_source surface (plus Tinylytics tiny_source / ts / ref). It is unchanged.
Campaigns is a separate table for utm_campaign and utm_medium on those same links. It stays hidden until a tagged visit arrives after this shipped — older hits are not backfilled — and you can still hide or reorder it under Appearance. Click a campaign or medium to filter the rest of Overview.
Countries comes from the visitor’s IP address, which is used for the lookup and then discarded. Country is as specific as it gets — there is no city and no map pin.
Browsers and Platforms are two separate tables: Chrome, Safari, and Vivaldi in one; iOS, Android, macOS, and Windows in the other.
AI agents is hidden until you ask for it. It counts visits from known assistants and crawlers, and it is kept out of your hit totals so that a curious language model cannot flatter your traffic. See AI agent traffic.
Filters
The date picker is the main filter, and for most questions it is the only one you need. You can also filter to a single path, but note that the path filter is an exact match: filtering to /docs will not include /docs/api. That is precise, and occasionally not what you meant — when you want a whole section treated as one thing, use segments instead.
Insights
The Insights tab is the same data read back to you in sentences: what moved this week, which pages rose, which referrers are new. Insights covers how it works and how to turn it on.