Transformation Configuration Setup
This pages provides instructions on what transform code should be added to a script manifest file to transform Klaviyo data into the Unified Notification Schema (UNS)
Overview
The Klaviyo extractor provides data on email and SMS subscribe / unsubscribe, campaigns / flows, profiles and sends / bounces / opens / clicks. The Daasity transformation code maps data from the Klaviyo schema into the Unified Notifications Schema (UNS)
Feature Dependencies
You must have enabled our Code Repository 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 Transformation Configuration section of our Help documentation to familiarize yourself with our workflow engine and script manifest files.
Script Manifest File (YML)
Upstream Transformation Dependencies
This code is dependent on the following integration being installed:
Klaviyo
This code block is dependent on the following upstream code blocks being implemented:
Transformation Code Requirements
This Transformation Code is for the V1 / V2 API version of Klaviyo data
To enable the data transformation from the Klaviyo schema into UNS, the following code must be run in a workflow:
Unified Notification Schema
Code to populate the UNS tables:
Last updated