Overview & visitors metrics

The overview page cards and their definitions, the visitors realtime capsule, and how they differ from the mKit reports.

Overview#

The overview page (`/dashboard`) summarises a site: traffic, search, key events, content, performance and monetization, drawing mainly on GA4 and GSC.

  • Endpoint: `GET /api/v1/overview`, with `range`, `compare` and `site` parameters.
  • The page degrades per source: without GA4 the traffic / content / visitor-group sections show a connect prompt; without GSC the search section does.
  • There is no backend plan gating; it is visible on Free too.

Cards and definitions#

Main cards and their definitions:

CardDefinitionSource
Visitors / usersActive users in the sessionGA4
Pageviewspageviews (screenPageViews)GA4
Bounce ratebounceRateGA4
Avg durationaverageSessionDurationGA4
Key events / conversionsCount of Key EventsGA4
Search clicks / impressionsGSC clicks / impressionsGSC
Note: Overview metrics use native GA4 definitions; "Key events" depends on the Key Events you mark in GA4 — when none are marked the section is empty and prompts you to the goals settings.

Realtime capsule#

The visitors page (`/dashboard/visitors`) has a realtime headcount capsule at the top, polling `GET /api/v1/reports/realtime` every 30 seconds; it returns `{ visitors: number }`.

  • The endpoint queries only the current active-user count, over the GA4 Realtime default window (product copy consistently calls this "the last 30 minutes").
  • The server caches it for 30 seconds (KV TTL 60 seconds).
Note: `/dashboard/reports/realtime` is not a standalone feature — it redirects straight to `/dashboard/mkit/live`.

Definition notes#

  • The overview "conversions" rely on GA4 Key Events; this differs from mKit conversion tracking (Forms & AFF, based on events such as `form_submit`).
  • The realtime capsule headcount and the overview visitors use different time windows, so the numbers are not meant to match.
  • Search clicks (GSC) and sessions (GA4) are two different definitions; across sources, treat differences as directional only.
Tip: For trend decisions, compare within one source and one time window.
  • Data latency & metric definitions: /data-latency
  • Data sources overview: /data-sources
  • Plans & feature gating: /plans