The HUMAN Dashboard offers several tools to help visualize your organization’s traffic data according to any number of custom configurations. However, if you’re not sure where to get started or don’t know which parameters would be most useful to incorporate into your visualizations, we’ve outlined some best practices for data visualization. You can get started with these configurations right out of the box or use them as a foundation to build your own custom configurations.
Although this guide includes screenshots from the Explore section of the Dashboard, these data configurations are also compatible with HUMAN's Reports feature. You can create reports with these parameters by importing data from an existing Explore view, or create a new report from scratch. Fields, metrics, and filters are consistent between Explore and Reports, which means you can incorporate the following parameters into your reports exactly as they are listed below.
Note: Since some customers have asked us to apply custom names to certain fields, the specific fields listed below may be named differently for your organization's instance of the HUMAN Dashboard. If you'd like to rename any of these fields, please reach out to your HUMAN representative.
Desktop traffic overview
This configuration provides an overview of site traffic that originated from desktop environments. You can recreate it by selecting the following parameters:
Fields
Href Domain: The domain where each impression occurred.
Provider: The publisher of the inventory.
Environment: The environment of each impression (Desktop, Mobile Web, etc).
IVT Categories: (optional) The HUMAN IVT category, if applicable.
Filters
Environment: Use the condition “Is Desktop” to only include traffic from desktop environments.
Total Events: (optional) Use the condition “Greater than 1000” to only include data from sources of traffic with more than 1,000 events.
Sophisticated IVT%: (optional) Use the condition “Greater than 1” to only include data from sources of traffic with SIVT levels of 1% or higher.
Metrics
We recommend sorting your data by the Sophisticated IVT% metric to determine which sources of traffic are bringing in the highest levels of SIVT. Sorting this metric by descending order will highlight the sources of traffic that are bringing in the highest percentages of SIVT.
Mobile app traffic
This configuration provides an overview of site traffic that originated from mobile app environments. You can recreate it by selecting the following parameters:
Fields
Detected App ID: The app ID detected by HUMAN.
Provider: The publisher of the inventory.
Environment: The environment of each impression (Desktop, Mobile Web, etc).
IVT Categories: (optional) The HUMAN IVT category, if applicable.
App Bundle: The client-defined app ID.
App Mismatch: A true or false value based on the consistency between the client-defined app ID and the app ID detected by HUMAN. If this value is True, a mismatch was detected.
Filters
Environment: Use the condition “Is Mobile App” to only include traffic from mobile app environments.
Total Events: (optional) Use the condition “Greater than 1000” to only include data from sources of traffic with more than 1,000 events.
Sophisticated IVT%: (optional) Use the condition “Greater than 1” to only include data from sources of traffic with SIVT levels of 1% or higher.
Metrics
We recommend sorting your data by the Sophisticated IVT% metric to determine which sources of traffic are bringing in the highest levels of SIVT. Sorting this metric by descending order will highlight the sources of traffic that are bringing in the highest percentages of SIVT.
Mobile web traffic
This configuration provides an overview of site traffic that originated from mobile web environments. You can recreate it by selecting the following parameters:
Fields
Href Domain: The domain where each impression occurred.
Provider: The publisher of the inventory.
Environment: The environment of each impression (Desktop, Mobile Web, etc).
IVT Categories: (optional) The HUMAN IVT category, if applicable.
Filters
Environment: Use the condition “Is Mobile Web” to only include traffic from mobile web environments.
Total Events: (optional) Use the condition “Greater than 1000” to only include data from sources of traffic with more than 1,000 events.
Sophisticated IVT%: (optional) Use the condition “Greater than 1” to only include data from sources of traffic with SIVT levels of 1% or higher.
Metrics
We recommend sorting your data by the Sophisticated IVT% metric to determine which sources of traffic are bringing in the highest levels of SIVT. Sorting this metric by descending order will highlight the sources of traffic that are bringing in the highest percentages of SIVT.
Traffic by publisher
This configuration provides an overview of the publishers driving your inventory. You can recreate it by selecting the following parameters:
Fields
Provider: The publisher of the inventory.
Environment: The environment of each impression (Desktop, Mobile Web, etc).
IVT Categories: (optional) The HUMAN IVT category, if applicable.
Filters
Total Events: (optional) Use the condition “Greater than 1000” to only include data from sources of traffic with more than 1,000 events.
Sophisticated IVT%: (optional) Use the condition “Greater than 1” to only include data from sources of traffic with SIVT levels of 1% or higher.
Metrics
We recommend sorting your data by the Sophisticated IVT% metric to determine which sources of traffic are bringing in the highest levels of SIVT. Sorting this metric by descending order will highlight the sources of traffic that are bringing in the highest percentages of SIVT.
Traffic by supplier
This configuration provides an overview of the suppliers providing your publisher. You can recreate it by selecting the following parameters:
Fields
Environment: The environment of each impression (Desktop, Mobile Web, etc).
IVT Categories: (optional) The HUMAN IVT category, if applicable.
Seller: The supplier of the inventory.
Filters
Total Events: (optional) Use the condition “Greater than 1000” to only include data from sources of traffic with more than 1,000 events.
Sophisticated IVT%: (optional) Use the condition “Greater than 1” to only include data from sources of traffic with SIVT levels of 1% or higher.
Metrics
We recommend sorting your data by the Sophisticated IVT% metric to determine which sources of traffic are bringing in the highest levels of SIVT. Sorting this metric by descending order will highlight the sources of traffic that are bringing in the highest percentages of SIVT.
Sorting and filtering FAQ
Why sort by Sophisticated IVT% rather than raw Sophisticated IVT?
We recommend sorting by Sophisticated IVT% because this metric provides greater insight into how many events are being flagged than filtering by raw Sophisticated IVT. Keep in mind that a seemingly-large number of SIVT events may not correlate to a high percentage of SIVT when the total number of events is taken into consideration. If the number of total events far outweighs the number of SIVT events, the resulting percentage of SIVT will be much smaller and may not provide the necessary information to find problematic domains, app bundle IDs, or publisher/supplier IDs.
For example, if HUMAN flags 50,000 events as SIVT, this may seem like a high level of fraudulent traffic. However, if HUMAN recorded 10,000,000 total events during the same period, then these SIVT events only comprise 0.02% of your overall traffic, which is a very low level overall. Sorting your data by SIVT% rather than raw SIVT will immediately make clear which sources of traffic are bringing in the highest proportional levels of SIVT overall.
Why filter by Sophisticated IVT%?
Generally speaking, HUMAN considers an Sophisticated IVT level of 1% or higher to be the threshold for investigating traffic. Creating a filter that only includes sources of traffic with SIVT levels greater than 1% will highlight any sources of traffic that warrant investigation, which helps you focus your efforts accordingly.
Why filter by Total Events?
Advertisers often use the term “cost per thousand” or “cost per mille” (CPM) when referring to the price of 1,000 ad impressions on one webpage. Since ads are measured by the thousand, any inventory that includes less than 1,000 events is considered a low source of traffic. Creating a filter that only includes inventories with at least 1,000 events ensures that only moderate or high sources of traffic are included in your reports.