Skip to content
Docs
CtrlK
Go to Dashboard

Account

Monitor real users with RUM

Lab vs real-user places the latest laboratory run next to consented field data from real page loads. Turning collection on is a single button, but the collector stays dormant until your consent manager signals a visitor, and the report is built purely from aggregates: percentiles, distributions, and coarse segments, with nothing that identifies a visitor or a page. Sustained field regressions appear as an in-dashboard list that a person acknowledges by hand.

How it works

  • Field collection is switched on from Lab vs real-user; there is no SDK install screen, and collection stays dormant until consent
  • Four metric cards, a Core Web Vitals distribution, a field budget verdict, and seven coarse breakdowns — all built from consented samples
  • A regression opens only after degradation across two consecutive 24-hour windows with at least 75 valid samples in each
  • Alerts are delivered by someone opening the screen and pressing Acknowledge; the dashboard has no email, webhook, Slack, or GitHub channel

Good to know

  • No URLs, paths, raw referrers, country codes, IP addresses, user agents, or user or session identifiers are stored — segments are coarse categories
  • An alert requires 75 valid samples in each 24-hour window and degradation across two consecutive windows, so one bad hour can never open one
  • There is no outbound alert channel in the dashboard — no email recipients, webhook, Slack, or GitHub fields — and Acknowledge is the only action an alert offers