Documentation

Email notifications

Alert emails, recovery notifications and the weekly report — what is sent when.

What email notifications do for you

Email is the most direct way to hear about alerts outside the interface. As soon as a scheduled scan triggers a relevant problem state, turbometrics can send a message, depending on your settings.

This is not about newsletters or marketing, but about productive notices on:

  • critical problems
  • warnings
  • failed scheduled scans
  • an alert being resolved (recovery)

turbometrics also sends automatic emails when your subscription changes – for example on an upgrade, a downgrade or a scheduled plan change.

What the requirements are

Three things need to be in place before email notifications will reach you:

  1. your plan allows the feature
  2. sending is enabled on the target
  3. there is a usable recipient in your profile

If one of these requirements is missing, the product points out the gap in the appropriate place.

Controlling critical and warning separately

In the product, critical alerts and warnings can be handled separately:

  • critical is suited to real problems that need action
  • warning makes sense when you want to see anomalies early, without having to escalate every case straight away

Not every plan unlocks warning emails. So it can happen that you can enable critical emails but not warning emails.

Subject scheme of the alert emails

Alert emails follow a consistent subject scheme, so that they are immediately recognisable in any inbox:

Type Subject example
Critical alert [Critical] dipalino.com – turbometrics
Warning [Warning] dipalino.com – turbometrics
Recovery [Resolved] dipalino.com – turbometrics
Test email [Test] dipalino.com – turbometrics

Note on the trigger threshold in the email

Every alert email states after how many consecutive bad scan results it was triggered – matching the setting of the scan target in question:

  • "This notification was triggered after the first bad scan result."
  • "This notification was triggered after 3 consecutive bad scan results were detected."

That way you can tell directly from the email whether this is a one-off outlier or a recurring problem. The setting itself can be adjusted per scan target under Alert after X consecutive bad scans.

Recovery emails

When a problem state resolves – that is, when an alert is marked as resolved – turbometrics automatically sends a confirmation email. The subject starts with [Resolved], and the design is green instead of red or yellow.

The same configuration applies as for the original alert: no separate toggle, no additional setting. If you receive critical alerts by email, you get the recovery email as well.

How the alert email is structured

Alert emails concentrate on the most important information:

  • the type and severity of the alert
  • the affected URL or domain
  • the region
  • the point in time
  • the trigger threshold (after how many consecutive bad scans)
  • direct actions such as Open scan, Open alerts or Open scheduled scan

That lets you jump straight from the email into the matching context.

Weekly report

turbometrics sends a weekly email report summarising the last 7 days:

Scan monitoring:

  • Score per domain with the delta to the previous week (↑/↓ arrows, green/red)
  • Domains sorted by score change

Live data (if enabled):

  • LCP p75 with the delta to the previous week
  • Number of page views during the week
  • CWV status (passed / failed)

Alerts:

  • Number of alerts triggered and resolved in the last 7 days

The weekly report is enabled by default. You can disable it under Profile > Notifications. From the same settings page you can also send a test email.

Recovery behaviour in detail

When a problem resolves (an alert gets a resolved_at timestamp), turbometrics automatically sends a recovery email. Recovery detection runs every 5 minutes via the CheckRumAlerts command. For scan-based alerts, recovery happens as soon as the next scan is successful. For RUM alerts, recovery happens when the p75 value falls back below the threshold for the configured number of consecutive checks. The same email configuration applies – a separate toggle is not needed.

Subscription notifications by email

Besides alert emails, turbometrics automatically sends notifications when your subscription changes. These emails follow the turbometrics: … scheme in the subject.

Upgrade

On an upgrade to a higher plan you receive a confirmation with the new limits of your plan (number of scans, intervals, history period).

Downgrade

On a downgrade to a lower plan you receive:

  • an overview of the new limits
  • a note about the 7-day grace period: your existing scan data is kept for another 7 days before older entries are automatically cleaned up to match the new history period

If the downgrade means that existing scan intervals are no longer compatible with the new plan, they are adjusted automatically to the next permitted interval. In that case you receive a separate email with an overview of the affected targets and their new intervals.

Scheduled downgrade

If you schedule a plan change via Stripe for a future date, you get a notification in advance containing:

  • the scheduled plan and the activation date
  • the limits that will apply from then on
  • a note that everything runs unchanged until then

What you additionally see in the product

Besides the email itself there are two helpful places:

  • Alerts for the current problem states
  • Alert history for your own history of notifications that were sent

That lets you trace what is currently open and what has already been sent.

Typical pitfalls

  • Email enabled on the target, but no suitable recipient address in the profile
  • Warning enabled although the current plan does not unlock warning notifications
  • Email enabled on too many low-value targets, so the signals stop meaning anything

Good practice

Start with critical alerts for a few important targets. Once that works cleanly, you can add warning emails for selected pages where early notice really helps you.

Further reading