Skip to content

Emulator and Bots

What it detects

Section titled “What it detects”

Emulators, headless browsers, and click farm automation tools generate traffic that mimics real user sessions but lacks the behavioral and hardware characteristics of a genuine device. This filter applies multi-signal analysis to identify and block non-human traffic before it reaches attribution.

How it works

Section titled “How it works”

Integr8 evaluates multiple signals on each incoming request to determine whether the traffic originates from a real device:

  • User agent anomalies: Identifies spoofed or implausible user agent strings common to automation frameworks (Selenium, Puppeteer, headless Chrome, etc.)
  • IP frequency analysis: Flags IP addresses with unnaturally high request rates or access patterns inconsistent with human behavior
  • Device behavior profiling: Detects device characteristics that contradict what the user agent claims — for example, an Android user agent with no gyroscope or touch events

Traffic that matches emulator or bot signatures is rejected immediately.

Configuration

Section titled “Configuration”

Navigate to Offers > Fraud Detection Groups > select a filter group > Emulator & Bots.

Parameter Default Options Description
reject_empty_browser_language false true, false Reject requests that do not include a browser language header

What happens when triggered

Section titled “What happens when triggered”

When a request is identified as emulator or bot traffic:

  • Block mode: The request is rejected with fraud_reason: emulator_bot.
  • Flag mode: The request is recorded with the fraud tag for audit without blocking.

Review flagged or blocked traffic in Reports > Click Reports filtered by fraud_reason: emulator_bot.

Enable Flag mode first to assess the volume of bot traffic on your campaigns. If the flagged volume is consistently high and concentrated on specific publishers, those publishers are likely operating fraudulent traffic sources.

Section titled “Related filters”