Skip to main content

Detection Tags (FraudSensor)

FraudSensor uses detection tags to collect the signals that drive HUMAN's decisioning. These tags are designed to work with your ad server and must be deployed alongside each ad you serve.

Some of the signals collected by FraudSensor's detection tag are detected automatically when the tag is deployed; others require you to send specific information to HUMAN by passing key/value pairs through the body of the tag. Your HUMAN representative will help you build your own unique FraudSensor tag and advise you on which parameters to include.

Placing detection tags

FraudSensor’s detection tags tend to be most effective when they are applied universally to all of your organization’s ads (also known as the “account level” or “organization level”). However, these tags can also be applied to specific ads as needed (on the “placement level,” “creative level,” or “campaign level”), which may be useful for certain types of detection.

In order to capture as many signals as possible, each FraudSensor tag must be served with the relevant ad. For example, if an ad is rendered with an HTML iframe, its detection tag should be run within the same iframe. Placing a detection tag in a separate iframe will still yield a limited number of signals, but you will not receive signals related to user interaction or other information specific to that iframe.


Please do not modify these tags after you've configured them, as any unexpected changes may interrupt HUMAN’s ability to collect signals. If you need to add, remove, or change any aspects of your existing detection tags (including custom parameters), please reach out to your HUMAN representative for assistance.