Analytics

Analytics is the exploration layer on top of everything your beacons collect: who's on the site right now, where traffic comes from, which pages get viewed, which errors fire, and how whole visits unfold. It complements the Web Vitals dashboard: same data, different question. Web Vitals asks "how fast is the site?"; Analytics asks "what's happening on it?"

The dashboard

The main Analytics view for a site shows:

• Current visitors: unique visitors in the last 5 minutes, expandable to a per-minute chart of the last 15.
• Three headline metrics: Unique Visitors, Pageviews, and Views per Visit, each with a sparkline and the change against the previous period.
• Trend chart: the headline metrics over the selected range, with an optional previous-period overlay.
• Breakdowns: four panels for Sources, Pages, Locations, and Devices, each with sub-tabs for drilling down (channel vs. UTM source, country lists, browser vs. OS, …).
• Campaigns & attribution: UTM coverage and source/medium/campaign lists, including ad-platform click-ID labels.
• Tech panel: back/forward-cache hit rate, top third-party categories, and whether errors originate first- or third-party.

Visitor counts are anonymous by construction; see Privacy for what a "visitor" can and cannot mean here.

Filtering

A filter bar sits next to the time picker on the dashboard, the overview, and every metric detail page. Type a dimension and value (for example country = DE) and press Enter to add a filter chip; the value field autocompletes with the real values for the current time range and shows how many pageviews each one has. The dimension picker lists the most-used dimensions first (Page, Country, Device), then the rest: browser, OS, connection, viewport, referrer source and medium, UTM fields, click-ID label, domain, navigation type, and protocol.

Filters live in the URL, so they survive a reload, are shareable, and carry across navigation between views. Multiple chips combine with AND; a comma inside one value means "any of". Click a chip to edit it; its X removes it. The "Filter" button carries a badge with the active count.

Navigating with the command palette

Press Cmd/Ctrl+K (or the command button in the top bar) to open a searchable command menu that drives the whole app: jump to any page, switch organization or site, change the time range and granularity, and add, remove, or clear filters. Start typing to search everything at once, or drill into a category with Enter or →; ← or Backspace steps back and Esc closes.

Error Analytics

The Errors view tracks JavaScript errors across the site:

• Error rate over time: the share of pageviews with at least one error.
• Error types: errors grouped by fingerprint (type + message
  • stack shape), ranked by count.
• Detail drill-down: for one fingerprint: total count, visitors affected, first/last seen, a time series, breakdowns by URL, browser, device, OS, and country, and sample pageviews with stack frames.

How much detail you see depends on the site's tracker settings: error type and count arrive always. The error message needs collect_error_messages, and full stack frames need collect_error_frames.

Visitors

The Visitors explorer lists distinct visitors (start and end time, duration, page count, device info, average LCP/FCP, error count) with filters, and a per-visitor detail view showing every pageview in order, each with its Web Vitals and errors.

A visitor is counted along an identity axis: stitch (present when store_stitch is on) or session (the cross-page session_id, present when collect_sessions is on). The site's count_visitors_by sets the default. New sites start on Standard, which stores stitch, so the visitor explorer works out of the box; the Minimal preset stores neither identity and leaves it empty. The per-visitor replay needs the session identity. See Visitors and sessions for the full model.

Fetch/XHR and Server-Timing

Beyond page navigations, the dashboard surfaces in-page request telemetry: a Fetch/XHR view with an aggregate waterfall (per-endpoint start offsets, duration histograms and percentiles, and a status-error distribution), plus a per-beacon detail, and a Server-Timing view that breaks out the Server-Timing metrics your backend reports. Both are driven by fields the tracker adds to each beacon (see the beacon).

The Server-Timing view is new: the beacon already reads the header on every pageview, and the dashboards on top of it are still being tuned. To emit the header and learn how fastmon splits it into backend phases, cache status, and custom keys, see Server-Timing headers.

Experience Score

The Experience Score panel breaks the score down by segment (all visitors, desktop, mobile, and slow connections), each with its grade, numeric score, and the per-metric values behind it. Useful for the classic case where the overall grade looks fine but mobile-on-3G is failing.

API

Every panel maps to a query endpoint under /v1/organizations/{org_id}/analytics/…: a flexible query endpoint for time series and breakdowns, plus dedicated endpoints for histograms, error types and details, visitors, Fetch/XHR, Server-Timing, resource and third-party breakdowns, LoAF, and the Experience Score. See the Analytics endpoint reference.

What's next

• Tracker settings: what the tracker collects per setting, and why the session identity or stack traces may be missing.
• Visitors and sessions: how pageviews become visitors and sessions.
• Synthetic Monitoring: the lab-data complement to these field dashboards.