Email Alerts and Verified Addresses

Any monitor can email you when it triggers, once per incident, and it can send several different emails to different people. Team members can be picked directly; any other address must click a verification link first.

Updated November 6, 2026

A monitor's alert shows in the app, on the dashboard and on the affected catalog or channel. Email is a separate action on the monitor, for what you want to hear about without logging in. A monitor can raise an alert and email, or only email.

Turn on email for a monitor#

  1. Open the monitor from the Monitoring page and find the Then section of its Rule tab.
  2. Click + Add action and pick Send an email.
  3. Fill in Send to. Team members and other addresses go in the same box:
    • Anyone in your organization can be picked directly, with no verification.
    • For any other address, type it under Add an email address. Renable sends it a verification email at once, and it appears in Send to.
  4. Publish the monitor.

Each Send an email row needs at least one recipient, or the monitor can't be published. To stop a monitor emailing, delete the row with the bin icon beside it.

Send more than one email#

A monitor can have up to 10 Send an email actions, each with its own Send to, Title and Body. Click + Add action and pick Send an email again. For example:

  • A short, plain note to the store owner: "Fewer products than usual are going to your ads today. We're on it."
  • A technical one to an agency inbox, with the observed numbers and a link straight to the catalog.

An address on two rows gets both emails. A row can send to at most 25 people. For more, use a shared address or a mailing list.

How verification works#

An address outside your team must confirm it wants these emails before any are sent.

  • The verification email has a confirmation link that's valid for 7 days. If it expires or gets lost, use Resend next to the pending address.
  • Until the link is clicked, the address shows in Send to as a dashed chip reading pending. You can publish the monitor with a pending address, but nothing reaches it yet.
  • Verification is per address, so a verified address receives alerts from every monitor it's added to.
  • Every alert email to an outside address ends with a Stop receiving these alerts link. It opens a page with one button, and pressing it removes the address from every monitor in your organization. You can add it again later, which sends a new verification email. Team members don't get this link. You manage them on the monitor.

What to expect#

  • You get one email per incident, when the monitor triggers, with no repeat on later checks while the problem persists. Very rarely, the same email arrives twice.
  • The email names the monitor and the affected catalog or channel, shows the observed numbers and links to the right page.
  • A monitor that keeps triggering and clearing sends each of its emails at most 10 times a day for the same catalog or channel. Later ones that day are skipped.
  • Your whole organization can send at most 200 a day, counted per recipient, so an email to 3 people counts as 3. An email that would go past the day's 200 isn't sent at all, to anyone. Both daily limits count days in UTC.
  • No email goes out when a monitor clears. If it raised an alert, the alert disappears from the app. A monitor with no condition never clears after imports or channel runs, so it emails once. If another system needs to hear about the clear, add a webhook that sends Cleared: see Send monitor events to a webhook.

The monitor's Activity tab lists each time it triggered, with every email and whether it was Sent, Failed or Skipped. An email is skipped when it has no verified recipient, when a daily limit was reached, or when the monitor was paused, archived or changed before the email went out.

Write your own title and body#

Under Send to, Customize the wording opens a Title and a Body. Both start with the standard wording, and both pick values from the same chips the condition uses: the monitor's name, the affected catalog or channel, why it triggered, a link back into the app.

  • If you leave them alone, they follow the standard wording, including any later improvements we make to it.
  • Reset to default, or clearing the field, goes back to the standard wording. An empty field never means "send nothing".
  • Your text replaces the message only. The observed numbers, the link to the affected catalog or channel and the footer are added below it.
  • Pick values from the list rather than typing them. A value that can't be filled in shows in the email as you typed it.
  • A title can be up to 200 characters and a body up to 2,000. The monitor's own Alert text, if you write one, can be up to 500.

Manage addresses#

Verified and pending addresses are shared across your organization's monitors, so you add an address once and use it anywhere. Removing one from a Send an email row stops that row's emails to it, and it stays available for other rows and monitors.

Tips#

  • A monitor that checks when an event is reported can forward every Warning and Error in your account to an inbox. The Anything needs attention suggestion on the Monitoring page sets this up.
  • When an alert should become a task in your CRM or ticketing tool, use Send a webhook instead of an email, or as well as one.