What are detection tags?
FraudSensor uses detection tags to collect the data that drives HUMAN’s traffic analysis. These tags consist of several parameters and macros in the tag body that help us collect specific impression-level signals. Your HUMAN representative will help you build these tags, which you must then implement into your own server in order to begin sending data to HUMAN’s detection engine.
HUMAN generates specific detection tags for each FraudSensor user. These tags are designed to work with your ad server and will include any relevant parameters, including standard required parameters, certain recommended and optional parameters, and any HUMAN-supported custom parameters that you have specified.
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, as any unexpected changes may interrupt HUMAN’s ability to collect signals. If you need to add, remove, or change any aspects of your detection tags, including custom parameters, please reach out to your HUMAN representative for assistance.