Critical-leak alerts

Not every leak needs a phone buzz. Critical alerts are reserved for findings large enough to interrupt your day.

The default threshold

$500 single-finding. Any detected leak estimated above $500 in 30-day impact triggers a critical alert across all configured channels.

What usually triggers

• Large single failed-payment renewal ($500+ MRR customer).
• Broken tracking pixel estimated to lose $500+ per day.
• Sudden refund-rate spike on a high-volume SKU.
• Ad-account-wide zero-ROAS day (usually a disconnected pixel).

Tuning

Raise the threshold if you're getting paged too often (large accounts sometimes set it to $2,000). Lower it for tighter ops (some set it to $200). Settings → Notifications → Critical threshold.

Paging

Scale customers can wire critical alerts into PagerDuty, Opsgenie, or webhook-to-anywhere. Settings → Notifications → Paging.