General Configuration

The Anti-Cheat System is pre-installed as a core component of the Preads Platform. This guide details the unified configuration suite available at Admin → Security → Anti-Cheat, allowing you to fine-tune the detection sensitivity and automated response protocols of your network.

⚙️ Global Ecosystem Settings

Located in the General tab, these settings control the high-level behavior of the fraud detection engine.

  • Enable Fraud Detection: The master switch for the entire system. When disabled, all traffic is bypass-allowed with a risk score of 0.
  • Auto-Block Critical Risks: If enabled, any transaction with a risk score exceeding the Critical Threshold (default: 60) will be immediately blocked.
  • Auto-Flag High Risks: If enabled, transactions exceeding the High Threshold (default: 40) will be automatically queued for manual administrative review.
  • Dry Run Mode: (If enabled) The system will process detections and log risk scores but will not block or flag any live traffic.

📊 Risk Threshold Configuration

The decision engine uses four distinct levels to categorize traffic quality based on the weighted risk score (0-100).

Setting Key Default Description
risk_threshold_low 20 Score below this are considered safe for immediate processing.
risk_threshold_medium 40 Score between Low and Medium are monitored for pattern analysis.
risk_threshold_high 60 Score between Medium and High are flagged for manual audit.
risk_threshold_critical 80 Score above this are treated as definitive fraud.

🧠 Behavioral Analysis Rules

Fine-tune how the system detects non-human usage patterns in the Behavior tab.

  • Fast Completion Threshold: Set the minimum time (in seconds) an offer can be completed. If a user converts faster than this, they are flagged for fast_completion.
  • Rapid Conversion Burst: The maximum number of conversions allowed within a 60-second window before triggering a rapid_conversion flag.
  • Sequence Validation: Enables logic to ensure users follow a linear path (Click → View → Conversion).

🌐 IP Intelligence & Caching

Optimize your API usage and detection accuracy in the IP Intelligence tab.

  • Cache TTL (Time-to-Live): Set how long IP intelligence results are stored in the database (default: 86,400 seconds / 24 hours). Higher values reduce API costs but may miss dynamic IP changes.
  • Proxy/VPN Sensitivity: Toggle specific detection for various infrastructure types (Proxies, VPNs, TOR, Datacenters).
  • Provider Chaining: Configure the priority order of integrated API providers (IPQualityScore, ProxyCheck, etc.). If the primary provider fails, the system automatically falls back to the secondary.

💻 Device Fingerprinting

Manage hardware-based detection rules in the Fingerprint tab.

  • Multi-Accounting Limit: Set the maximum number of unique user accounts allowed per physical device fingerprint.
  • Bot Resistance: Identify and flag "Headless" browser signatures and automated crawling scripts.

🔑 API & License Management

The API Keys tab is where you securely store and test the credentials for your integrated intelligence providers.

  • Individual Toggles: Enable or disable specific providers (e.g., enable IPQualityScore while keeping MaxMind disabled).
  • Connection Sandboxing: Each provider section includes a Test API button to verify connectivity and credential validity before saving.
  • License Management: Configure enterprise-level licenses for providers like MaxMind GeoIP2 or FingerprintJS.

Mastering IP Intelligence Providers →