FraudSensor Parameters

FraudSensor’s detection tags collect various signals that HUMAN uses in our decisioning. Many of these signals come in the form of parameters, which are discrete data points collected at the time of each impression. Certain parameters require you to provide key/value pairs in the body of the detection tag when an ad is served; other parameters are detected automatically and require no action on your part.

Below you’ll find information about the specific parameters that are collected by FraudSensor’s detection tags, along with a description of each parameter.

The Tag parameters section includes a list of parameters that you must provide in the detection tag.
The Detected parameters section includes a list of parameters that are automatically detected by HUMAN.

Data from all parameters, regardless of whether they’re tag parameters or detected parameters, is available through the HUMAN Dashboard and in reports.

Tag parameters

Tag parameters are parameters that you must manually provide to HUMAN—we don’t detect these signals automatically. You can provide us with tag parameters by building your detection tag to include the relevant key/value pairs in the body of the detection tag itself.

We’ve broken down this list into required, recommended, and optional tags. Certain parameters are only required if you’re using FraudSensor in conjunction with MediaGuard; we use these MediaGuard-specific parameters to close the loop between solutions. Recommended and optional parameters aren't strictly necessary; however, some recommended parameters help us make more accurate decisions about your traffic, and optional parameters provide you with more detailed data to view in reports.

NOTE

Unless indicated otherwise, all parameters are supported across all environments.

caution

For any tag parameter where there is no value to report, like in the case of a null or unknown value, pass an empty string through the body of the tag (in other words, leave the value blank). For example, if the au parameter has an unknown value, but the subsequent ar parameter has a known value, that snippet of the tag body should be formatted as ...&au=&ar=25….

Required parameters

App ID (ap)

Required // Mobile App and CTV traffic only

The app bundle in which the ad was served (as reported by the device where the impression occurred).

For in-app mobile and CTV traffic, the App ID value should match the App/Bundle ID (as outlined by IAB Tech Lab standards). This parameter is case-sensitive; do not alter the value by changing it to all lowercase or uppercase.

Examples:

iOS: 324715238
Android: com.example.Example
Roku CTV: 41468
Samsung CTV: G15115002089
Vizio CTV: vizio.tubitv

Detection Tag ID (dt)

Required // All traffic types

The numeric identifier of the detection tag that detected the impression.

When HUMAN generates a new detection tag, this value is inserted into the body of the tag by default; however, HUMAN cannot automatically detect this information if the required key/value pair is absent from the tag, so make sure not to delete the parameter by mistake.

Domain Intended (di)

Required // Desktop traffic only

The domain where the ad was intended to be delivered. This value should include the full top-level domain, but should exclude the protocol and path.

Examples:

reddit.com
bbc.co.uk
m.wikipedia.org

Media Type (md)

Required // All traffic types

The media type of the ad inventory, corresponding to a number between 1 and 4. For example, if the inventory was a video, this parameter should have a value of 2.

Possible values:

1 = Banner
2 = Video
3 = Audio
4 = Native

OpenRTB 2.5 Reference: sections 3.2.6-3.2.9

Publisher ID (pp)

Required // All traffic types

The final seller of the traffic source. This value must be consistent with OpenRTB’s Publisher ID and should match the value in the second field of the ads.txt file. One or more Publisher IDs will correspond to a single Supplier ID.

Examples:

pub-4177862836555934
testpub123

Supplier ID (sr)

Required // All traffic types

The domain of the ad system that created the current version of the bid request that corresponds to the impression. This value should match the first field of the associated entry in the publisher’s ads.txt or app-ads.txt file. If you are a supply-side platform (SSP), this is usually your own domain.

Examples:

openx.com
adx.com
rubiconproject.com

Prediction ID (pv)

Required (MediaGuard users only) // All traffic types

A unique identifier that HUMAN uses to link pre-bid and post-bid data. This value should correspond to the value of the lookupId field returned by the MediaGuard API or MediaGuard SDK for the impression's corresponding bid request. If your MediaGuard integration is built on the MediaGuard SDK, you'll need to convert the value of lookupId from a base64-encoded raw byte value to a UUID string.

Example: defc04b9-6558-11e9-9196-1271b71e9caa

For more information, see Closing the loop.

Prediction Timeout (to)

Required (MediaGuard users only) // All traffic types

Whether an impression's corresponding bid request was sent to MediaGuard, and if so, whether MediaGuard successfully returned an IVT prediction for that bid request.

For example, if you sent the bid request to MediaGuard and MediaGuard successfully returned an IVT prediction, this parameter should have a value of 3. If you sent the bid request to MediaGuard and MediaGuard timed out without responding, this parameter should have a value of 1.

Possible values:

0 = N/A (MediaGuard was not called at all)
1 = Response timeout (MediaGuard was called but did not respond)
2 = Error response (MediaGuard was called but responded with an error)
3 = Successful response (MediaGuard was called and returned an IVT prediction)
4 = Other

For more information, see Closing the loop.

Transaction ID (ti)

Required // All traffic types

A unique identifier that HUMAN uses to identify each impression.

To use this parameter properly, you must generate a new random value every time you serve an ad and pass this value through the tag accordingly.

Example: 4d2ab6f3189e72166c3e8ca424aa1528