Skip to content
WebsiteLogin

Device anomaly detection

Device Anomaly screens sources with unusually high shares of outdated operating systems or browsers. It supports clicks, conversions and impressions and uses the event’s device information. A single old device is not the same as a source-level anomaly.

Open Device Anomaly in Filters and select the event type. Configure the OS and browser checks that apply to your traffic:

  • Set Rejection Threshold Percentage: allowed share before the anomaly check rejects traffic.
  • Minimum Total: sample count required before comparing the share.
  • Lookback Time: the measurement window.
  • Check on Sub ID Level: narrow evaluation to a Sub ID.
  • Min OS Version and Min Browser Version: version cutoffs used to identify outdated devices.

Select Done, then save the page. Review the sample minimums as well as the percentage; low-volume sources need enough observations before a percentage is meaningful.

A campaign intentionally serving older devices can have a high outdated-version share without being automated. Set version cutoffs for the devices your campaign supports and assess rejections in Monitoring mode before blocking. Do not treat a version mismatch alone as proof of fraud.

See Emulator & Bots for automated-traffic screening and Data Validation for conversion app-version checks.