Every notification you can receive
A complete list of the alerts Metric Vault can send you, with the event that triggers each one, where it arrives, and which preference controls it.
Last updated 2026-08-06
Summary#
Metric Vault sends notifications through four channels: the in-app feed behind the bell icon, email, a Slack webhook, and a generic JSON webhook. This is the complete list. If a notification is not on this page, Metric Vault does not send it.
Overview#
Two things determine whether a notification reaches you.
Where it is configured. In-app feed items and the emails Metric Vault sends about your own account are governed by the four switches in Account → Preferences. Slack messages, JSON webhooks and alert emails addressed to a recipient you chose are configured on the individual monitored URL or rank alert, and the account preferences do not affect them.
What actually happened. Every notification below is driven by a real event: a page changed, a keyword moved, a schedule ran, a visibility score fell, someone invited you. Nothing is sent on a timer for its own sake.
Notification preferences explains the four preference switches. This page is the inventory.
In-app notifications#
These appear behind the bell icon in the top bar and on the full-page Track & Report → Notifications & Alerts Hub. Both read the same feed.
| Notification | Trigger | Channel | Controlling preference |
|---|---|---|---|
| Competitor change | Competitor Monitor detects a change on one of your monitored URLs. Changes from the last 14 days that you have not dismissed are included | In-app feed | Competitor Alerts |
| Rank drop | A tracked keyword's latest position is worse than the previous check by at least that alert's drop threshold, or it was in the top 10 and no longer ranks. Alerts checked in the last 14 days are included | In-app feed | SEO Score Alerts |
| Scheduled report ready | A scheduled report has a saved result, or the run failed. A run still waiting for its report is not shown. Runs from the last 14 days are included | In-app feed | None — always shown |
| Public link viewed | A public share link you created has been viewed at least once | In-app feed | None — always shown |
What each in-app item looks like#
| Notification | Title | Body |
|---|---|---|
| Competitor change | <competitor domain>: <change type> | The description of the change |
| Rank drop | "<keyword>" dropped on <domain> | Was #12. Now #19. or Was #4. Now not ranking in top 30. |
| Scheduled report ready | Scheduled report ready: <workflow> on <target> | The run status |
| Scheduled report run, failed | Scheduled report failed: <target> | The failure detail |
| Public link viewed | "<report title>" viewed 3 times | Public link /share/<slug> has been viewed. |
Clicking a competitor change opens the monitored URL in a new tab. Clicking a public-link item opens the share page.
Severity#
Every feed item carries a severity, shown as a colored label on the row.
| Severity | Color | Used for |
|---|---|---|
High | Red | A failed scheduled report; a keyword that fell out of the rankings entirely or dropped by at least twice its threshold; a competitor change the monitor graded as high |
Medium | Amber | A rank drop past the threshold but less than twice it; a competitor change graded as medium |
Low | Muted | A scheduled report that is ready; a public link view; a competitor change graded as low |
Feed behavior#
| Behavior | Detail |
|---|---|
| Unread badge | A red count on the bell icon. Above 99 it reads 99+ |
| Unread marker | A red dot on each row that arrived since you last cleared the panel |
| Mark all read | Clears the dots and the badge, and records competitor changes as read on your account |
| Item cap | The feed returns the 50 most recent items across all sources |
| Time window | Competitor changes, rank drops and scheduled runs from the last 14 days |
| Empty state | All caught up — no new alerts. |
| Signed out | Sign in to see notifications. |
| Load failure | Could not load notifications. |
| Footer | Alerts from Watchtower, Rank Alerts, and Scheduled Reports |
The full-page hub adds filter pills: All, Unread, Competitor, Rank drops and Reports, plus Mark all read and Refresh. See Notifications and alerts hub.
Email notifications#
| Notification | Trigger | Sent from | Subject | Recipient | Controlling preference |
|---|---|---|---|---|---|
| Scheduled report ready | A schedule you created runs and has a recipient address set on it | Metric Vault <reports@metricvaultai.com> | Scheduled report ready: <target> | The recipient address on that schedule | Email Notifications |
| AI Visibility change | A tracked brand's AI visibility score moves, up or down, by at least the alert's threshold, where that move carries at least 3 prompt-and-engine results. On a paid plan the alert is created for you when you first measure the brand. Sent at most once every 24 hours per alert | Metric Vault Alerts <alerts@metricvaultai.com> | AI Visibility drop on <brand> - down <N> points or AI Visibility rise on <brand> - up <N> points | Your account address | Email Notifications and SEO Score Alerts — both must be on |
| Competitor change alert | Competitor Monitor detects changes at or above the severity gate set on that monitored URL | Watchtower <alerts@metricvaultai.com> | Watchtower: <N> changes on <label> | The address set on that monitored URL | None — configured on the monitored URL |
| Rank drop alert | A tracked keyword drops past its threshold or falls out of the top 10, and that alert has an email recipient stored | Watchtower <alerts@metricvaultai.com> | Watchtower: <N> change on Rank drop: "<keyword>" | The address stored on that rank alert | None — configured on the alert |
| Workspace invitation | A workspace owner invites you to their team | Metric Vault <invites@metricvaultai.com> | <inviter address> invited you to a Metric Vault workspace | The invited address | None — invitations are always sent |
Note: The AI Visibility change email is the only one that needs two preferences on at once. If you have switched SEO Score Alerts off to quiet the in-app feed, that email stops as well.
What the emails contain#
| Contents | |
|---|---|
| Scheduled report ready | Which workflow ran, on which target, and a link to open your reports library |
| AI Visibility change | The brand, the previous and current visibility percentages, the size and direction of the move, how many of the scan's prompt-and-engine results changed, the threshold that was crossed, and a link to the dashboard |
| Competitor change alert | The monitored URL and its label, the number of changes, the severity gate applied, and up to twelve individual changes with their severity |
| Rank drop alert | The same layout, describing the drop, for example "running shoes" dropped from #6 to #14 on Google for example.com |
| Workspace invitation | Who invited you, what a member gets access to, and an Accept invite link |
Emails are sent in English regardless of the interface language you have chosen.
Slack and webhook notifications#
These are configured per monitored URL or per rank alert, not on the Account screen. The account preferences do not switch them off; clear the field on the item itself.
| Notification | Trigger | Channel | Where it is configured | Controlling preference |
|---|---|---|---|---|
| Competitor change to Slack | Changes at or above the monitored URL's severity gate | Slack incoming webhook | The Slack webhook field on the monitored URL | None |
| Competitor change to a webhook | Same trigger | A JSON POST to your endpoint | The webhook URL field on the monitored URL | None |
| Rank drop to Slack | A tracked keyword drops past its threshold or leaves the top 10 | Slack incoming webhook | The Slack webhook stored on the rank alert | None |
| Rank drop to a webhook | Same trigger | A JSON POST to your endpoint | The webhook stored on the rank alert | None |
The Slack message is headed Watchtower alert and includes the label, the URL, the list of changes, the severity gate and the check interval.
The JSON webhook payload identifies itself with "source": "Metric Vault Watchtower" and "event": "changes_detected", and carries the monitored item, the full list of changes with their severity and old and new values, the top change, the change count, the detection timestamp and a dashboard link.
Important: The Rank Alerts screen collects a keyword, a domain and a drop threshold. It does not collect Slack, webhook or email channels, so a rank alert created there reaches you in the in-app feed. Rank drops only produce Slack, webhook or email delivery when those channels are stored on the alert itself.
What Metric Vault does not send#
Being explicit here prevents a long wait for something that is not coming.
| Not sent | What happens instead |
|---|---|
| A weekly digest email. The Weekly Digest preference is stored but no digest is sent today | Use scheduled reports for a recurring summary. See Scheduled reports |
| Marketing or product-update emails from the notification system | Not part of this system |
| Sign-in, password change or new-device alerts | Not sent. See Account security |
| Credit or quota warning emails | The usage figure on the Account screen and the credits pill in the top bar are the signals. See Tracking your usage |
| Payment and invoice notifications | Billing is handled by Stripe, outside this notification system. Invoices are available in the billing portal. See Invoices and receipts |
| Browser push notifications or a mobile app | The bell panel and email are the channels |
| SMS | Not offered |
See also
Was this article helpful?
Thanks — feedback noted for the docs team.