--- schema_version: "1" id: 1416e2a84fe651c80c1ec883f3a2609d7f8389e07c90294a2957d341aa75852d title: eCommerce Package Configuration Guide collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mc_ab_ecommerce_package_technical_specifications.md canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mc_ab_ecommerce_package_technical_specifications.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: ca3ded0528e440ccb665741bdfa7d7e8c5364f26dbf1145f3817bbf6885b7989 description: The eCommerce Dimension Package includes standard dimension packages derived from a standardized data extension–based data model. This functionality provides a turnkey solution that brings ecommerce and purchase data into Marketing Cloud Engagement without the need for a costly custom implementation. products: - Marketing - Marketing Cloud Engagement release: "264" --- # eCommerce Package Configuration Guide The eCommerce Dimension Package includes standard dimension packages derived from a standardized data extension–based data model. This functionality provides a turnkey solution that brings ecommerce and purchase data into Marketing Cloud Engagement without the need for a costly custom implementation. The dimension package set includes two primary components: - Data extension templates in Email Studio - Dimension Package Set in Audience Builder ## Configuration This section outlines the data extensions required for the eCommerce Dimension Package Set. Each subscriber-centric data extension relies on identified subscribers and an Engagement subscriber key value. ## Standard Order Header Data Extension Use this data extension as a universal purchase event repository. Some eCommerce providers choose to generate this information in a different model than what is defined, such as XML or JSON. We chose to this model for simplicity and consistency.
Related Dimension Packages
  • Purchase LTD Product
  • CountPurchase LTD Order
  • CountPurchase LTD
  • RecencyPurchase LTD
  • SpendDays Since Last
  • PurchaseAverage Days
  • Between PurchasesAverage
  • Order ValueProducts
  • Purchased by Product Name (EVER)
  • Products Purchased by Days
  • Products Purchased by Product Name Last 30, 60 & 90 Days
  • Products Purchased by Product SKU Last 30, 60 & 90 Days
  • Orders by Promotion Code
  • Orders by Promotion Code TLD
  • Orders by Delivery Method
  • Orders by Discount Amount
  • Orders by Channel
  • Orders by Status
  • Orders by Date
  • Orders by Total Order Amount
STD\_ORDER\_HEADER This data extension contains order header information from an eCommerce system. | Field Name | Description and Comments | Data Type | Primary Key | Required | | --- | --- | --- | --- | --- | | SubscriberKey | The subscriber key includes a client-specific value supplied in your data. Because this value often contains an email address or other PII-type data, some web analytics providers choose to use the Subscriber ID bigint value from Marketing Cloud Engagement. For SubscriberID values in the native data load, either perform a join before loading data into Engagement or after loading data via query activity using Data Views. | Text (100) | Y | Y | | OrderHeaderID | This value contains the primary identifier of a given order. The OrderHeaderID and the subscriberKey values make up the composite key for this data source. You can perform an add or update on this data source to update Engagement when an order ships or the status changes. | Text (100) | Y | Y | | StoreID | This value includes a foreign key to the STD\_STORE data source. | Text (100) | | N | | OrderAmount | This value represents the total order amount, including the sum of all items, tax, shipping, and any additional fees. | Decimal (10) | | Y | | OrderLineItemsQty | The total number of line items in a given order | Number | | Y | | OrderStatus | The current, user-defined status of an order | Text (100) | |   | | OrderChannel | Typically the channel the order originated from | Text (100) | | N | | DeliveryMethod | User-defined value identifying the selected shipping method | Text (100) | | N | | ShippingDate | The date the order shipped | Date - (MM/DD/YYYY) | | N | | OrderDate | The date the customer placed an order | Date - (MM/DD/YYYY) | | Y | | DiscountAmount | Amount of discount, if any, applied to the total order | Decimal (10) | |   | | PromotionCode | User-defined code representing a promotion applied to an order | Text (100) | | N | | ModifiedTimestamp | This value includes the date that the record last updated. This value allows for efficiencies when updating Audience Builder. | Date - (MM/DD/YYYY) | | Y | ## Standard Order Line Item Data Extension Use this Data Extension as a line item repository for items associated with an order via the STD\_ORDER\_HEADER data extension.
Related Dimension Packages
  • Products Purchased by Product Name (EVER)
  • Products Purchased by Date
  • Products Purchased by Product Name Last 30, 60, & 90 Days
