SaaSMaestro emails you when something needs attention, so you don’t have to check every day. Owners and admins control both what counts as a problem and which emails go out.
Alert thresholds
Under Settings → your workspace → Alert thresholds:
| Setting | Default | Effect |
|---|---|---|
| Visitors drop (%) | 20% | How far visitors must fall before an issue is raised. |
| Search clicks drop (%) | 20% | The same for search clicks. |
| Conversions drop (%) | 25% | The same for conversions. |
| Flag data as stale after (hours) | 48 | How long without a sync before data is marked stale (6 to 720 hours). |
Tracking failures are always critical, whatever the thresholds.
Notification emails
Under Settings → your workspace → Notifications. All are on by default. Times are UTC.
| Who gets it | When | |
|---|---|---|
| Critical issue alerts | Owners and admins | Daily at 07:30, when there are new critical issues. Each issue is emailed at most once a week, and issues already marked done or dismissed are skipped. |
| Connection problems | Owners and admins | Daily at 07:30, when a Google connection breaks or data goes stale. |
| Downtime alerts | Owners and admins | As soon as a website is confirmed down (once per outage per week), a key page starts failing or a heartbeat is missed. |
| Monthly uptime report | Owners and admins | On the 1st of each month, when Uptime monitoring is on: each website’s uptime and outages over the month before. |
| Weekly digest | Everyone in the workspace | Mondays at 08:00: the workspace summary for the last 7 days, with open issues. |
| Assigned tasks | Anyone with assigned actions | Mondays at 08:15: your open tasks, overdue and soonest due first. |
These switches are the workspace defaults. Anyone can turn their own emails on or off under Notifications → Your emails, and each email has an Unsubscribe link that turns it off for you alone.
Website health warnings, such as an expiring certificate or domain or changed nameservers, are sent as critical issue alerts as soon as a check finds them. The checks themselves are switched on under Data connections → Website health. See Website health monitoring.
Hiding what you don’t use
If a workspace doesn’t track conversions or use Search Console, switch them off under Workspace basics → What to show. Their figures, alerts and reports are hidden, but data keeps being collected so you can switch them back on at any time.
Slack, Teams, Discord and webhooks
Owners and admins can send alerts to chat as well as email, under Notifications → Chat and webhooks. Paste the channel’s incoming webhook address, choose what it should get (critical issues, connection problems, a website going down, a website coming back up), then click “Send test”.
- Slack: create a Slack app with Incoming Webhooks turned on, and copy the address for the channel.
- Microsoft Teams: in the channel, add the “Post to a channel when a webhook request is received” workflow and copy its address.
- Discord: Channel settings → Integrations → Webhooks → New webhook.
- Webhook (JSON): any HTTPS address. Each request is JSON with the event and its alerts, signed in the X-SaaSMaestro-Signature header (sha256= then the HMAC-SHA256 of the body with the secret shown when you add it).
Chat channels follow their own choices, so you can, for example, turn downtime emails off and still get downtime in Slack. Messages are written in the language of the workspace’s owner.