Last updated
Was this helpful?
Last updated
Was this helpful?
The Cordial data share provides data on email and SMS subscribe / unsubscribe, regular and triggered campaigns, contacts and sends / bounces / opens / clicks. The Daasity transformation code maps data from the Cordial data share into a Cordial schema and then finally into the Unified Notifications Schema (UNS)
You must have enabled our feature in order to both access the Daasity transformation code as well as modify a Script Manifest File enabling this code to execute
We recommend you review the section of our Help documentation to familiarize yourself with our workflow engine and script manifest files.
This code is dependent on the following data share being setup:
Cordial
This code block is dependent on the following upstream code blocks being implemented:
This Transformation Code is for the Cordial Snowflake Data Share
To enable the data transformation from the Cordial data share into the Cordial schema and UNS, the following code must be run in a workflow:
The Cordial Schema scripts must be modified to use the name of the Snowflake share that Cordial has created. Look for this block <'database_share_name'> within the SQL code and replace this with the name of the database share
Code to populate the UNS tables:
The data from the Cordial Snowflake share includes JSON that must be de-nested in order to populate the UNS tables. The following code must be copied into your own and modified to have the name of the data share updated. This code must be run to de-nest the data and populate the Cordial schema which is used as the source for UNS:
This pages provides instructions on what transform code should be added to a script manifest file to transform Cordial data into the Unified Notification Schema (UNS)