Alerts & Anomaly Detection
Admin
Active Alerts
Critical
Resolved (30d)
Paused Rules
Lazy evaluation (no cron): rules re-check on page reads and event ingest, at most once per hour. Last pass:

Alert History

90d · G9
Fired Rule Observed Severity State
Payloads are aggregate-only (churn context = count + MRR-at-risk sum) — never a named account or user list.

Alert Rules

CRUD: /api/admin/alerts/* (editor+)
Rule Metric Cond. Threshold Sev. State
Custom rules: / · deactivated rules are preserved, never deleted (G9-5).
The LTV/CAC rule (G9-4) stays honestly paused — "CAC unavailable — alert paused" — until ad-spend data lands (M6). A ratio is never fabricated. Trial-CVR alerting (G9-3) is descoped: no trial dates exist in the live client data.

Delivery

In-app v1

Alerts are delivered in-app only in v1 — this panel and the history feed above. Email and webhook delivery are deferred (decision D-4): an email channel can be stored on a rule today, but nothing is sent until delivery ships. No fake "connected" states.

Computed Alerts

Analyzing…