Transformation Configuration Setup

This pages provides instructions on what transform code should be added to a script manifest file to transform Pepperjam data into the Unified Marketing Schema (UMS)

Overview

The Pepperjam extractor provides data on marketing spend and performance from impressions through vendor attributed revenue and orders. The Daasity transformation code maps data from the Pepperjam schema into the Unified Marketing Schema (UMS) for the following marketing channels

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:

• Pepperjam

This code block is dependent on the following upstream code blocks being implemented:

• Initialization

Transformation Code Requirements

To enable the data transformation from the Pepperjam schema into UMS, the following code must be run in a workflow:

  ums_pepperjam:
    integrations:
      - pepperjam_ads
    scripts:
      - "github://platform-sql-shared/scripts/pro/1500_ums/1560_UMS_BAS_pepperjam_spend.sql"
      - "github://platform-sql-shared/scripts/base/1500_ums/vendor_kpi/2560_UMS_BAS_pepperjam.sql"

UMS Master Spend

The following code will transform the specific Pepperjam spend into the [ums.master_spend] table:

• https://github.com/Daasity/platform-sql-shared/blob/master/scripts/pro/1500_ums/1560_UMS_BAS_pepperjam_spend.sql

UMS Vendor Performance

The following code will transform the specific Pepperjam data into the [ums.vendor_performance] table:

• https://github.com/Daasity/platform-sql-shared/blob/master/scripts/base/1500_ums/vendor_kpi/2560_UMS_BAS_pepperjam.sql