Snowflake Native Application - July 31, 2024

Below are details about enhancements made to our Snowflake Native Application on July 31, 2024.

Enhanced Identity Resolution Logic

We’ve enhanced our identity resolution algorithm to more effectively and efficiently match against our Identity Graph. As a result, customers will see improved match rates (if receiving Identity keys) and fill rates (if receiving Attributes data)!

In-Market Scores Added to Native App

Our proprietary InMarket Score datapoints are now available for appends through the application. InMarket Scores provide insight on consumers' propensity to be in-market for major life purchases (e.g. insurance, mortgage, higher education). These datapoints are derived by combining VMS' unique view of shopping activity across thousands of lead sites along with hundreds of household and consumer level attributes. To add this data to your outputs, reach out to your Customer Success Manager!

Event sharing error notification

When installing the Native Applications, customers must first enable event sharing, so that VMS can properly track/bill usage. We’ve implemented an error message that will appear when users make a call to the application, but have not yet enabled event sharing. Users will not be able to receive data from the app until event sharing is configured. For details on how to enable, consult the application’s readme file.

Licensed features error notification

Our Native Application enables users to key records and/or enrich records, based on what products were purchased. If trying to call a procedure for which the account is not configured, we’ve implemented a new error that will clarify that your account’s settings will not permit the request. For example, if contracted for identity keying, but a user tries to run our Attribute enrichment function, they will receive an error noting that they are not configured for this service.

Bug Fix: Match Level 6 appearing in outputs

Addressed a bug where the level 6 match code was not rendering in the application’s outputs. For reference, match code definitions are provided below:

• 1 - indicates a match at the individual level

• 2 - indicates a match at the household level

• 3 - indicates a lower level match

• 4 - indicates a match to a single identity marker where multiple markers were provided

• 5 - indicates a match to an identity that does not have demographics available – gender, age, and dob are the only fields that may contain values

• 6 - indicates that no match was made our identity graph but a gender could be inferred based on analysis of the name present on inputTCI Licensed File