Event checks (preview)

Open Event checks in the dashboard sidebar, pick a site, and add a missing-event rule or a repeated-business-ID rule. For example, investigate when no signup events arrive despite 100 pageviews in 24 hours, or when purchase events repeat the same order_id string property.

A missing-event rule can measure how busy the site is by an event, pageviews by default, or by engaged visits: visits where someone scrolled, tapped, typed or stayed 15 seconds. Engaged visits are the better choice when automated browsers load your pages. They fire pageviews but never engage, so a wave of them can neither set off a false alarm nor hide a real one. Over the API or MCP, send "reference": "engaged_visits" and leave out referenceEvent.

Checks run every five minutes using their own rolling windows, exclude classified bots, and retain evidence and incident history. Missing-event checks wait for a complete window after creation or resume. Low activity and missing IDs are shown as inconclusive or incomplete. These checks inspect received events; they do not test browser flows or reconcile billing.

When a check finds a problem, every verified member of the workspace gets one email. They get one more when the check passes again. A problem that continues does not send a new email every five minutes. Every alert email has a link to turn that kind of email off, and each person can switch alerts on or off for themselves under Account → Email alerts.

Workspace owners and admins can create up to ten checks per site. Read results with GET /v1/event-checks or MCP get_event_checks. Use Copy for your agent to hand the evidence to your coding agent. A passing rule does not prove a customer flow works or that a code fix succeeded.