---
schema_version: "1"
id: fbff74c5bd1d04fae7031f2bdf53c3ba3a5322aea85ae872f0ab6d73814172da
title: Web Analytics Dimension Package Technical Specifications
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mc_ab_web_analytics_package_technical_specifications.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mc_ab_web_analytics_package_technical_specifications.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 8fbfd858d2baaf9ee45bac923637a58d9b020423bd47cfde421a1d7ec6cb25c9
description: The Web Analytics Dimension Package Set includes standard dimension packages derived from a standardized data extension–based data model. It brings web analytics data into Audience Builder without needing custom implementation.
products:
  - Marketing
  - Marketing Cloud Engagement
release: "264"
---
# Web Analytics Dimension Package Technical Specifications

The Web Analytics Dimension Package Set includes standard dimension packages derived from a standardized data extension–based data model. It brings web analytics data into Audience Builder without needing custom implementation.

The Audience Builder Web Analytics Dimension Package Set contains these components.

- Data extension templates in Email Studio
- Dimension package set in Audience Builder

These data extensions are required. Review the fields and details in the tables.

- Standard Page Browse data extension
- Standard Cart Abandon data extension
- Standard Product Purchase data extension
- Standard Product Catalog 3-Level data extension

## Standard Page Browse Data Extension

This data extension acts as a universal page or product browse event repository. While some analytics providers separate this information into two or more output files, we chose to merge them for the sake of simplicity. For ProductID values, we perform a lookup on the Product Catalog Data Extension (STD\_PRODUCT\_CATALOG\_3LEVEL) and use the related product data to populate various dimension packages with the related Product Data.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="vertical-align:top;" id="d2496e77">Related Dimension Packages</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Related Dimension Packages" class="slds-cell-wrap" style="vertical-align:top;" headers="d2496e77 ">
              <ul>
                <li>Products Browsed By SKU</li>

                <li>Product Browse Count By Days</li>

                <li>Products Browsed By Date</li>

                <li>Products Browsed By Days</li>

                <li>Products Browsed By Hierarchy</li>

                <li>Products Browsed By Name</li>

              </ul>
            </td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d2496e77 ">
              <ul>
                <li>Page Browse Count By Days</li>

                <li>Page Category Count By Days</li>

                <li>Categories Browsed By Days</li>

                <li>Categories Browsed By Name</li>

                <li>Pages Browsed By Date</li>

                <li>Pages Browsed By Days</li>

                <li>Pages Browsed By Name</li>

              </ul>
            </td>

          </tr>
        </tbody>
      </table>

## STD\_PAGE\_BROWSE

    
| 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 |
| BrowseDate | Date of browse event | Date - MM/DD/YYYY | Y | Y |
| PageName | Typically the page title or product name browsed | Text (200) | Y | Y |
| PageCategory | Optional page category as supported by some web analytics providers | Text (200) |  | N |
| ProductID | This value includes the foreign key to the STD\_PRODUCT\_CATALOG\_3LEVEL data extension. When using the ProductID value, we use the related data contained within the Product Catalog to build product-specific browse dimension packages. | Text (100) |  | N |

## Standard Cart Abandon Data Extension

This data extension acts as an abandoned cart event repository.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="vertical-align:top;" id="d2496e304">Related Dimension Packages</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Related Dimension Packages" class="slds-cell-wrap" style="vertical-align:top;" headers="d2496e304 ">
              <ul>
                <li>Abandon By Product Hierarchy</li>

                <li>Abandon By Product Name</li>

                <li>Abandon By Product SKU</li>

                <li>Abandon Date</li>

                <li>Abandon Days</li>

              </ul>
            </td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d2496e304 "> </td>

          </tr>
        </tbody>
      </table>

## STD\_CART\_ABANDON

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:14.285714285714285%">
          <col style="width:14.285714285714285%">
          <col style="width:14.285714285714285%">
          <col style="width:14.285714285714285%">
          <col style="width:14.285714285714285%">
          <col style="width:14.285714285714285%">
          <col style="width:14.285714285714285%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d2496e370">Field Name</th>
            <th scope="colgroup" class="slds-cell-wrap" colspan="3" style="vertical-align:top;" id="d2496e373">Description and Comments</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d2496e376">Data Type</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d2496e379">Primary Key</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d2496e382">Required</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Field Name" class="slds-cell-wrap" colspan="2" style="vertical-align:top;" headers="d2496e370 d2496e373 ">SubscriberKey</td>

            <td data-label="Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d2496e373 ">
              <span>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.</span>
            </td>

            <td data-label="Primary Key" class="slds-cell-wrap" style="vertical-align:top;" headers="d2496e373 ">Text (100)</td>

            <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d2496e376 ">Y</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d2496e379 ">Y</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d2496e382 ">&nbsp;</td>

          </tr>
          <tr class="">
            <td data-label="Field Name" class="slds-cell-wrap" colspan="2" style="vertical-align:top;" headers="d2496e370 d2496e373 ">AbandonDate</td>

            <td data-label="Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d2496e373 ">Date of abandon event</td>

            <td data-label="Primary Key" class="slds-cell-wrap" style="vertical-align:top;" headers="d2496e373 ">Date - MM/DD/YYYY</td>

            <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d2496e376 ">Y</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d2496e379 ">Y</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d2496e382 ">&nbsp;</td>

          </tr>
          <tr class="">
            <td data-label="Field Name" class="slds-cell-wrap" colspan="2" style="vertical-align:top;" headers="d2496e370 d2496e373 ">ProductID</td>

            <td data-label="Data Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d2496e373 ">This value includes the foreign key to the
              STD_PRODUCT_CATALOG_3LEVEL data extension. When using the ProductID
              value, we use the related data contained within the Product Catalog
              to build product-specific browse dimension packages.</td>

            <td data-label="Primary Key" class="slds-cell-wrap" style="vertical-align:top;" headers="d2496e373 ">Text (100)</td>

            <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d2496e376 ">&nbsp;</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d2496e379 ">Y</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d2496e382 ">&nbsp;</td>

          </tr>
        </tbody>
      </table>

