Best Practices

Keying Frequency

Verisk customers typically get started by running their full population through the Verisk Native Application during implementation.  We then recommend running a full refresh at least once per year, while also running new records through the system regularly (i.e., daily, weekly, etc.). A faster refresh cycle may be needed based on the type of population and use cases.  

Persistent ID Management

When keying data through the Snowflake Native App, Verisk will return a Persistent ID (PID), a Household ID (HHID), and an Address ID (ADDRID).  Verisk may match at different levels depending on the data provided and Verisk’s ability to find a consumer/household/address in our identity graph.  Household level attributes can be extremely valuable depending on the use case and are encouraged to be used when a person level ID (PID) is not available. Records that do not receive a PID, HHID, OR ADDRID have no presence in our graph and likely have limited potential as a marketing opportunity.

If a person level Persistent ID is needed to facilitate data capture, Verisk recommends concatenating the HHID with the first name to create an algorithmic PID.  In this event, Verisk also recommends marking the PID as an algorithmic creation until it can be overwritten with a Verisk provided PID during future keying operations.

Running the Native Application

Verisk recommends using an extra-large (XL) warehouse in Snowflake to run the Verisk Native Application. The application runs against the full Verisk Marketing Solutions graph of billions of records. As such, the compute power of an XL warehouse provides the most efficient way to run the application. Smaller warehouses may struggle to run the application or return data in a timely manner.

Run times for the application will vary. As a benchmark, 1 million records should be processed in under 30 minutes. Internal tests have shown 250 million records to be enriched in under 2 hours. If your process runs for 4 or more hours, we recommend reaching out to our support team: VMSsupport@verisk.com  

Parsing JSON response

The Verisk Native Application responds with a JSON response.  Utilize the example SQL query within Snowflake to parse the response into a table.  Note that you’ll need to update your database/schema/table name and the selection location.  Retrieve the example the SQL code from the following documentation:

Example of Parsed Response: