Email & SMS
This page provides detailed instructions on the Email & SMS Code transform code block and what should be added to the Script Manifest file in order to execute the code
Script Manifest File (YML)
Upstream Transformation Dependencies
This code block is dependent on the following upstream code blocks being implemented:
Initialization
UOS
UNS
Order Status
Transformation Code Requirements
The following code should be added to the main workflow in the appropriate position, after Product and Inventory per the Transform Code Sequence - DRP page
Email & SMS
Add this code to create the tables that enable performance of your Email & SMS channels
[
drp.notification_engaged_file_size
][
drp.notication_campaign_detail
][
drp.notification_product_purchase_view_through
][
drp.notification_file_size_monthly
][
drp.notifications_customer_profile
]
Create the [uns.unique_contacts_lkp
] table to link contacts across the different Email, SMS providers if multiple are used
Build the history tables to track status and file size over time
Build the [drp.notication_campaign_detail
] table to be able to analyze campaign performance down to the individual customer level
Build the [drp.notification_product_purchase_view_through
] table to understand the performance of campaigns based on a view through perspective - i.e. the impact of email / SMS performance if the customer interacted with the campaign but did not purchase directly from the campaign
Build the [drp.notification_file_size_monthly
] table to track the monthly file size
Build the [drp.notifications_customer_profile
] table to understand customer level interactions with Email / SMS
Last updated