Alerts and monitoring

Alerts help you detect analytics problems before they become silent data gaps.

Alert types#

PureStats can monitor:

• Tracking stopped.
• Traffic unusually increased or decreased.
• Goal conversions dropped.
• Human visit conversion rate dropped.
• Drop-off between selected funnel steps increased.
• Scheduled report or alert delivery appears delayed.

Alert rules#

Each alert rule has a site, condition, threshold, notification target and cooldown period. Cooldowns prevent repeated notifications for the same ongoing issue.

Alert events#

When a rule triggers, PureStats creates an alert event. Events show when the condition started, when it recovered and whether a notification was sent.

Notifications#

Alert notifications are sent by email to the configured recipients.

In Profile → Email preferences, enable or disable each alert type for your account's email address across all websites. Re-enabling removes your own unsubscribe suppression; delivery blocks caused by bounces or administrator decisions still apply. Reports and account emails have separate settings.

Choose immediate delivery or a daily summary for each type. Summaries group the previous day's events by email address and alert type and are queued from 08:00 Europe/Berlin. Each immediate mail and summary includes a link to unsubscribe from exactly its type; opening the link only shows a confirmation page.

Durations are displayed as 45m, 2h 15m or 3d 4h.

Weekday comparison#

Traffic spike and drop rules can compare with the same local time in the preceding four weeks. Select Same weekday · four weeks in the rule. This mode requires four weeks of tracking history, an evaluation window of at most 24 hours, sufficient baseline traffic and no known tracking gaps in the compared windows. Without those prerequisites it does not trigger a change alert. Existing rules retain their previous-window comparison until you change them.

Conversion-rate and funnel warnings#

These rules start disabled. Enable them in Website settings → Alerts after choosing a threshold and, for funnel warnings, a funnel and a step with a following step.

Conversion-rate warnings compare the percentage of distinct human visits with a goal conversion within 60 minutes of the session start. Duplicate conversions count once. Select all eligible goals or one goal; goals must predate every compared window. A 50% threshold means a relative rate decrease, such as 10% to 5%.

Funnel warnings use the same matching rules as the funnel report and wait for the configured conversion window to finish. They compare the share of visits reaching the selected step that fail to reach the next step. A threshold of 20 percentage points means, for example, a change from 10% to 30% drop-off. Visitors can therefore see different numbers in a report that includes newer, unfinished cohorts.

Every current and baseline window needs at least 100 qualified human visits by default (configurable down to 20), sufficient site and goal/funnel history, and no known tracking gaps. Conversion-rate baselines also need at least five converting visits. Same-weekday mode requires all four previous weekly windows to qualify. Missing samples or gaps defer evaluation and preserve existing open events; they do not establish recovery. These are configurable monitoring thresholds, not statistical significance tests. Notifications use the existing cooldown, delivery preferences and per-type unsubscribe links.

Recommended starting rules#

For production sites, start with:

• No tracking hits for 24 hours.
• Traffic down more than 80% compared with the same period.
• Rollup job delayed.

Adjust thresholds after you understand normal traffic variance.