Analyze6 min read
The dashboard, page by page
The dashboard has one home page (Overview) and a set of pages that each zoom into one slice of the same underlying data. This page is a map of all of them, not a deep dive into any one: every page that has more to say gets its own guide, linked at the bottom.
Overview: the KPI row and chart
The top of Overview is a row of headline numbers for the selected range: Visitors, Pageviews, Sessions, Bounce rate, and Avg session (duration), plus Revenue and ARPV once you've recorded any revenue events. Each card shows the percentage change against the immediately preceding period of equal length.
Below the KPI row is the main chart: a daily series you can switch between Visitors, Pageviews, Sessions, Avg session, and Bounce rate, with a revenue overlay when there's revenue to show. A second strip below the chart adds Bounce rate, Pages / session, Avg session time, and New vs returning as smaller trend cards.
Visitors, Pageviews, and Sessions are counted from the authoritative per-session record, so the headline, the chart, every breakdown table, and the Visitors page all agree with each other by construction. See Reference: metrics for exact definitions.
Range, comparison, and freshness
Every page shares the same range picker in the top-right: presets from Today up to Last 12 months, a custom range, and a Compare switch. The full behaviour, including what "today" means in your timezone and how fresh the numbers are, is covered in Date ranges and comparisons.
The breakdown pages
These pages all answer "who, or what, made up that headline number" for the active range and filters. None of them has a dedicated guide beyond this page, because each is a straightforward breakdown of the metric you choose (Visitors, Visits, or Pageviews) by one dimension.
Pages- Every path visited, ranked by your chosen metric, plus separate top-entry-page and top-exit-page lists. Entry and exit pages are always counted in unique visitors, regardless of the metric toggle, so that card stays on one consistent unit.
Sources- Where visitors came from: referrer and medium, new-vs-returning split by source, outbound-click and download destinations, and a revenue-by-source breakdown. UTM-tagged traffic shows up here too.
Devices- Top device types, browsers, and operating systems, ten of each.
Geo- Countries, regions, and cities. Regions and cities are always counted in visitors: they're a reach view, not a visits/pageviews one.
Campaign links (UTM)- A builder for tagged URLs (newsletters, ads, social, affiliates), not a stats page. Once a tagged link gets clicks, the attribution shows up on Sources.
Performance- Core Web Vitals (LCP, CLS, INP, TTFB, FCP) graded at the 75th percentile against the standard good/needs-work/poor thresholds.
Revenue- Total revenue and ARPV (revenue ÷ visitors) for the range, a daily series, and a breakdown by traffic source. Sourced from events you've marked as revenue, not from rollup guesswork.
Journeys- The most common page sequences visitors actually walked, read from the ordered pageview rows of each session and shown to a depth you choose (up to 5 steps, top 12 sequences). Only multi-page sessions count, and a page repeated back to back (a reload, or an SPA re-render) collapses into one step. On a busy range the walk is drawn from the most recent 4,000 multi-page sessions and the page says it's a sample.
Visitors and replay
Visitors lists every distinct person seen in the range with their first/last-seen times, session and pageview counts, and a drawer that opens their full journey, covered in Visitors and the visitor drawer. Replay plays back real sessions recorded by rrweb, with form inputs masked by default; consent to record is on you to obtain from your own visitors.