sc_adspend_order_attribution

In this article

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

Summary

The sc_adspend_order_attribution view explicitly ties an order with the money spent acquiring that order. Impressions, clicks, and ad costs are all aggregated to the order level to analyze the relationship between ad dollars and order acquisition. 

• View Grain: order-level data
• Primary (Composite) Key(s):
  • order_id
• Foreign Key(s):
  • campaign_id
  • attribution_date
  • adspend_date
  • cuid

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_adspend_order_attribution and other views. This list should not be assumed to be comprehensive. 

• I am interested in learning what the average ad spend is for all orders placed in a given location for a given date range within a specific campaign.
• Which sources and media drive sales in a specific time frame, location, or customer attribute?

When not to use the view

This view brings together different concepts into a single place. Orders data (and, through it, customer data) can be associated with ads via campaigns, and pertinent metrics can be calculated from this intersection.

This view does not necessarily contain specifics about the following:

• Fulfillment-related metrics (i.e., shipment partner, tracking number, fulfillment breakdown of constituent items)
• Item-related metrics (i.e., sku-level price, sku-level cost, sku-level discounts)
• Product-related metrics (i.e., warehouse inventory for a given product)
• Customer PII-related values (i.e., first and last names, addresses)
• Customer-related metrics (i.e., customer-aggregated sales, lifetime value, running order counts)

Return to SoundCommerce Retail Modules