Anomaly settings

Adjust the period and thresholds for anomalies

Wijnand Meijer avatar
Written by Wijnand Meijer
Updated over a week ago

As mentioned in the introduction of custom attributes, the second section of the custom attribute window is for anomaly settings:

We currently monitor daily for anomalies in the following metrics:

  • Clicks

  • Cost

  • Conversions

This list will be expanded with metrics like CPA, ROAS, Conversion value and Impression share.

By default, an anomaly is triggered based on the following settings:

  • Comparing the last 7 days

  • With the 7 days before (Previous period)

  • When there's at least a 50% change (increase or decrease) in the selected metric

Once we find such an anomaly, it will show in the anomaly column of the All accounts overview:

When editing this part of the custom attributes, you're free to choose from the following options:

Most recent period to use as baseline:

  • Last 7 days

  • Last 30 days

  • Last 90 days

Period of equal length to compare it with:

  • Previous period (e.g. the 7 days before the last 7 days), which can best be used in non-seasonal accounts or accounts with less than 1 year of history.

  • Same period last year (e.g. the same 7 days a year ago), which can best be used in seasonal accounts with at least 1 year of history.

Change thresholds to trigger an anomaly:
Both an increase or decrease in the selected metric of at least:

  • 20%

  • 30%

  • 40%

  • 50%

  • 60%

  • 70%

  • 80%

  • 90%

  • 100%

Once you've made sure the anomaly settings are to your liking, it's time to move to the last section: enable/disable checks.

Did this answer your question?