Unified Traffic Schema (UTS)

This page provides a detailed description of the Unified Traffic Schema (UTS) within the Daasity Data Model and defines each table and column in this schema

Overview

The Unified Traffic Schema (UTS) is a core data model within the Daasity transformation module that helps accelerate development of analytical capability by normalizing all traffic data from Google Analytics (Universal Analytics and GA4), Amazon and retail platforms like Retail Next and ShopperTrak.

The normalized schema was designed to help you in several key areas:

  1. Make an effective transition from GA3 (Universal Analytics) to GA4 by allowing you to compare metrics across the two GA platforms and pick which source to use as your truth for additional analytics

  2. Seamlessly combine your GA3 (Universal Analytics) and GA4 into a single schema to make it easy to report on analytics across platforms

  3. Compare overall conversion metrics across eCommerce, Amazon and Retail

  4. Compare product page performance across eCommerce and Amazon

Entity Relationship Diagram (ERD)

Click on this link to view the ERD for the Unified Traffic Schema (UTS) illustrating the different tables and keys to join across tables.

Unified Traffic Schema Tables

  • GA Comparison [uts.ga_comp]

  • Multi Channel Funnel [uts.multichannel_funnel]

  • Product Page [uts.product_page]

  • Shopping Stage [uts.shopping_stage]

  • Traffic [uts.traffic]

  • Transactions [uts.transactions]

TIP: All the tables contain the following fields which can be used to track the data flow from the source system to the integration schema within the database and then to UTS, our normalized traffic schema

  • channel: the channel associated with the UTMs from the Daasity Channel Mapping process

  • vendor: the vendor associated with the UTMs from the Daasity Channel Mapping process

  • sub-channel: the sub-channel associated with the UTMs from the Daasity Channel Mapping process

  • media_type: the media_type associated with the UTMs from the Daasity Channel Mapping process

  • integration_id: the ID of the integration within the Daasity platform

  • integration_name: the name of the integration within the Daasity UI

  • __loaded_at: defines when the record was last loaded into this table

  • __synced_at: defines when the record was last replicated from the source system into the integration tables

  • __sync_key: defines a unique key that is created as part of the replication from the source system into the integration tables

GA Comparison

Purpose: Enables you to compare your GA3 (Universal Analytics) traffic to your GA4 traffic so you can understand how your metrics will change with GA4

Table Name: uts.ga_comp

Multi-Channel Funnel

Purpose: Enables you to have a single table regardless of data source (GA3, GA4, etc.) to track the individual site visits in the conversion path to a transaction

Table Name: uts.multichannel_funnel

Product Page

Purpose: Enables you to compare product page performance across digital platforms (Ecommerce vs. Marketplace) by combining your GA3/GA4 with your Amazon data

Table Name: uts.product_page

Shopping Stage

Purpose: Enables you to have a single table regardless of data source (GA3, GA4, etc.) to track the site visit data in the conversion funnel

Table Name: uts.shopping_stage

Traffic

Purpose: Enables you to compare product page performance across digital platforms (Ecommerce vs. Marketplace) by combining your GA3/GA4 with your Amazon data

Table Name: uts.traffic

Transactions

Purpose: Enables you to have a single table regardless of data source (GA3, GA4, etc.) to track the site information for each transaction

Table Name: uts.transactions

Last updated