# Analytics alerts and notifications

> Set alerts for traffic thresholds, anomalies, goals, missing data, downtime, SSL expiry, Web Vitals and usage, delivered by email, Slack, Teams or webhooks.

## Rule types

| Rule | Fires when |
|---|---|
| **Threshold** | A metric (visitors, visits, pageviews, bounce rate or conversion rate) goes above or below a value over a period, e.g. visitors < 10 per hour |
| **Anomaly** | A metric moves unusually far from its automatic baseline, with sensitivity low, medium or high |
| **Goal** | A goal reaches N completions within the rule's window |
| **No data** | No hits for N hours: the script may be missing |
| **Uptime** | An [uptime check](/docs/features/uptime) goes down or recovers |
| **SSL / domain** | A certificate or domain expires within N days |
| **Vitals** | A Web Vitals metric (LCP, INP, CLS, FCP, TTFB) regresses |
| **Usage** | Workspace usage reaches 80% or 100% of the plan (workspace-level) |

Site rules live in **Site settings → Alerts**. All rules are listed in the
workspace's **Alerts** page.

## Channels

Alerts are delivered through **notification channels**, set up once per
workspace and reused by any rule:

| Channel | Plan |
|---|---|
| Email | All |
| Slack, Microsoft Teams, Discord | Pro and up |
| Webhook ([signed](/docs/api/webhooks)) | Pro and up |
| Browser push | Pro and up |
| PagerDuty, Opsgenie | Business |

Each channel has a **Send test** button.

## Noise control

- **Mute** a rule for a period (for example during a planned migration).
- **History**: every time a rule fired and recovered. **Acknowledge** a
  triggered alert to show the team someone's on it.