## Standard Product Purchase Data Extension

This data extension acts as a product purchase event repository.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="vertical-align:top;" id="d2496e479">Related Dimension Packages</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Related Dimension Packages" class="slds-cell-wrap" style="vertical-align:top;" headers="d2496e479 ">
              <ul>
                <li>Purchase By Product SKU</li>

                <li>Purchases By Date</li>

                <li>Purchases By Days</li>

                <li>Purchases By Product </li>

                <li>Hierarchy</li>

                <li>Purchases By Product Name</li>

              </ul>
            </td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d2496e479 "> </td>

          </tr>
        </tbody>
      </table>

## STD\_PRODUCT\_PURCHASE

    
| 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 |
| PurchaseDate | Date of purchase event | Date - MM/DD/YYYY | Y | Y |
| ProductID | This value includes the foreign key to the STD\_PRODUCT\_CATALOG\_3LEVEL data extension. When using the ProductID value, we use the related data contained within the Product Catalog to build product-specific browse dimension packages. | Text (100) | Y | Y |

## Standard Product Catalog 3-Level Data Extension

This data extension acts as the primary product catalog for all items designated as a product on a website. The data contained in this data extension relates to browse, purchase, and abandon events to enrich that event data with metadata to add value to your implementation.

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 the following structure for levels one through three.

```
Clothing > Mens > Outer Wear > [ITEM]
```

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="vertical-align:top;" id="d2496e658">Related Dimension Packages</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Related Dimension Packages" class="slds-cell-wrap" style="vertical-align:top;" headers="d2496e658 ">
              <ul>
                <li>Cart Abandonment<ul>
                    <li>Abandon By Product Hierarchy</li>
                    <li>Abandon By Product Name</li>
                    <li>Abandon By Product SKU</li>
                  </ul>
                </li>

              </ul>
              <ul>
                <li>Products Browsed<ul>
                    <li>Products Browsed By SKU</li>
                    <li>Product Browse Count By Days</li>
                    <li>Product Browse Count By Hierarchy</li>
                    <li>Products Browsed By Name</li>
                  </ul>
                </li>

              </ul>
            </td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d2496e658 ">
              <ul>
                <li>Purchases<ul>
                    <li>Purchase By Product SKU</li>
                    <li>Purchases By Product Hierarchy</li>
                    <li>Purchases By Product Name</li>
                  </ul>
                </li>

              </ul>
            </td>

          </tr>
        </tbody>
      </table>

## STD\_PRODUCT\_CATALOG\_3LEVEL

    
| Field Name | Description and Comments | Data Type | Primary Key | Required |
| --- | --- | --- | --- | --- |
| ProductID | Product ID | Text (100) | Y | Y |
| SKU | Product SKU | Text (100) | Y | Y |
| ProductDescription | Description of the product – the human-readable name of your product | Text (200) |  | Y |
| ProductLevel1Id | ID of product root level | Text (100) |  | Y |
| ProductLevel1Description | Text (200) |  | Y |   |
| ProductLevel2Id | 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 adhere to that number of levels with your products.

For example, if you sell shoes and you have three levels for men’s shoes, your product catalog items for men’s shoes can look like this.

   
| 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.

   
| 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.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:25%">
          <col style="width:25%">
          <col style="width:25%">
          <col style="width:25%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d2496e1130">Level 1</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d2496e1133">Level 2</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d2496e1136">Level 3</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d2496e1139">Product</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Level 1" class="slds-cell-wrap" style="vertical-align:top;" headers="d2496e1130 ">Mens</td>

            <td data-label="Level 2" class="slds-cell-wrap" style="vertical-align:top;" headers="d2496e1133 ">Running Shoes</td>

            <td data-label="Level 3" class="slds-cell-wrap" style="vertical-align:top;" headers="d2496e1136 ">null</td>

            <td data-label="Product" class="slds-cell-wrap" style="vertical-align:top;" headers="d2496e1139 ">[products…]</td>

          </tr>
          <tr class="">
            <td class="slds-cell-wrap" colspan="4" style="vertical-align:top;" headers="d2496e1130 d2496e1133 d2496e1136 d2496e1139 ">or</td>

          </tr>
          <tr class="">
            <td data-label="Level 1" class="slds-cell-wrap" style="vertical-align:top;" headers="d2496e1130 ">Children’s</td>

            <td data-label="Level 2" class="slds-cell-wrap" style="vertical-align:top;" headers="d2496e1133 ">Boys</td>

            <td data-label="Level 3" class="slds-cell-wrap" style="vertical-align:top;" headers="d2496e1136 ">Shoes</td>

            <td data-label="Product" class="slds-cell-wrap" style="vertical-align:top;" headers="d2496e1139 ">[products…]</td>

          </tr>
        </tbody>
      </table>

## Data Model

![Data Model for eCommerce Dimension Package](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-mktg-mc_contact_data-264-0-0-production-enus/0e4d875c-8c8c-4be4-8f13-c8278eafbbf9/mc_contact_data/images/DataModel.png)