For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
HUMAN DashboardHUMAN WebsiteRequest a Demo
Media SecurityMalvertising DefenseAPI Reference
Media SecurityMalvertising DefenseAPI Reference
  • Media Security Overview
    • MediaGuard Overview
    • FraudSensor Overview
    • Closing the Loop - MediaGuard and FraudSensor
    • IVT Taxonomy
    • Click Defense Overview
    • Metrics (Media Security)
    • Brand Safety Web Crawler
  • HUMAN Dashboard
    • Understand the HUMAN Dashboard
  • Analysis and Reporting
    • Explore Dashboard (Legacy)
    • Create Custom Data Views
    • Schedule Reports and Alerts
    • Access Transaction Level TLX Reports
  • Integrations
LogoLogo
Login
Login
HUMAN DashboardHUMAN WebsiteRequest a Demo
On this page
  • How MediaGuard works
  • Get started with MediaGuard
Media Security Overview

MediaGuard Overview

Pre-bid prediction to prevent ad fraud before it happens.

Was this page helpful?

FraudSensor Overview

Post-bid detection to gather more data about traffic quality and ecosystem insights.

Next
Built with

MediaGuard is HUMAN’s predictive, pre-bid advertising fraud prevention system that predicts, in real-time, whether a specific ad opportunity is likely to be invalid traffic (IVT) based on information provided from the OpenRTB bid object. It focuses on identifying illegitimate ad impressions that are not being served to, or viewed by, humans in real-time. You can think of MediaGuard as a predictive model based on reputation data. MediaGuard is deployed in tandem with FraudSensor. The information collected via the FraudSensor tag is used to train the MediaGuard algorithms.

You must include FraudSensor as a component of your overall MediaGuard integration. When used in tandem, FraudSensor can validate the predictions you receive from MediaGuard. This combination of pre-bid and post-bid data also helps us fine-tune MediaGuard’s prediction models against new and evolving threats.

To learn more about using MediaGuard and FraudSensor together, see Closing the Loop.

How MediaGuard works

MediaGuard is an intermediary service that sits between the bid requests you receive and the bids that you actually make. After you’ve set up a MediaGuard integration, you’ll be able to send data to MediaGuard and receive real-time predictions about your bid requests.

Every time you receive a bid request, you’ll either need to extract certain details from that bid request and send them to MediaGuard or send the bid request’s entire OpenRTB BidRequest object to MediaGuard. MediaGuard analyzes these details to determine whether the user driving that bid request is valid or invalid. Any invalid bid requests are sorted into different IVT categories with information about the specific traits displayed by that bid request.

MediaGuard then delivers bot or fraud decisions on individual ad opportunities in milliseconds. Based on this decision, you can decide whether to continue bidding on a specific ad impression. For example, you might configure your bids to automatically drop any bid requests that receive an IVT=true response from MediaGuard. You can also view your MediaGuard data in the HUMAN Dashboard or via our Reporting API.

Get started with MediaGuard

To get started with MediaGuard, you’ll need to set up an integration with either the MediaGuard API or the MediaGuard SDK.

A HUMAN representative will help you choose the best integration option to suit your needs, walk you through the integration process, and set up a new MediaGuard cluster on your behalf.