Back to overview
Lesson 4 of 6

Qualification Rules and Automated Filtering

7 min read

From Scoring to Action: Qualification Rules

A quality score tells you which affiliates send good traffic. Qualification rules determine what happens to traffic that does not meet your standards. Without rules, scoring is just reporting. With rules, your platform automatically holds, adjusts, or rejects payouts based on predefined quality criteria -- removing the need for manual review of every conversion.

Qualification rules sit between the conversion event and the commission payout. When a referred user completes an action (registration, deposit, trade, purchase), the system evaluates whether that action meets the qualification criteria before marking it as commissionable. This is the single most effective mechanism for controlling traffic quality at scale.

Types of Qualification Rules

Rule TypeWhat It ChecksExample Configuration
Minimum depositFirst deposit meets a dollar thresholdFTD >= $20 to qualify as CPA conversion
Activity requirementUser performs meaningful post-registration actionMust place at least 1 trade or 1 bet within 7 days of deposit
Time delaySufficient time between click and conversionClick-to-registration >= 30 seconds (filters bot auto-fills)
Geographic matchUser location matches allowed marketsIP country must match a permitted jurisdiction list
Device uniquenessConversion comes from a unique deviceDevice fingerprint not seen in another conversion within 30 days
KYC completionUser passes identity verificationKYC documents submitted and approved within 14 days of registration
Negative revenue filterUser does not generate negative valueNet revenue >= $0 at day-30 review for RevShare qualification
Duplicate detectionUser is not already in the systemEmail, phone, or payment method not linked to an existing account

Layer qualification rules from broad to specific. Start with technical filters (bot detection, geo-match, duplicate check), then apply behavioral requirements (minimum deposit, activity within timeframe), then financial thresholds (net revenue positive at review date). Each layer reduces the volume that needs manual review at the next stage.

Configuring Rules Without Losing Good Partners

The risk of aggressive qualification rules is rejecting legitimate conversions. A new player who deposits $15 instead of $20 is not fraudulent -- they are cautious. Setting the minimum deposit threshold too high filters out real users along with low-quality ones. The goal is to find thresholds that catch 80% of quality problems while rejecting less than 5% of legitimate conversions.

  • Analyze your conversion data before setting thresholds: what is the 25th percentile deposit amount for users who remain active at day 30?
  • Run qualification rules in "shadow mode" for 30 days before enforcing -- measure what would have been rejected and review those cases manually
  • Set different thresholds by partner tier: premium partners with proven track records can have lighter qualification requirements
  • Build in an appeal process: when a conversion is disqualified, the affiliate should be able to see the reason and request manual review
  • Review and adjust thresholds quarterly based on evolving traffic patterns and conversion data

Automated Enforcement Workflows

Manual qualification review does not scale. A program processing 5,000 conversions per month cannot have a human evaluating each one. Automated enforcement applies rules instantly at the platform level, with manual review reserved for edge cases and appeals. The workflow follows a clear path: conversion event fires, qualification rules evaluate, and the conversion is either approved, held for review, or rejected.

Qualification OutcomeSystem ActionPartner Visibility
ApprovedCommission calculated and added to next payout cycleConversion shows as "qualified" in partner dashboard
Held for reviewCommission pending, flagged for manual evaluationConversion shows as "pending review" with estimated review timeline
Rejected (rule-based)No commission, conversion marked as disqualifiedConversion shows rejection reason -- partner can appeal within 14 days
Rejected (fraud)No commission, account flagged for fraud team reviewConversion removed from dashboard, partner notified of investigation

Never reject conversions silently. Partners who see conversions disappear without explanation will assume the program is cheating them and leave. Transparent rejection with clear reasons builds trust even when the partner disagrees with the outcome. The appeal process is not just fair -- it is a retention mechanism for affiliates.

Qualification Rules by Commission Model

CPA programs need front-loaded qualification rules because the commission is paid once at conversion. If a low-quality registration triggers a $150 CPA and the user never returns, that cost is unrecoverable. RevShare programs can afford lighter upfront qualification because the commission is tied to ongoing activity -- a user who generates no revenue generates no commission. Hybrid models need qualification at both the CPA trigger point and at RevShare review intervals.

  • CPA: Minimum deposit + activity requirement + KYC completion before payout triggers
  • RevShare: Lighter upfront rules, but apply negative carryover and minimum net revenue thresholds at monthly review
  • Hybrid: CPA qualification for the upfront payment + RevShare qualification for the ongoing share
  • Tiered CPA: Different qualification levels for different payout tiers -- higher CPA requires stricter qualification

Key Takeaways

  • Qualification rules are the mechanism that turns quality scoring into actual commission control
  • Layer rules from broad technical filters to specific behavioral and financial thresholds
  • Run new rules in shadow mode for 30 days before enforcement to avoid rejecting legitimate conversions
  • Never reject conversions silently -- transparent reasons and an appeal process retain good partners
  • Match qualification stringency to commission model: CPA needs strict upfront rules, RevShare can rely on ongoing revenue thresholds