Tracking-stopped alerts
Get one email the moment Muro stops receiving events from your site, so a broken deploy or a removed script doesn't go unnoticed for days.
A tracking-stopped alert is a single email Muro sends when your site stops sending events at a time it normally would. It's the one insight that doesn't wait for the daily digest. Turn it on if a silent outage would cost you, for example during a launch or after frequent deploys.
Alerts are off by default.
Turn on alerts
The owner setting is account-wide: it covers every project you own.
Open notifications
Go to Settings → Notifications.
Switch it on
Turn on Email me if tracking stops: "One email, right away, when Muro stops receiving events from one of your sites. Everything else stays in the daily digest. Also posts to Slack if it's connected."
Members choose per project.
Pick the project
Select the shared project in the project switcher.
Switch it on
Go to Settings → Notifications and, under This project's notifications, turn on Email me if tracking stops.
If the owner has connected Slack for the project and turned alerts on, the alert also posts to that Slack channel.
When an alert is sent
The alert comes from the Tracking stopped insight. Muro checks every hour whether events stopped arriving at a time your site normally gets them. Busy sites can trigger after a few hours of silence, quieter sites need a longer gap, up to about 3 days. See Tracking stopped for the details.
- Only when it's sure. Muro emails only after two hourly checks in a row agree, so a single slow hour never sends an alert.
- One email per outage. While the outage lasts, you won't get more emails about it.
- It closes itself. When events come back, the insight resolves on its own. No "all clear" email is sent.
- A daily ceiling. Muro sends at most a few alerts per project per day, even if tracking flaps on and off.
Alerts need a project that is at least a week old and gets about 7 events a day. Before that, Muro can't tell a real outage from a quiet day.
A paused project, or a project whose new events are paused (lapsed trial, failed payment or a reached pageview limit), never sends a tracking-stopped alert. Muro knows why events aren't being stored, so it doesn't report an outage.
What the email says
The subject is "Tracking may have stopped on project name", from alerts-noreply@muroanalytics.com. It goes to the email address on your account. The email shows the insight's headline, such as "Muro hasn't received any events for 6 hours", and a checklist:
- Check that the Muro script is still in your site's
<head>. - If your site sets a Content-Security-Policy, allow
api.muroanalytics.comandcdn.muroanalytics.com.
A View the insight button opens the card on your Insights board. To work through the cause, see No events are arriving and Fix Content-Security-Policy errors.
Turn alerts off
Switch off Email me if tracking stops in Settings → Notifications, or use the unsubscribe link at the bottom of any alert email.
Verify it works
You can't trigger a test alert, but you can check the setup:
- In Settings → Notifications, confirm Email me if tracking stops is on.
- Open Insights. If the board says "Muro starts watching for tracking outages after your site's first week" or mentions "about 7 events a day", outage checks haven't started for this project yet.
- Add
alerts-noreply@muroanalytics.comanddigest-noreply@muroanalytics.comto your contacts so Muro's emails don't land in spam.