sc_marketing_campaign_mapping

In this article

• Summary
• Supported Use Cases
• When not to use the view

Summary

Often, campaign names from one data source (i.e., Facebook Ads) may differ from those from another (i.e., Google Analytics). When this happens, combining the statistics gathered from one data source with the other is not easily accomplished. SoundCommerce has instituted a mapping process to ensure that campaigns have the same name, regardless of data source. The sc_marketing_campaign_mapping view provides a look into the mapping SoundCommerce uses. This view can be manipulated in sc.io through the UTM override feature. 

• View Grain: campaigns
• Primary (Composite) Key(s):
  • campaign_id
• Foreign Key(s):
  • source_mapped
  • medium_mapped

Supported Use Cases

The following use cases are examples and only provide a subset of all potential use cases that can be addressed with data found in sc_marketing_campaign_mapping and other views. This list should not be assumed to be comprehensive. 

• I want to ensure that campaign names from source/medium X match up with source/medium Y. 

When not to use the view

This is not an analytics view. This view helps users understand the actual campaign translations from the initially ingested value to the business-friendly override.

Return to SoundCommerce Retail Modules