Transformation Configuration Setup

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

Overview

The Google Ads extractor provides data on marketing spend and performance from impressions through vendor attributed revenue and orders. The Daasity transformation code maps data from the Google Ads 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

Transformation Code Requirements

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

  ums_google_ads:
    integrations:
      - google_ads
    scripts:
      - "github://platform-sql-shared/scripts/pro/1500_ums/1530_UMS_BAS_google_spend.sql"
      - "github://platform-sql-shared/scripts/base/1500_ums/vendor_kpi/2530_UMS_BAS_google_adwords.sql"

We recommend this code be added within a UMS block that transforms all your marketing integrations into the appropriate UMS tables

UMS Master Spend

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

UMS Vendor Performance

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

Last updated

Was this helpful?