Claravine + Snowflake Data Share

Share Data from Claravine to Snowflake

Claravine offers Snowflake Data Sharing to enable data transfer from The Data Standards Cloud to Snowflake with permissioning. Data is shared via read-only direct share for your team to access. With this approach, you can ensure that your application of data standards across campaign, content, and creative data in our platform enhances the quality and speed of your analytics and BI efforts. The Claravine team can support setup.

As data is updated in Claravine platform datasets, it will automatically deliver to Snowflake. By leveraging Claravine as your source of marketing metadata you can simplify your ETL across teams and systems.

Enable Data Sharing

The Snowflake Data Sharing configuration is a multi-step process that will be supported by your Claravine contact. Reach out to get started.

Background Documentation

• https://docs.snowflake.com/en/user-guide/security-access-control-overview
• https://docs.snowflake.com/en/user-guide/data-sharing-intro

Set Up Data Sharing

Template Setup

Claravine will set up templates in the Claravine platform for the Claravine Snowflake data sharing account, and set customer database and schema as the destination. This includes using the customer’s exact table configuration requirements (include code/abbreviation values, hidden fields, concatenations, autofills, etc.).

Integration Testing

Claravine will work with the customer to test the Claravine <> Snowflake integration with a submission to make sure data is coming over correctly and in the right Snowflake location

1. Claravine creates data share object in Snowflake for the customer
2. Claravine adds customer template tables to data share by submitting a row
3. Claravine confirms customer has access to data through share object

Requirements: Snowflake account identifiers from customer

Managing Data History

Data is overwritten with the most recent iteration in the case of resubmissions (i.e., the data in Snowflake will reflect the most recent version with no history tracking). Discuss if the customer needs the Created and Updated dates or Claravine ID to help manage new/edited data. Additionally, the customer may leverage Snowflake procedures when handling the received data to retain historical records in a secondary table.

Managing Changes or Additions

Customers can submit a ticket any time they want Snowflake share access to a new template or if changes are needed.