Additional configurations in Zia Anomaly detector
Dear all,
We have recently made a few enhancements and UI related changes to the Anomaly detector feature. In this post we will discuss what you can achieve with the help of these additional configurations.
Using related metric to draw comparison between metric
In addition to finding an anomaly of a single metric like deal closure, leads created etc., you can compare this metric with a related metric to get a ratio of the two and make more meaningful insight. For example, you can view the ratio between number of deals closed : number of contacts created.
Here, we have calculated the rate of deal closure as a single metric that shows 3 anomalous data points.
Here, we have calculated the rate of deal closure as a single metric that shows 3 anomalous data points.
With the related metric, we get the ratio between number of deals closed and number of contacts created. The ratio shows only two data points as anomalous, the other point is not considered an anomaly because the number of deals closed is proportional to number of contacts created.
Indicate if a surge or dip should be identified as positive or negative
You can set if an increase in value is considered as positive or negative anomaly. For example, an increase in the number of deals that were closed in a positive anomaly, but an increase in the number of support cases is a negative anomaly.
Grouping the data points under a category
You can group the results under a particular category like leads by their source or deals by their stage. Grouping can be done based on: time, currency, date, or any pick-list field. Below is grouping of leads by their source on a weekly basis.
Kindly refer to our
help doc to learn more about use cases and the configuration details. Please share your feedback and suggestions by commenting here.
Regards,
Anumita Gupta