Dashboard overview

Choose a website from Your sites or the site switcher, then open Overview. Reports apply to that website. Select the Seean wordmark to return to the homepage.

Use the sun or moon control in the header to change the appearance. Dark mode uses blue-grey backgrounds with a deeper sidebar and lighter cards, menus and dialogs; light mode uses warm neutral surfaces. The choice is remembered in this browser.

Tap the menu icon at the top left to open navigation. The hamburger animates into an X in the same position; tap it again to close. The icon transition respects your device’s reduced-motion preference. Choose a report, Your sites, Roll-up or Settings; use the website and account controls at the bottom to switch sites or open account settings. The menu scrolls on short screens. Choosing a different page closes it. To stay on the current page, use the close button, tap outside the menu or press Escape.

Read the overview

The top strip shows visitors, visits, views, bounce rate, session time and net revenue. Select any of the six KPIs to change the chart and its units. Each KPI’s small chart uses its own metric; changing the selection reuses the current analysis. Choose Trend for the selected KPI or Conversion peak for custom event timing. Selecting a KPI returns to Trend.

Below the chart, cards break down pages, sources, locations, devices and custom events. Pageviews appear under Views, Pages and the activity log rather than the Events card. Google search keywords are available after connecting Search Console.

The KPI strip is one row on wide screens, three cells per row on tablets and two on phones, with each small chart under its value except on the widest screens; card tabs wrap onto a second line, long labels in the breakdown lists are shortened with an ellipsis, and a table wider than its card scrolls sideways inside the card - a fade on the right edge shows while more columns remain. The page itself never scrolls sideways.

Conversion peak

Choose Conversion peak above the chart to see custom events grouped into Monday-Sunday rows and 00-23 hour columns. Darker cells contain more events within the selected period. Hover, tap or focus a cell for its exact count and hour. Each cell and its popup have a readable accessible name; arrow keys move between cells. On smaller screens, scroll the grid sideways to reach all hours.

The label shows the display time zone: your saved account timezone, or your browser’s timezone when no preference is saved (UTC on the public demo). Change it in account settings. Each event is placed using that timezone’s offset at the event’s timestamp, including daylight-saving changes. Repeated clock hours are added together; skipped hours contribute no events. The selected date range remains unchanged.

Only collected custom events count: pageviews, revenue orders and daily imported history do not. This is an event count, not a conversion rate or a count of configured goals. The Conversion selector first chooses visitors who triggered that goal in the period, including their other visits. Other dashboard filters select the same matching visits as the other Overview cards; all custom events within those visits count. For example, an event filter for signup can also include a later purchase in the same matching visit. Only the current period appears; the previous-period comparison is used by Trend.

The analysis starts when you open this view, reuses the existing calculation service and shows its computed period. Loading, updating and retry notices appear above the grid. No matching custom events produces an explicit empty state. Changing filters requests a separate result; this view does not appear in shared dashboards or the customer API/MCP. See custom events and date ranges and filters.

Add chart notes

Owners and admins can pin a short note to a day on the Trend chart: click a point on the chart, or choose Add note above it, to open the note dialog for that day. Pick the day with the date field (limited to the selected period), type up to 200 characters, choose one of six colours and select Add note. Existing notes for that day are listed in the same dialog with Edit and Delete. Notes are saved per website, up to 200 per website; viewers see them but cannot change them.

A day with notes shows a dashed marker line and a coloured dot at the top of the chart; hovering that day’s point lists the note text under the values. Days are calendar days in the display time zone, matching the chart’s daily buckets; on hourly views the marker sits on the day’s first hour. A note written in one time zone keeps its calendar date when a teammate views it in another. Notes are private to the signed-in team: shared dashboards, embedded widgets, reports and the API never include them. Filters and comparisons do not hide notes.

Take the guided tour

Open your workspace menu in the sidebar and choose Show tour to walk through the Overview. Use Next and Back to move between steps, or Skip / Close to finish. The tour follows your light or dark theme.

Set a period

Use the date control in the top bar. Where available, No comparison opens preceding-period, fixed-day-shift and custom comparison choices on supported reports. See date ranges and filters for how filtering changes a report.

