Data Validation
What it detects
Invalid or unexpected parameter values in tracking requests — unknown advertiser IDs, unauthorized publisher IDs, missing sub IDs, or malformed offer references — indicate either misconfigured tracking links or fraudulent traffic injection. The Data Validation filter checks core request parameters against your defined allowed and blocked values before any attribution occurs.
How it works
When a click or conversion arrives, Integr8 evaluates the configured parameters against your rules:
- Allowlist (whitelist): Only requests with values in the allowed list are accepted. All other values are rejected.
- Blocklist (blacklist): Requests with values in the blocked list are rejected. All other values pass.
- Empty value handling: You can configure whether empty values for each parameter are accepted or rejected.
Rules are evaluated per parameter independently. You can configure any combination of parameters.
Configuration
Navigate to Fraud Prevention > Traffic Quality > Data Validation to configure.
Supported parameters
| Parameter | Description |
|---|---|
| Advertiser | The advertiser ID passed in the tracking request |
| Publisher | The publisher ID associated with the click |
| Offer | The offer ID the click was generated for |
| Sub ID | The sub source identifier passed by the publisher |
For each parameter, configure:
| Setting | Description |
|---|---|
| Allowed values | Comma-separated list of valid values. Only these values pass. Leave empty to allow all. |
| Blocked values | Comma-separated list of rejected values. These values are always rejected. |
| Reject empty value | When enabled, requests with a missing or empty value for this parameter are rejected. |
What happens when triggered
When a request fails validation:
- The request is rejected with
fraud_reason: data_validation. - No attribution is recorded.
- The event is logged in Reports > Click Reports or Conversion and Events Report depending on the event type.
Use allowlisting (whitelist mode) when you want to restrict tracking to a known, finite set of sources. Use blocklisting when you want to reject specific known-bad values while allowing everything else.
Related filters
- Sub-ID Validity Check — enforces format and uniqueness rules on sub ID values
- ISP Filter — blocks traffic based on network-level ISP identity