FraudSensor FAQ

Below you’ll find a list of frequently asked questions (and answers) about MediaGuard. If you have a question that isn’t answered here, please reach out to a HUMAN representative for assistance. We’re always happy to help!

Does FraudSensor flag based on ads/app-ads.txt data?

FraudSensor does not actively flag events based on ads.txt data. However, FraudSensor does actively flag based on app-ads.txt data, though only “Unauthorized” sellers are flagged.

Does FraudSensor flag based on sellers.json data?

FraudSensor does not actively flag based on sellers.Json data.

How does FraudSensor handle inline frames?

In order to function properly, FraudSensor’s detection tags should be served with the relevant ad. If an ad is rendered in an inline frame (also known as an iframe), that detection tag should be deployed within the same iframe. Detection tags deployed outside of an iframe can still collect certain signals for ads rendered inside an iframe, but we won’t be able to collect signals related to user interaction (like clicks, mouse movement, and so on).

Sandboxed iframes require the same type of detail as regular iframes but require a specific token. If you are running ads within a sandboxed iframe, please reach out to a HUMAN representative for assistance.

How does FraudSensor handle throttling and caching?

There is no caching allowed on the client-side. FraudSensor tags (of all types) should be served to all users for every ad impression.

HUMAN may throttle traffic to our servers to meet contractual agreement. However, you should still tag 100% of the incoming traffic you receive.

Which detection tag collects the most/strongest signals?

The JavaScript tag is FraudSensor’s strongest and most flexible detection tag, but it may not be the best choice in all contexts.

For an overview of the different tag types and their uses, see our Tag Types and Environments guide.

Can you deploy multiple detection tags on a single page?

If multiple FraudSensor tags are deployed to the same page, like having multiple subsequent impressions or deploying multiple tags on the same page load (in the case of multiple HUMAN-tagged creatives on one page), HUMAN will identify these other tags. Once identified, the grouped tags can communicate and associate their data with one another to reach a comprehensive decision using all available information, which results in a consistent decision across HUMAN’s respective detection tags.

Can you use the same detection tag type across all environments?

We do not recommend taking a “one tag fits all” approach to detection. When choosing detection tags for each ad placement, it’s important to consider which tag will best suit the ad environment. For example, if an environment supports JavaScript tags, using a 1x1 tag instead will yield fewer signals and offer less protection.

For an overview of the different tag types and their uses, see our Tag Types and Environments guide.

What happens if I believe FraudSensor has mistakenly flagged traffic?

If you believe FraudSensor is flagging traffic inaccurately, please reach out to your Technical Account Manager and request a false-positive check. False-positive checks can help determine whether valid traffic is mistakenly being flagged as invalid.

After you’ve requested this review, your Technical Account Manager will work with HUMAN’s Detection team to gather more information and verify the accuracy of your results. Your Technical Account Manager will then help you take further steps as needed.