Skip to content

Sub-ID Validity Check

What it detects

Fraudulent publishers sometimes pass malformed, missing, or excessively unique sub IDs to obscure traffic origin or game attribution. The Sub-ID Validity Check enforces format rules and uniqueness limits, blocking clicks and conversions that fail to meet your sub ID standards.

How it works

Integr8 validates the sub_id parameter on each incoming request against the rules you configure:

  • Format rules: You can require numeric-only sub IDs and enforce minimum/maximum length constraints.
  • Uniqueness limit: You can cap the number of unique sub IDs allowed per publisher. Sub IDs beyond the limit are grouped under a unified placeholder value, and the original sub ID is stored in invalid_sub_id.

The filter applies to both clicks and conversions.

Configuration

Navigate to Fraud Prevention > Traffic Quality > Sub-ID Validity Check to configure.

ParameterDefaultDescription
accept_only_numbersfalseWhen enabled, only numeric sub IDs are accepted
min_length0Minimum character length for a valid sub ID
max_length0 (unlimited)Maximum character length for a valid sub ID
max_unique_sub_ids0 (disabled)Maximum number of unique sub IDs per publisher. Set to 0 to disable
unified_sub_id_name(empty)Replacement sub ID value used when max unique sub IDs is exceeded

Setting max_unique_sub_ids to a non-zero value enables the uniqueness cap. Sub IDs beyond the limit are renamed to unified_sub_id_name in reports. The original value is preserved in invalid_sub_id for auditing.

What happens when triggered

When a sub ID fails format validation:

  • The click or conversion is rejected with fraud_reason: invalid_sub_id.

When the unique sub ID cap is exceeded:

  • The click is still attributed, but the sub ID is replaced with the unified placeholder value.
  • The original sub ID is stored in invalid_sub_id for review in reports.