Technical Capabilities (FraudSensor)
FraudSensor's detection tags can be broken into two main types: JavaScript-supported detection tags and (non-JavaScript) pixel tags. However, there are several practical differences when using FraudSensor with JavaScript tags versus pixel tags.
Max detection session time
The maximum time it takes for FraudSensor’s detection tags to finish collecting signals per impression.
- JavaScript tags
- FraudSensor grants JavaScript tags a maximum of two minutes to fully collect signals for each impression. However, most JavaScript tags will finish collecting signals in far less time. Also note that JavaScript tags load asynchronously, so collecting time should not impact overall site performance.
- Pixel tags
- Pixel tags finish collecting signals as soon as the tag is loaded.
UTM codes
How FraudSensor collects data for UTM codes.
- JavaScript tags
- JavaScript tags automatically collect UTM data if it is included in the URL of the impression’s referring domain.
- Pixel tags
- UTM data must be passed as part of the pixel tag's parameters.
Payload size
The size of each detection tag’s payload.
- JavaScript tags
- Initial: ~2 KB (the detection tag)
main.js: ~33 KB (the JavaScript function) - Pixel tags
- No payload
Signal strength
The quality and number of signals that each tag collects.
- JavaScript tags
- JavaScript tags are stronger and collect a wider number of signals.
- Pixel tags
- Pixel tags are weaker and collect fewer signals.
Environments
The environments supported by each tag type.
- JavaScript tags
- JavaScript tags are supported for most ad types in desktop, mobile web, and mobile app environments. However, native ads in mobile app environments and non-VAST 4.0 video ads are not supported.
- Pixel tags
- Pixel tags are supported for all ad types in desktop, mobile web, mobile app, and CTV environments.