Use selection menus

Property, funnel, step-type, exclusion-match and shared-dashboard date selectors follow Seean’s light or dark theme. Open a selector with a click or tap; the current choice has a checkmark. With the keyboard, focus the control, press Enter or Space, move with the arrow keys and press Enter to choose. Type to jump to a matching option, or press Escape to close without changing the value. Long lists scroll; unavailable controls are disabled while their request runs. Read-only values such as a website or account ID, an API endpoint or a one-time secret sit in a muted field: you can select and copy them, but not edit them.

Inspect a result

Click a supported breakdown row or the filter icon beside its count to filter the Overview. In an expanded card, the same controls apply the filter.

Each card shows its top 8 rows. Select the expand button in a card header to open the full list: switch tabs, type in the search box to match any part of a key (case-insensitive, matched on the server across the whole dimension), select Load more to page through 50 rows at a time, and click the Visitors or Revenue column header to sort the loaded rows. A search checks up to 1,000 final rows per page; the count of loaded and checked rows appears above the list. Full lists are calculated on demand for the current analysis’ captured data and period, without storing a second copy of every breakdown. Loading and errors appear inside the expanded card; Retry breakdown retries the request without discarding earlier loaded pages. If the analysis expired or its source data changed, refresh the analysis first. Rows without a supported filter have no filter button. Selected filters appear above the KPIs; remove one with its close button. Open Events in the sidebar for the individual activity log.

Select a card’s i button to read its explanation in a theme-matched popup beside the button. Click or tap outside it, or press Escape, to close it. The button also works with Tab and Enter/Space.

Understand report state

A calculation notice can show that results are being prepared or refreshed. Use the displayed computed time and period when checking whether two reports describe the same data. Compare the same website, filters, time zone and currency; a later calculation can include newly received records or refunds. An empty report can mean no matching data, an uninstalled tracker or paused collection; follow setup troubleshooting.

Reports use the automatic refresh schedule while visible and pause their clock in hidden tabs. A calculation prepares an exact result for its displayed period. Newly accepted records waiting to become available can keep a new report in its preparing state; they are not silently counted as zero. A waiting calculation asks the store to transfer those records immediately, so this state normally lasts well under a second instead of up to the ten-second background transfer cycle. Completed calculations keep their saved KPIs, charts, top rows and excluded-currency warning while releasing temporary work. Expanded Overview lists are calculated only when requested. Active calculations keep the state they need. Hourly cleanup expires calculations older than one day. This cache cleanup does not delete collected history or saved report files; a new calculation uses retained source records. Event, Web Vitals and order records follow the rolling three-year retention policy.

Accepted imported history joins the main KPIs, chart and available breakdowns for complete source days inside the selected range. Session filters exclude aggregates. Historical visitors are daily sums; missing source metrics show -. See imports for source definitions and skipped days.

A website reset excludes older raw records from new analyses immediately. Refunds, changed imported history, resets and source-data retention can make an on-demand breakdown unavailable for an older calculation. Refresh the analysis to obtain consistent totals and details; a request spanning such a change fails instead of mixing datasets. Saved results and report files are not silently recalculated.

New Overview calculations always use on-demand breakdowns; older clients cannot request a persistent copy of every detail row. If an older open browser tab asks you to reload the page to use the updated breakdown viewer, reload it before expanding a card. Existing stored snapshots remain readable until expiry or an explicitly requested cache reset. A cache reset can require a new calculation; it does not delete collected history or saved report files.

Native-only Overview lists fetch the leading rows and requested pages directly from the analytics store. Reports that merge revenue or imported history keep the exact merge rules instead of approximating their totals. That merge, and the compatible older full-list path, has a safety limit of 10,000 aggregate records or 4 MiB of serialized aggregate data across a calculation. This is not a limit of 10,000 source events. If exceeded, the calculation fails with an instruction to narrow the date range or add a filter; it never silently drops rows. Revenue and Campaign calculations using the same exact merge have the same bound. Busy expanded lists offer a retry; see analysis availability.

Something unclear? Contact support.