Data Extension Configuration
Data Extension Name STD_ORDER_LINE_ITEM
Description
## STD\_ORDER\_LINE\_ITEM This data extension includes eCommerce individual records contained within an order.
Field Name Description & Comments Data Type PK Req
OrderHeaderId This value includes a foreign key to the STD_ORDER_HEADER data extension. This value relates individual line items to a given order. TEXT (100) Y Y
ProductID This value includes a foreign key to the STD_PRODUCT_CATALOG_3LEVEL data extension. We use the related data contained within the Product Catalog to build product-specific purchase dimension packages. TEXT (100) Y
OrderLineItemNumber This value includes the line item of the Order Header for this product. The OrderLineItemNumber and the OrderHeaderID make-up the composite key for this table Number Y Y
SubscriberKey   TEXT (100) Y
LineItemAmount This value includes the total amount for this line item. Although required, we don’t use this value in dimension packages. Decimal (10) Y

LineItemDiscountAmount

This value includes the Discount applied, if any, for this line item.

 Decimal (10) N
ModifiedTimeStamp This value includes the date that the record was last updated. This value allows for efficiencies when updating Audience Builder. Date - (MM/DD/YYYY) Y
## STD\_STORE Standard Store Data Extension This data extension stores metadata. | Field Name | Description and Comments | Data Type | Primary Key | Required | | --- | --- | --- | --- | --- | | StoreID | The store identifier, used in the STD\_ORDER\_HEADER data source | Text (100) | Y | Y | | StoreName | The name of the store | Text (200) | | Y | | StoreAddressLine1 | The address of the store | Text (200) | | N | | StoreCity | The city of the store | Text (100) | | N | | StoreState | The state of the store | Text (100) | | N | | StoreZipCode | The ZIP or Postal code of the store | Text (20) | | N | | StoreRegion | The region of the store | Text (200) | | N | ## Standard Product Catalog 3-Level Data Extension Use this data extension as the master product catalog for all items designated as a product in the STD\_ORDER\_LINE\_ITEM data source. The data contained in this Data Extension relates to purchase records to enrich that data with metadata and add value to your implementation.
Related Dimension Packages
  • Products Purchased by Product Name (EVER)
  • Products Purchased by Date
  • Products Purchased by Days
  • Products Purchased by Product Name
  • Last 30, 60, & 90 Days
  • Products Purchased by Product SKU
  • Products Purchased by Product SKU Last 30, 60, & 90 Days
  • Products Purchased By Product Hierarchy Level 1, 2, & 3
STD\_PRODUCT\_CATALOG\_3LEVEL This data extension contains product catalog data up to three levels deep: ``` (Parent Category (level 1) > Sub Category1 (level 2)> Sub category2 (level 3)> Product) ``` Assume this structure for these levels: ``` Clothing > Mens > Outer Wear > [ITEM] ``` | Field Name | Description and Comments | Data Type | PK | Req | | --- | --- | --- | --- | --- | | ProductID | Product ID | Text (100) | Y | Y | | SKU | Product SKU | Text (100) | Y | Y | |   | Description of the product – the human-readable name of your product | Text (200) | | Y | | ProductLevel1Id | ID of product root level | Text (100) | | Y | | ProductLevel1Description | Description of root level | Text (200) | | Y | |   | ID of product level 2 | Text (100) | | N | | ProductLevel2Description | Description of level 2 | Text (200) | | N | | ProductLevel3Id | ID of product level 3 | Text (100) | | N | | ProductLevel3Description | Description of level 3 | Text (200) | | N | | ProductUnitPrice | Selling price of the product | Decimal | | N | | ProductCost | Cost of the product | Decimal | | N | ## Hierarchical Dimension Packages Example The related hierarchical dimension packages, including those dimension packages using the term …By Product Hierarchy in their names, rely on these listed ProductLevel IDs. Choose whether you use one, two, or three levels of product hierarchy, and use it with all your products. For example, if you sell shoes and you have three levels to your men's lines of shoes, your product catalog items for men’s shoes looks like this data. | Level 1 | Level 2 | Level 3 | Product | | --- | --- | --- | --- | | Mens | Shoes | Running | \[products…\] | | Mens | Shoes | Dress | \[products…\] | If your children’s line of shoes only has two levels, your product catalog items for children’s shoes looks like this data. | Level 1 | Level 2 | Level 3 | Product | | --- | --- | --- | --- | | Childrens | Shoes | null | \[products…\] | | Childrens | Shoes | null | \[products…\] | Modify your three-level products to fit into two levels or modify your two-level products to fit into three levels:
Level 1 Level 2 Level 3 Product
Mens Running Shoes null [products…]
or
Childrens Boys Shoes [products…]