Getting started with custom monitors

The comparison operators in the alert rule builder can be set to compare changes in a value based on a relative or absolute basis. 

When using the relative basis comparison, it will measure the percent change from the original value. Choosing the absolute comparison operators will measure the change based on the numeric increase or decrease from the original value. 

For example, say you have the following relative condition: 

Alert when open rate relatively increases by more than 10% in the last 3 days compared to the previous 3 days.

If the open rate during the previous 3-day period was 20%, for this condition to be satisfied, the open rate would need to increase by a relative 10% (i.e., a multiplier of 1.1x) to 22%.

Meanwhile, if you set the condition to absolute, it would look like the example setup below. 

Alert when open rate is absolutely increased by more than 10% in the last 3 days compared to the previous 3 days

If the open rate during the previous 3 day period was 20%, for this condition to be satisfied the open rate would need to increase by an absolute 10% (i.e., an increase of 10%) to 30%.

With a Single metric monitor you can proactively monitor the number of Active on Site events captured in Klaviyo, and receive alerts if there is a drop in website traffic.

Below is an example of a custom monitor you can set up for the Active on Site event. Once you set the Monitor type and Metric name, you can use the Metric preview to see the daily, weekly or monthly numbers of Active on Site events to use as a benchmark for the values in the alert rules. 

For the alert rule, create the following 2 conditions, as shown in the example below: 

• Alert when Sum of Total number of Active on Site is less than 9300 in the last 7 days
  

Or

• Alert when Average of Total number of Active on Site is relatively decreased by more than 15 in the last 30 days compared to Average of previous 30 days. 

This first condition in this monitor calculates the number of Active on Site events during the last 7 days and compares it to a threshold of 9300. If the number drops below this threshold, an alert triggers. 

The second condition in this alert calculates the average number of Active on Site events in the last 30 days and compares it to the average for the prior 30 days. If the difference is more than 15%, an alert triggers. 

With a Single flow monitor, you can create a monitor that proactively monitors the unsubscribe rate for key flows on your account. This is a great way to easily identify issues with unsubscribe rates in your flows so you can resolve them before your deliverability is impacted. 

You can select any flow on your account, along with the channel you want to monitor (i.e., email or SMS unsubscribe rates). Once you set the Monitor type and Metric name, you can use the Metric preview to see daily, weekly or monthly unsubscribe rates to use as a benchmark for values in the alert rules.

For the alert rule, create the following 2 conditions, as shown in the example below: 

• Alert when Unsubscribe rate for [flow] is greater than 0.5 in the last 7 days

OR 

• Alert when Unsubscribe rate for [flow] is absolutely increased by more than 0.2 in the last 1 day compared to the previous 1 day

This first condition in this monitor checks the flow’s unsubscribe rate in the last 7 days and compares it to a threshold of 0.5%. If the unsubscribe rate exceeds 0.5% an alert triggers.

The second condition in this alert checks the unsubscribe rate for the flow in the last day compared to the prior day. If the unsubscribe rate increases by more than 0.2% from the previous day, an alert triggers. 

With a Single flow monitor, you can create a monitor that proactively monitors the total number of conversions for key flows on your account. This is a way to spot drops in conversions in your flows, so you can resolve them before there is a significant impact on your revenue.

You can select any flow on your account, along with the channel you want to monitor (i.e., email or SMS conversions). Once you set the Monitor type and Metric name, you can use the Metric preview to see daily, weekly or monthly numbers of conversions to use as a benchmark for values in alert rules. In the section below, Placed order is used as the conversion metric. 

For the alert rule, create the following 2 conditions, as shown in the example below: 

• Alert when Sum of Total conversions for [flow] is less than 1000 in the last 7 days

OR 

• Alert when Average of Total conversions for [flow] is absolutely decreased by 20 in the last 3 days compared to Average of the previous 3 days.

This first condition in this monitor checks the number of conversions from the flow in the last 7 days and compares it to a threshold of 1000. If the number of conversion drops below this threshold, an alert triggers. 

The second condition in this alert checks the average number of conversions from the flow in the last 3 days compared to the prior 3 days. If the number of conversions between these periods drops by 20, an alert triggers. 

With a Single segment monitor, you can create a monitor that proactively monitors the total number of added profiles in key segments. If you have any important segments on your account, this is a way to check that the segments are growing at expected rates so you can quickly investigate drops in growth rates. 

Below is an example of a custom monitor you can set up for a segment. Once you set the Monitor type and Metric name, you can use the Metric preview to see daily, weekly or monthly numbers of added segment members to use as a benchmark for values in the alert rules. 

For the alert rule, create something similar to the following 2 conditions: 

• Alert when Average of Added members for [segment] is less than 1400 in the last 30 days
  

OR

• Alert when Sum of Added members for [segment] is relatively decreased by 15% in the last 7 days compared to Sum of the previous 7 days. 

The first condition checks the average number of added members in the last 30 days, and if it drops by a threshold of 1400, an alert triggers. 

The second condition checks the number of added members during the last 7 days in comparison to prior 7 days, and if there is a decrease of 15% between these periods, an alert triggers. 

With a Single metric monitor, you can proactively monitor the health of custom or 3rd-party integrations using counts of key inbound metrics. 

Below is an example of a monitor you can set up for an event called Filled out form that is being synced from a 3rd-party integration.

Once you set the Monitor type and Metric name, you can use the Metric preview to see the daily, weekly or monthly numbers of your events to use as a benchmark for the values in the alert rules. 

For this example, the alert rule has the following condition as shown below: 

• Alert when Average of Total number of Filled out form is relatively decreased by more than 50 in the last 3 days compared to Average of previous 7 days. 

This condition calculates the average number of Filled out form events during the last 3 days and compares it to the average from the previous 7 days. If there is more than a 50% drop from the average of the previous 7 days, a notification will send and may indicate a problem with the health of your integration.