Notification showing a website traffic spike alert

Alerts Guide: How to Configure Traffic Spike and Drop Alerts in statpx

You shouldn't have to remember to check your dashboard to find out something went wrong. The Alerts page in statpx lets you set thresholds for traffic spikes or drops and get notified by email or in-app the moment they're crossed — plus an opt-in anomaly detector that watches your daily numbers for unusual patterns without any thresholds at all.

What Alerts Monitor

Alerts in statpx are threshold rules built on three metrics: daily pageviews, hourly pageviews, and daily sessions. Each rule watches one metric and fires when it goes above or below a number you define. You can run up to 10 alert rules per site, so it's practical to set both a "too low" floor (catch outages and broken tracking) and a "too high" ceiling (catch viral spikes, bot floods, or a marketing push you want to know about immediately) on the same site.

Creating a Threshold Alert

To add a new alert, open the Alerts page for your site and fill in:

  1. Name — a label so you recognize the alert later, e.g. "Daily pageviews floor."
  2. Metric — daily pageviews, hourly pageviews, or daily sessions.
  3. Condition — above or below.
  4. Threshold — the number that triggers the alert.
  5. Channel — email, webhook, or both. A webhook lets you pipe alerts into Slack, Discord, or any endpoint that accepts an HTTPS POST; the URL must be a public HTTPS address.

Once saved, the alert runs continuously in the background — there's nothing else to configure, and you can edit or delete any rule at any time from the same page.

Turning On Anomaly Detection

Threshold alerts require you to know in advance what "too high" or "too low" looks like. For sites whose traffic isn't a flat, predictable number, statpx also offers anomaly detection — an opt-in setting that analyzes your daily traffic pattern and flags days that deviate significantly from what's normal for your site, without you having to pick a threshold yourself. It's off by default; turn it on from the anomaly alerts checkbox on your site's Settings page, alongside the rest of your site-level configuration.

Use both together. A hard threshold alert is great for a known "this must never happen" number (e.g. zero pageviews for an hour). Anomaly detection is better for catching gradual or unusual shifts that don't cross any single number you'd have thought to set as a threshold.

Where Alerts Show Up

When a threshold is crossed, statpx sends an email to your account address (plus any extra email you configured on the alert) and creates an in-app notification visible from the bell icon in your dashboard. If a webhook channel is configured, the same event is POSTed to your endpoint so it can land in whatever team chat tool you already use. Because alerts run against your live rollup data, they typically fire within the same hour the threshold is crossed.

When you're investigating why an alert fired, check annotations on the same date first — a deploy, campaign launch, or redesign you already logged is often the answer before you even open the traffic charts.

Never miss a traffic spike or drop again

statpx alerts you by email and in-app the moment your traffic crosses a threshold you set — or opt in to anomaly detection for automatic pattern monitoring.

Start for free →

The Bottom Line

Alerts turn analytics from something you have to remember to check into something that comes to you. Set a hard floor threshold to catch outages, a ceiling to catch spikes worth knowing about immediately, and turn on anomaly detection in Settings if your traffic pattern is too irregular for a fixed number to work well. Between the two, you'll hear about a problem within the hour instead of the next time you happen to open the dashboard.

Continue reading

Technical
How to Identify and Block Referrer Spam in Website Analytics
Metrics
How to Track and Reduce Shopping Cart Abandonment with Analytics
Privacy
Google Consent Mode v2 Explained: What It Means for Your Analytics
Analytics by statpx