Device ID Check
What it detects
Bots, emulators, and SDK spoofing tools frequently submit malformed, missing, or fake device IDs — either because they cannot generate a real device fingerprint or because they use programmatically generated values that don’t follow standard formats. The Device ID Check validates that every device ID conforms to the standard UUID format and rejects non-conforming requests.
How it works
Integr8 validates the device ID parameter on each request against the UUID format:
36 characters: 8-4-4-4-12Example: 68753A44-4D6F-1226-9C60-0050E4C00067Any ID that deviates from this structure — wrong length, missing hyphens, incorrect character grouping, or empty value — triggers a rejection.
Configuration
Navigate to Fraud Prevention > Device Fraud > Device ID Check to configure.
| Parameter | Default | Options | Description |
|---|---|---|---|
enabled | false | true, false | Enable UUID format validation for device IDs |
block_empty | true | true, false | Reject requests with missing or empty device ID |
What happens when triggered
When a device ID fails UUID format validation:
- The request is rejected with
fraud_reason: invalid_device_id. - No attribution is recorded.
- The event is visible in Reports > Click Reports with the fraud reason tag.
This filter applies to mobile app install campaigns that pass device IDs (IDFA on iOS, GAID on Android). It is not applicable to web campaigns where device IDs are not collected.
Related filters
- Device Anomaly Detection — blocks traffic from outdated device OS/browser versions
- Emulator and Bots — detects non-human traffic signals beyond device ID
- Wrong Install Time — detects SDK spoofing via invalid install timestamps