White Ops: HUMAN Advertising Integrity

Protection against digital programmatic advertising fraud

Description:

HUMAN is a cybersecurity company that collectively protects global enterprises and internet platforms from digital fraud and abuse. Sophisticated bots look and act like humans when they visit websites, fill out forms, take over accounts, scrape information, and commit payment fraud creating billions of dollars in losses for brands and consumers. We Stop Them.

HUMAN’S Human Verification Engine is powered by our Multilayered Detection Technology combining technical evidence, machine learning, threat intelligence, and continuous adaptation and solves top enterprise pain points through our product offerings.

Advertising Integrity is HUMAN’s tool for detecting and preventing digital advertising fraud. Our leading market solution provides digital advertisers (including mobile publishers and programmatic advertising platforms) with the knowledge to protect themselves against malicious bot activity and prevent losses from wasted ad spend. Our joint pre-bid and post-bid solutions (known as MediaGuard and FraudSensor, respectively) ensure that your ads are delivered to humans and not bots, boosting your overall ROI.

Samples/Tables Included:
– White Ops Advertising Integrity FraudSensor reporting data
– White Ops Advertising Integrity MediaGuard reporting data

Fields Included in FraudSensor:
– Timestamp: The date and time of the impression.
– Href Domain: The domain where the impression occurred.
– Referring Domain: The domain that referred a user to the site of the impression.
– Intended Domain: The domain where the advertisement was intended to be delivered.
– True Domain: The domain where the impression actually occurred (when supported by browser/device/OS constraints).
– Mismatch Domain: A Boolean value that, when true, indicates a mismatch between the intended domain and true domain.
– Top Level Href Domain: The top-level href domain (without subdomain information).
– Top Level True Domain: The top-level true domain (without subdomain information).
– Top Level Ref Domain: The top-level referring domain (without subdomain information).
– Page: The webpage where the impression occurred.
– App ID: For mobile apps—the app bundle in which the ad was delivered, as provided by the publisher.
– Detected App ID: For mobile apps—the app bundle in which the ad was delivered, as detected by HUMAN.
– Advertiser: The advertiser or brand that runs the ad campaign.
– Campaign ID: The unique identifier for tracking your advertising campaign.
– Dimensions: The width and height of the ad creative, measured in pixels.
– Ad ID/Placement ID: The unique identifier for the digital advertisement.
– Media Type: The media type of the inventory (banner, video, etc).
– Buy Type: Whether the ad was purchased through programmatic or direct buying.
– Device Type: The type of device where the ad was delivered (mobile, desktop, etc).
– Has Prevention ID: A Boolean value that, when true, indicates that the impression has a corresponding MediaGuard prevention ID.
– Publisher ID: The publisher of the traffic source.
– Supplier ID: The domain of the supplier of the traffic source.
– Environment: The type of environment where the ad was delivered (mobile web, desktop, etc), as detected by HUMAN.
– OS: The operating system of the device where the ad was delivered.
– Platform Type: The type of platform where the ad was delivered (desktop, mobile, CTV, etc), as detected by HUMAN.
– IVT Categories: The IVT categories associated with the impression, if applicable.
– Tag ID: The identifier of the HUMAN tag that detected the impression.
– Tag Name: The name of the HUMAN tag that detected the impression.
– Transaction ID: The unique identifier for the transaction.
– IVT: A Boolean value that, when true, means that the impression was identified as invalid traffic (IVT).
– SIVT: A Boolean value that, when true, means that the impression was identified as Sophisticated IVT (SIVT).
– GIVT: A Boolean value that, when true, means that the impression was identified as General IVT (GIVT).

Fields Included in MediaGuard aggregate level views (see Usage Examples section for specific views):
– Date: The date and time of the request.
– Publisher ID: The publisher ID, as provided in the request to MediaGuard.
– Supplier ID: The supplier ID, as provided in the request to MediaGuard.
– Device Type: The device type, as provided in the request to MediaGuard.
– Media Type: The media type, as provided in the request to MediaGuard.
– Total Requests: The total number of requests, grouped into 60-second intervals.
– Valid Requests: The total number of valid requests, grouped into 60-second intervals.
– IVT: The number of requests that were identified as invalid traffic (IVT).
– SIVT: The number of requests that were identified as Sophisticated IVT (SIVT).
– GIVT: The number of requests that were identified as General IVT (GIVT).

Example Use Case:
Analyze Bot Traffic percentage by publisher or domain. Frequently, you’ll find that certain publishers or domains have high bot rates that account for the bulk of fraudulent activity. Identify these hotspots and address them by blocklisting poor-performance domains and/or notifying the publisher so they can address the issue.

About the Provider:

White Ops is the global leader in collective protection against sophisticated bot attacks and fraud. We protect enterprises across the globe – including the largest internet platforms – from sophisticated bot attacks by verifying the humanity of more than five trillion online interactions every week. The most sophisticated bots look and act like humans when they visit websites, fill out forms, take over accounts, scrape information, and commit payment fraud. We stop them. White Ops recently received an investment by Goldman Sachs Merchant Banking Division and ClearSky Security to support the company’s next phase of growth. To learn more, visit www.whiteops.com.

Visit the provider’s website for more

Get access to White Ops: HUMAN Advertising Integrity Dataset in Snowflake

Sign up for a free trial

Already a Snowflake customer?
Access this dataset directly from your Snowflake account