A monitor watches your catalogs and channels and reacts when a condition holds. An alert is what you receive when it triggers. To set one up, start with Monitoring your catalogs and channels.
Monitors and Alerts Explained
A monitor is a rule that watches your catalogs and channels. When it triggers it can raise an alert, send an email, hold a publish or send a webhook, and it clears on its own when the problem goes away.
Updated November 6, 2026
Monitor#
"Alert me when a catalog's product count drops more than 25% between imports" is a monitor. It says what to check (each catalog import), the condition (product count change below -25%), and what to do (raise a Warning alert, perhaps send an email).
What a monitor does is a list of actions, and it needs at least one: Raise an alert, Send an email (up to 10), Hold the publish and Send a webhook (up to 10). So a monitor can just email you, just hold the publish, or just tell another system.
Monitors belong to your organization and live on the Monitoring page. One monitor watches catalogs or channels, never both: all of them, a subset, or a single one.
A monitor triggers when its condition holds and clears on its own when a later check passes. Each catalog or channel is judged separately, so a monitor watching all catalogs can be triggered on one and quiet on the rest. A monitor's card shows where it's triggered right now, whether or not it raises alerts.
A monitor that holds a channel's publish keeps the previous feed live instead of publishing suspicious data. See Hold a channel's publish when something looks wrong.
You pause a monitor with a switch, which takes effect at once with no publish step, and you archive it rather than delete it. Edits stay in a draft until you press Publish, and every published version is kept in its history.
A monitor with no condition#
The condition is optional, except on a schedule. With none, a monitor matches every check it makes. One that watches imports or channel runs triggers on the first check and stays triggered: its email goes out once, and any alert it raises never clears, so each catalog or channel it watches shows as needing attention until you pause it. One that reacts to events clears when none of those events is open.
Alert#
An alert can reach you in two ways:
- In the app: with Raise an alert, an entry on the dashboard's attention list and on the Activity tab of the catalog or channel, raised as a Warning or an Error depending on how you set up the monitor.
- By email: with Send an email, one email per incident, to team members or verified outside addresses. A monitor can send several different emails, each to its own people with its own wording. See Email alerts and verified addresses.
An alert disappears when the monitor clears. If it's still there, the monitor's last check still matched, so a monitor on imports clears at the next import after you fix the problem.
A monitor holding a publish always shows an Error alert, even without Raise an alert. Use that alert's Publish button to publish anyway.
A monitor also raises an Error alert for each webhook it can't deliver. That alert clears with the next successful delivery to that webhook, or when you remove the webhook and publish.
Other terms#
- Publish held: the status of a channel's run when a monitor held its publish. The previous feed stays live, and the hold clears with the monitor.
- Webhook: a message a monitor sends to another system, such as a CRM: an HTTPS POST with a JSON body to an address you choose. Each Send a webhook action picks its own events, and the monitor's Activity tab shows the deliveries of its newest 50 events. See Send monitor events to a webhook.
- Matched, Triggered, Cleared: the three events a webhook can send. Matched is every check where the condition holds; Triggered and Cleared are the moments the monitor starts and stops triggering.
- Verified address: an email address outside your team that has clicked its verification link.