Notification catalog
Every message Metric Vault can send, by channel, with what triggers it, who receives it, and the exact sender and subject line.
Last updated 2026-08-06
Summary#
This is the complete inventory of messages the platform can send, across five channels. Each row gives the trigger, the channel, the recipient and, for email, the exact sender address and subject line, so a support agent can identify a message a customer has quoted. If a message is not on this page, Metric Vault did not send it.
Overview#
Every notification you can receive answers "what will I receive and how do I switch it off?" from your point of view. This page answers "what can the platform emit, and what does it look like?" — including messages addressed to people who are not account holders, such as a blog subscriber or someone being invited to a workspace.
Five channels exist.
| Channel | Where it arrives | Configured |
|---|---|---|
| In-app feed | The bell in the dashboard top bar, and Track & Report → Notifications & Alerts Hub | Account → Preferences |
| The address on the alert, the schedule, or your account | Per item, or Account → Preferences | |
| Slack | An incoming webhook you paste in | On the monitored URL |
| Generic webhook | A POST of JSON to an endpoint you own | On the monitored URL |
| Identity email | Your inbox, sent by the sign-in system | Not configurable |
Two facts shape everything below.
- Nothing is sent on a timer for its own sake. Every message follows a real event: a page changed, a keyword moved, a schedule ran, a score fell, someone invited you.
- Email delivery is best effort. If email is not configured on the environment, the message is skipped silently rather than failing the job that produced it. The in-app feed item is still created.
Emails#
| # | Message | Trigger | Sent from | Subject |
|---|---|---|---|---|
| 1 | Competitor change alert | Competitor Monitor finds changes on a monitored URL at or above that URL's severity gate, and an email address is set on it | Watchtower <alerts@metricvaultai.com> | Watchtower: <N> changes on <label> |
| 2 | Rank drop alert | A tracked keyword drops past its threshold, or leaves the top 10 entirely, and the alert carries an email address | Watchtower <alerts@metricvaultai.com> | Watchtower: 1 change on Rank drop: "<keyword>" |
| 3 | Test alert | You use the test-alert control on a monitored URL to check your channels | Watchtower <alerts@metricvaultai.com> | Watchtower: 1 change on Test alert from Metric Vault Watchtower |
| 4 | Scheduled report ready | A schedule you created runs and has a recipient address | Metric Vault <reports@metricvaultai.com> | Scheduled report ready: <target> |
| 5 | AI Visibility change | A tracked brand's visibility score moves by at least the alert threshold, in either direction, carried by at least 3 prompt-and-engine results | Metric Vault Alerts <alerts@metricvaultai.com> | AI Visibility drop on <brand> - down <N> points or AI Visibility rise on <brand> - up <N> points |
| 6 | Workspace invitation | A workspace owner invites someone | Metric Vault <invites@metricvaultai.com> | <inviter> invited you to a Metric Vault workspace |
| 7 | Blog subscriber welcome | Someone subscribes to a blog you publish with Blog Studio | Metric Vault Blog <blog@metricvaultai.com> | You're subscribed to <site name> |
| 8 | Blog newsletter | You send a published post to your subscribers | Metric Vault Blog <blog@metricvaultai.com> | The subject you set on that post's newsletter |
What each email contains#
| Contents | |
|---|---|
| Competitor change alert | The label and the URL, how many changes were found, the severity gate that was applied, a list of up to twelve changes, and a link to open Competitor Monitor. Beyond twelve it says …and <N> more |
| Rank drop alert | The same layout, describing the keyword, the previous position and the current one |
| Test alert | A single synthetic change, so you can confirm the address, the Slack channel or the webhook works before relying on it |
| 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 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. Footer: Sent by Metric Vault. To stop receiving these, remove the alert in the dashboard. |
| Workspace invitation | Who invited you, what a member can see and do, and an Accept invite → link. Footer: If you weren't expecting this, you can safely ignore the email. |
| Blog subscriber welcome | Confirmation of the subscription, from the blog they subscribed to |
| Blog newsletter | The post, plus that recipient's own unsubscribe link |
Rules that apply to email#
| Rule | Detail |
|---|---|
| Language | All of these are sent in English, whatever interface language you have selected |
| AI Visibility change frequency | At most once every 24 hours per alert, however often the score is measured. Scheduled scans are weekly, so in practice one per scan |
| Newsletter recipients | Only confirmed subscribers. A recipient picker can narrow that list, never widen it |
| Newsletter size cap | 2,000 recipients per send |
| Newsletter privacy | One message per recipient, each with its own address and unsubscribe link, so subscribers never see each other |
| Newsletter repeat | A post that has already been sent is refused unless you deliberately force a resend |
| Severity gate | Applies to alert emails 1 to 3. Changes below the gate produce no email at all |
In-app notifications#
Four sources feed one list, newest first, capped at the 50 most recent items.
| Notification | Trigger | Window | Title format |
|---|---|---|---|
| Competitor change | Competitor Monitor detected a change you have not dismissed | Last 14 days | <competitor domain>: <change type> |
| Rank drop | A tracked keyword fell past its threshold, or out of the top 30 | Last 14 days | "<keyword>" dropped on <domain> |
| Scheduled report ready | A schedule produced a saved report, or failed | Last 14 days | Scheduled report ready: <workflow> on <target> or Scheduled report failed: <target> |
| Public link viewed | A share link you created has been viewed at least once | Any | "<report title>" viewed <N> times |
Severity is shown on every row as High, Medium or Low. A failed scheduled report and a keyword that left the rankings are High; a public link view and a successful run are Low.
Mark all read is recorded on the server for every type. Competitor changes are flagged one by one; rank drops, scheduled runs and share views are marked read up to the moment you press it, using a per-account read timestamp. Because that lives on the server rather than in the browser, marking read on one device also clears the badge on another, and an alert that arrives afterwards comes back unread.
Slack and webhook messages#
Both are configured on the individual item, and neither is affected by the account preference switches.
| Message | Channel | Payload |
|---|---|---|
| Competitor change to Slack | Slack incoming webhook | A message headed Watchtower alert with the label, the linked URL, the list of changes at • <severity> — <description> (first eight, then …and <N> more), and a footer giving the severity gate, the check interval and a link to Competitor Monitor |
| Competitor change to a webhook | POST of JSON to your endpoint | Identified by "source": "Metric Vault Watchtower" and "event": "changes_detected", carrying the monitored item, every change with its severity and old and new values, the top change, the change count, the detection timestamp and a dashboard link |
| Rank drop to Slack | Slack incoming webhook | The same shape, with the label Rank drop: "<keyword>" |
| Rank drop to a webhook | POST of JSON to your endpoint | The same shape, describing the keyword rather than a monitored page |
A rank drop is described in one of two exact forms, and that wording is what appears in the Slack message, the webhook payload and the email:
"<keyword>" dropped from #<previous> to #<current> on Google for <domain>"<keyword>" no longer ranks on page 1 for <domain> (was #<previous>)
Each channel is attempted independently. Slack failing does not stop the email, and neither stops the in-app item being recorded.
Important: The Rank Alerts screen collects a keyword, a domain and a drop threshold. It does not ask for a Slack channel, a webhook or an email address, so an alert created there reaches you in the in-app feed only. Rank drops reach the other three channels only when those details are stored on the alert itself.
Identity emails#
These come from the sign-in system rather than the product, so the sender and subject are set there and are not customizable from the app.
| Message | Trigger | Notes |
|---|---|---|
| Confirmation link | You create an account with an email address and password | Until you click it, the account cannot sign in. The sign-up screen says Almost there — we sent a confirmation link to <email>. Click it to activate your account, then sign in. |
| Password reset link | You use Forgot password? on the sign-in page | The page confirms with Password reset email sent. The link opens the Set New Password form |
Both links are time-limited by the sign-in system. Request a new one if a link has expired. See I cannot sign in.
Operator-only#
| Message | Notes |
|---|---|
| Diagnostic test message | An operator can send a test message to verify email delivery. It is never addressed to a customer and never carries customer data |
What Metric Vault never sends#
| Not sent | What to use instead |
|---|---|
| A weekly digest. The Weekly Digest preference is stored but nothing sends one today | A scheduled report. See Scheduled reports |
| Sign-in, password-change or new-device security alerts | Review your account yourself. See Account security |
| Credit or quota warning emails | The credits pill in the top bar and the usage figure on the Account screen. See Tracking your usage |
| Payment, invoice or card-expiry emails from this system | Billing messages come from Stripe. See Invoices and receipts |
| Marketing or product-update email from the notification system | Not part of this system |
| Browser push notifications | The bell panel is the in-app channel |
| SMS, WhatsApp or phone alerts | Not offered |
| Notifications to a teammate when you run a tool or share a report | Nothing is broadcast to a workspace |
Troubleshooting#
| Symptom | Likely cause | Fix |
|---|---|---|
| An in-app item appeared but no email arrived | No email address is set on that monitored URL or alert, or the change was below the gate for email | Add the address on the item itself; alerts do not fall back to your account address |
| No alerts at all from a monitored URL | The severity gate is set higher than the changes being found | Lower the gate on that URL and use the test alert to confirm the channel |
| The Weekly Digest switch is on but nothing arrives | No digest is sent today | Use a scheduled report |
| A scheduled report email never came | The schedule has no recipient address, or Email Notifications is off | See My scheduled report never arrived |
| The AI Visibility email stopped | It is limited to once every 24 hours per alert, needs both Email Notifications and SEO Score Alerts on, and ignores any move under 10 points or carried by fewer than 3 prompt-and-engine results | Check both switches in Account → Preferences, then check the trend chart: a quiet mailbox usually means the score has not really moved |
| Emails arrive in English although the app is in Spanish | Working as designed | See Supported languages |
See also
Was this article helpful?
Thanks — feedback noted for the docs team.