FraudSensor uses several types of detection tags to collect traffic signals and analyze data. Each tag type offers different strengths and weaknesses, including the amount and quality of signals collected, but certain tags are designed to provide coverage in specific scenarios.
To get the most out of FraudSensor’s detection tags, it’s important to choose a tag type that supports the environment where the tag is deployed and the format of the associated advertisements. To help you choose the right detection tag for any scenario, we’ve compiled a list of HUMAN-supported environments and the best tag flavors for various types of ads in each environment.
Banner ads: JavaScript tag
Rich media: JavaScript tag
Video (VPAID-enabled): VPAID tag
Video (VAST only): Pixel tag
Native ads: JavaScript tagBanner ads: JavaScript tag
Rich media: JavaScript tag
Video (VPAID-enabled): VPAID tag
Video (VAST only): Pixel tag
Native ads: JavaScript tagBanner ads: JavaScript tag
Rich media: JavaScript tag
Video: Pixel tag
Native ads: Pixel tagBanner ads: Pixel tag
Video: Pixel tag
JavaScript tags
JavaScript tags are FraudSensor’s main method of collecting traffic signals. In order to function properly, these tags must be embedded in a JavaScript-enabled environment.
Tag components
- URL
- The URL of the server that delivers the tag.
- loader
- A script that loads FraudSensor's main payload.
- Parameter list
- The parameters built into the body of the tag, separated by an ampersand (&) character. These parameters should be populated by your ad server.
- async
- A Boolean value that dictates whether the tag should load asynchronously from other page content. If set to “true”, loading the FraudSensor script will not slow down overall pageload times.
Signal strength
JavaScript tags are the most flexible tags and collect the most and strongest signals for HUMAN’s detection engine. Thanks to the strength of these signals, we recommend using JavaScript tags whenever possible.
Supported environments
You can deploy JavaScript tags in desktop and mobile browsers for most non-video ads. You can also deploy JavaScript tags for certain mobile app ads, like banners and rich media, but native ads in mobile app environments are not rendered in a browser or web view and therefore do not support JavaScript tags.
VPAID tags
VPAID tags are generally used for video ads. These tags provide a VPAID wrapper for VAST 2.0 ads.
Tag components
- URL
- The URL of the server that delivers the tag.
- ci
- Your HUMAN customer ID.
- originVast
- Any third-party tags to be included.
- Parameter list
- The parameters built into the body of the tag, separated by an ampersand (&) character. These parameters should be populated by your ad server.
Signal strength
Since VPAID tags collect signals on par with JavaScript tags, we recommend using VPAID tags for any campaign that runs on VAST and supports VPAID ads.
Supported environments
You can deploy VPAID tags for VPAID-enabled VAST ads across all platforms. However, certain VAST-based video ads do not support VPAID and require a 1x1 tag instead.
Pixel tag
Pixel tags (also known as 1x1 tags) offer a “slimmed-down” version of FraudSensor. Pixel tags collect basic information using a server-side GET request and the parameters passed through the tag. Although these tags offer limited functionality, they are useful in situations where JavaScript and VPAID tags are not supported.
Tag components
- URL
- The URL of the server that delivers the tag.
- analytics.gif
- The actual pixel image (in GIF format).
- Parameter list
- The parameters built into the body of the tag, separated by an ampersand (&) character. These parameters should be populated by your ad server.
Signal strength
Since pixel tags collect fewer signals than JavaScript and VPAID tags, we recommend only using these tags when no other tag type is supported.
Supported environments
You can deploy pixel tags in any environment, including desktop browsers, mobile browsers, mobile apps, and CTV devices.