Snowflake Data Fields

After you've imported your HUMAN data into Snowflake, you'll be able to view the following data fields.


MediaGuard

There are two views available for MediaGuard: advertising_integrity_fraudsensor and advertising_integrity_mediaguard. Each view includes the following data fields (for FraudSensor and MediaGuard, respectively):

FraudSensor fields MediaGuard fields

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: The app bundle in which the ad was delivered, as provided by the publisher (for in-app mobile environments only). 

Detected App ID: The app bundle in which the ad was delivered, as detected by HUMAN (for in-app mobile environments only).

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, indicates that the impression was identified as invalid traffic (IVT).

SIVT: A Boolean value that, when true, indicates that the impression was identified as Sophisticated IVT (SIVT).

GIVT: A Boolean value that, when true, indicates that the impression was identified as General IVT (GIVT).


BotGuard for Growth Marketing

A transaction-level view is available for BotGuard for Growth Marketing, with the following data fields:

Timestamp: The date and time of the start of the session (first pageview).

Tag ID: The identifier of the HUMAN tag that detected the pageview/session.

Tag Name: The name of the HUMAN tag that detected the pageview/session.

Session ID: The unique identifier for the session.

User ID: The unique identifier for the user associated with the session, as configured by your HUMAN tag.

UTM Source: The utm_source parameter, as detected from the user's referring URL.

UTM Medium: The utm_medium parameter, as detected from the user's referring URL.

UTM Campaign: The utm_campaign parameter, as detected from the user's referring URL.

UTM Term: The utm_term parameter, as detected from the user's referring URL.

UTM Content: The utm_content parameter, as detected from the user's referring URL.

Referring Domain: The domain that referred a user to the site of the pageview/session.

Page: The page where a pageview/session occurred.

Client Page: The page where a pageview/session occurred, with top-level domain information removed.

URL: The full URL of the page where a pageview/session occurred.

OS: The operating system of the device where the pageview/session occurred. 

OS Version: The version of the operating system of the device where the pageview/session occurred. 

Browser Name: The name of the browser where the pageview/session occurred. 

Browser Version: The version of the browser where the pageview/session occurred. 

IVT Categories: The IVT categories associated with the pageview/session, if applicable. 

IVT: A Boolean value that, when true, indicates that the pageview/session was identified as invalid traffic (IVT).

SIVT:  A Boolean value that, when true, indicates that the pageview/session was identified as Sophisticated IVT (SIVT).

GIVT: A Boolean value that, when true, indicates that the pageview/session was identified as General IVT (GIVT).


BotGuard for Applications

A transaction-level view is available for BotGuard for Applications, with the following data fields:

Timestamp: The date and time of the event.

Mode: The mode in which the detection tag has been deployed (0 = Passive, Non-Interactive, 1 = Passive, Interactive, 2 = Active)

Tag ID: The identifier of the HUMAN tag that detected the event.

Transaction ID: The unique identifier for the event.

Site ID: The unique identifier for your website.

User ID: The unique identifier for the user associated with the event.

Cookie ID: The unique identifier for the cookie associated with the event.

Country: The country where the event originated.

ASN: The ID of the autonomous system (ASN) through which the event was routed.

ASN Name: The name of the autonomous system (ASN) through which the event was routed.

User Agent: The user agent of the user associated with the event.

IP: The IP address of the user associated with the event.

Referring Domain: The domain that referred a user to the site of the event.

Href Domain: The domain where the event occurred.

Top Level Href Domain: The top-level href domain (without subdomain information).

Top Level Ref Domain: The top-level referring domain (without subdomain information).

Page: The webpage where the event occurred.

Form ID: The unique identifier of the form where the event occurred.

Platform Type: The type of platform where the event occurred (desktop, mobile, CTV, etc), as detected by HUMAN.

Device Type: The type of device where the event occurred (mobile web, desktop, etc).

Device ID: The unique ID of the user’s device, as designated by their IDFA or AAID (for in-app mobile environments only). 

App ID: The app bundle where the event occurred (for in-app mobile environments only).

OS: The operating system of the device where the event occurred. 

Event Type: The specific type of user event being monitored (account login, password reset, etc), as configured by your HUMAN tag.

Threat Profile: The primary threat type associated with the event (valid, nonstandard, or bot).

Threat Categories: Additional information about the event’s threat type, if applicable.

Action: The suggested action returned by the Mitigation API (e.g., block, allow, verify) for that event.

Event Success: A Boolean value that, when true, indicates that the user's interaction with the protected surface was successful.

Username: The SHA1-hashed value of the username associated with the event.

User Exists: A Boolean value that, when true, indicates that the user has provided a username that actually exists (in the case of a login event only).

Password Match: A Boolean value that, when true, indicates that the user's inputted password was correct.

Endpoint: The URL of your API endpoint or server to which HUMAN-protected events will be sent.

Client Error: A Boolean value that, when true, indicates that the request to the Mitigation API was malformed or invalid, usually corresponding to a 400-level HTTP status code.

Server Error: A Boolean value that, when true, indicates that the request to the Mitigation API resulted in an error code during the API response, usually corresponding to a 500-level HTTP status code.

Validation Error: A Boolean value that, when true, means that contained data that the request to the Mitigation API failed logic validation, usually corresponding to a 400-level HTTP status code.

Custom: A JSON object containing custom fields that you can configure during the setup of your BotGuard for Applications integration.