For the complete documentation index, see llms.txt. This page is also available as Markdown.

Traffic Metrics Bot Detection

Bot Detection helps managers identify potential bot accounts among fans acquired through traffic links. This improves visibility into real audience activity and helps prevent traffic metrics from being inflated by automated or fake accounts.

Overview

Bot Detection operates at the level of individual traffic links and displays results throughout the Link Overview interface.

Supported traffic types:

  • Tracking Links

  • Trial Links

Bot Detection is not available for Direct Traffic. For Direct Traffic, bot-related metrics always display N/A.

Enabling Bot Detection

You can start a bot scan from the Link Overview using the Bot Detection button in the top-right corner of the page.

Once Bot Detection is enabled for a link:

  • Newly acquired fans are scanned automatically.

  • A notification appears after the scan is completed.

If scan results are not reviewed within 10 days, Bot Detection is automatically disabled for that link. You can re-enable it at any time from Link Overview.

Where Bot Detection Appears

Next to the Fan Purchase Frequency block, the Bots block displays aggregated detection results for the selected link:

  • Detected — Total number of fans identified as potential bots.

  • Bot Rate — Percentage of detected bots among all fans acquired through the link.

Fans flagged by the system display a red bot icon next to their username.

  • Bot icon visible — Fan was flagged as a potential bot

  • No icon — Fan passed bot detection

This allows suspicious accounts to be identified directly within the fan list.

Detection Methodology

To maintain the effectiveness of Bot Detection and reduce circumvention attempts, the specific detection signals, rules, and underlying analysis methods are not publicly disclosed.

Usage and Responsibility

Bot Detection results are generated automatically and are provided for informational purposes only. Although the system aims for high accuracy, false positives and false negatives may occur.

Any decisions made based on Bot Detection data — including, but not limited to, fan moderation actions, refunds, payout adjustments, or communication with traffic providers — remain the sole responsibility of the organization using the information.

Access Requirements

Bot Detection follows the same permissions structure as Traffic Metrics.

The View Traffic Metrics permission is required to view bot-related data.

The Edit Traffic Metrics permission is required to start and manage bot scans.

Last updated

Was this helpful?