Snowflake Quickstart

If you're a Snowflake user, you can access HUMAN integrations through the Snowflake Data Marketplace. We’ve compiled a guide to help you query and import your HUMAN data into your Snowflake environment.

Our Human Verification Engine analyzes real-time traffic signals to provide continuous, multi-layered detection throughout your digital ecosystem. Datasets are available for the following HUMAN solutions:

These datasets provide you with the knowledge to explore traffic data, monitor your customer base, and eliminate fraud. HUMAN offers granular data about individual transactions, including “bot or not” decisions and detailed threat taxonomies to isolate hotspots of fraudulent activity. Potential use cases may involve identifying fraudulent ad publishers, analyzing the effects of an email marketing campaign, or discovering the types of automated traffic that your application receives.

Get started

After you’ve spoken to a HUMAN representative to set up your HUMAN account (if you don't have one already), you’ll need to request access to HUMAN data through the Snowflake Data Marketplace.

1. Navigate to the Snowflake Data Marketplace and select HUMAN from the provider drop-down menu.
2. HUMAN’s offerings include three solutions: MediaGuard, BotGuard for Growth Marketing, and BotGuard for Applications. From these options, select the solution that you’d like to use. (If you’d like to use multiple HUMAN solutions, you can repeat these steps for each applicable solution.
3. On the relevant solution’s product page, select Request. A HUMAN representative will contact you shortly to verify and approve your request.

Configure your environment to receive data

To configure your environment in Snowflake, you’ll need to use the ACCOUNTADMIN role or any other role with the IMPORT SHARES privilege. 

There are two ways to set up a share in Snowflake: by using Snowflake's web interface or via SQL commands. For more information about shares, please consult this Snowflake guide.

Web interface setup

Navigate to the Shares tab, then select the Inbound toggle.

You’ll see a list of all the shares available to your account. When you create a database from a share, its name will appear in the Database column. If the Database column is empty, this means you haven’t yet created a database from the share. 

To create a database from the share, select the share and choose Create Database from Secure Share.

SQL setup

Execute a SHOW SHARES statement. The result should include a share name starting with “WHITEOPS_” followed by the name of the solution you selected in the Getting Started section above (either WHITEOPS_ADVERTISING_INTEGRITY, WHITEOPS_MARKETING_INTEGRITY, or WHITEOPS_APPLICATION_INTEGRITY) and the provider “WHITEOPS<region name>”.

For example, your output for may look like this:

show shares;

+---------------------------------+---------+-------------------------+-----------------------+----+-------+---------------------------------------------+

| created_on                      | kind    | name                    | database_name         | to | owner | comment                                     |

|---------------------------------+---------+-------------------------+-----------------------+----+-------+---------------------------------------------|

| Thu, 15 Jun 2017 17:02:29 -0700 | INBOUND | WHITEOPSAWSUSEAST1.WHITEOPS_ADVERTISING_INTEGRITY         |                       |    |       |           |

| Sat, 09 Jul 2016 19:18:09 -0700 | INBOUND | SFC_SAMPLES.SAMPLE_DATA | SNOWFLAKE_SAMPLE_DATA |    |       | Sample data sets provided by Snowflake      |

+---------------------------------+---------+-------------------------+-----------------------+----+-------+---------------------------------------------+

After obtaining the share name, create a database using the following command (replacing <name> with the name you’d like to assign to your new database, <provider_account> with the WHTEOPS<region name> value described above, and <share_name> with WHITEOPS_<product requested>):

CREATE DATABASE <name> FROM SHARE <provider_account>.<share_name>

For example, using the information from the output above, a database creation command might look like this:

CREATE DATABASE myDB FROM SHARE WHITEOPSAWSUSEAST1.WHITEOPS_ADVERTISING_INTEGRITY

If you selected multiple HUMAN solutions in the Getting Started section above, you’ll need to repeat these SQL commands for each applicable solution.

Verify your setup

If you’ve created the database successfully, you should be able to access some or all of the following views in your Snowflake share:

• mediaguard_prebid
• mediaguard_prebid_sampled
• mediaguard_postbid
• botguard_apps
• botguard_growth_marketing

The following views are deprecated but may still be accessible in Snowflake. These views are no longer maintained and should not be used:

• advertising_integrity_fraudsensor
• advertising_integrity_mediaguard
• marketing_integrity
• application_integrity

You will only be able to access views that correspond to the solution(s) you set up in the previous steps. MediaGuard users have access to views for HUMAN’s pre-bid solution (MediaGuard) and post-bid solution (FraudSensor); however, if you have not subscribed to both of these solutions, you will only be able to select pre-bid or post-bid data according to your current setup.

Use HUMAN data in Snowflake

For more information about using your HUMAN data in Snowflake, please consult our Data Fields guide and our Example Queries guide.