# Threshold reporting in Omni
**URL:** https://community.omni.co/t/threshold-reporting-in-omni/218
**Category:** Visualizations
**Tags:** dashboards
**Created:** [January 24, 2025, 2:36am UTC](https://community.omni.co/t/threshold-reporting-in-omni/218 "2025-01-24T02:36:04Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@kylee](https://community.omni.co/u/kylee)
#### Post date: [January 24, 2025, 2:36am UTC](https://community.omni.co/t/threshold-reporting-in-omni/218/1 "2025-01-24T02:36:04Z")
**Threshold alerting** allows data teams and executives to monitor key metrics and act proactively when thresholds are crossed.
In this example we will be setting up an alert for when the number of users at our platform goes above 20,000. In a workbook tab, output the total number of users and filter for the number of users we want to be notified of, which should return no results right now. Now, we go to the dashboard \> file menu \> deliveries & alerts \> alert. When setting up the alert in the dashboard we can send out the tab where we are checking results or the entire dashboard in the **send** dropdown, and then indicate the tab with the filter applied in **results to check** and set the condition to **results have changed**. Now we will be notified when the users count passes the threshold defined in the filter.
A similar process can be followed for many other types of data changes we would want to be alerted on. For example, if we wanted to know when the users count passed 2,000 users for a particular state we could pull state into the query and filter for user count over 2000 would show us any states past the threshold.
---
### Author:  [@colin](https://community.omni.co/u/colin)
#### Post date: [April 29, 2025, 12:37am UTC](https://community.omni.co/t/threshold-reporting-in-omni/218/2 "2025-04-29T00:37:25Z")
Here’s an example with some screenshots. We’re looking for change in daily sales of more than 50%.
Here is our baseline view, simple sales (we may want to add outlier bands, etc):
We can write a few calcs in a second tab to calculate the trigger (here growth \> 50%):
And set up a simple query trigger (not filtered for last 2 days and the calculation):
Finally on the dashboard, we just set the trigger to our trigger query (in production, we’d hide all but the base query, but including here for thoroughness):
