Seller Retail Analytics Reports

This pages provides instructions on what transform code should be added to a script manifest file to transform Amazon data from the Seller Retail Analytics reports

Overview

The Daasity transformation code maps data from the Amazon Seller Central schema into the Unified Traffic Schema (UTS) for traffic data

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:

• Sales and Traffic Business Report

• Sales and Traffic SKU Report

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

• Initialization

Transformation Code Requirements

To enable the data transformation from the Amazon Seller Central schema into UOS, the following code must be run in a workflow:

  uts_amazon:
    integrations:
      - amazon_selling_partner
    scripts:
     - "github://platform-sql-shared/scripts/base/2650_uts/2653_UTS_BAS_traffic_amazon.sql"
     - "github://platform-sql-shared/scripts/base/2650_uts/2663_UTS_BAS_product_page_amazon.sql"

Unified Traffic Schema

Code to populate the UTS tables with general traffic data and product views data from Amazon

• https://github.com/Daasity/platform-sql-shared/blob/master/scripts/base/2650_uts/2653_UTS_BAS_traffic_amazon.sql

• https://github.com/Daasity/platform-sql-shared/blob/master/scripts/base/2650_uts/2663_UTS_BAS_product_page_amazon.sql