Alerts
Configure notifications for the changes and conditions that matter to your team.
Updated 9 August 2026Turn unusual movement into an actionable notification
Alerts monitor a selected measure for a defined change and email the people who need to respond. They are most useful for conditions that matter enough to investigate but are easy to miss between scheduled report reviews.
Use Alerts for meaningful exceptions rather than routine fluctuation. A focused set of well-owned notifications helps the team react sooner without teaching people to ignore a noisy inbox.
Build the alert condition
Select the measure the alert should monitor.
Defines the direction or kind of movement that should qualify.
Sets the size of the change required before the condition is met.
Interprets the amount in the unit appropriate to the chosen condition.
Adds another condition that must also be satisfied.
Adds an alternative condition group that can trigger the same Alert.
Choose thresholds that reflect business impact and normal volatility. A small percentage movement may be meaningful for high-volume revenue, while the same threshold can create noise for a low-volume event.
Name and deliver the Alert
Add a clear name
Describe the situation rather than the implementation, for example a material fall in completed sales or an unexpected increase in error activity.
Explain the response
Use the description to state what the Alert means, who owns it and the first report or setup area to check.
Add a communications channel
Choose add new comms channel and enter the contact email. Add only recipients who have a reason to act on the notification.
Save the rule
Save stores the Alert while keeping the editor open. Save & Exit stores it and returns to the Alerts list. Cancel leaves without saving the current changes.
Design Alerts people will trust
- Start with the few conditions that represent material commercial or measurement risk.
- Use AND logic when several signals together indicate a real issue.
- Use OR logic when different symptoms should produce the same response.
- Allow for day-of-week, campaign and seasonal patterns before setting a threshold.
- Review Alert ownership when responsibilities change.
- If an Alert fires repeatedly without action, improve the threshold or retire it.
It identifies that configured conditions were met; it does not diagnose the cause. Check the relevant report, date range, filters and tracking health before acting.