Your Adobe Commerce Intelligence Environment

As you analyze your commerce data, be aware of these factors and common misconceptions. If you need assistance with making sure you are using your Commerce schema correctly, do not hesitate to contact support.


Many of your tables contain a column named entity\_id. In each table that contains an entity\_id, that column is used to identify unique rows.

For example, each row in the sales\_order table is a unique order. The primary key in this table is called entity\_id. This column can be thought of as order\_id. In a separate table, customer\_entity, each row represents a unique customer. The primary key in this table is also called entity\_id, which can be thought of as customer\_id.

In those tables, sales\_order.entity\_id does not equal customer\_entity.entity\_id. This holds true for all sets of tables that contain entity\_id: table\_A.entity\_id does not equal table\_B.entity\_id.

Guest orders

If you allow customers to order from your site without having an account (guest orders), those customers do not populate as a row in your customer\_entity table. Also, each order placed by a guest has a null customer\_id value on the sales\_order table.

Therefore, if you wish to track your guests’ behaviors over time, all customer-level columns must be calculated on the sales\_order table, using a customer identifier such as customer\_email.

If you use the sales\_order table as a customer table, you must then be careful when creating customer-level metrics. For example, consider an average lifetime revenue metric. This metric is used to identify the average lifetime revenue across your customer base. This first requires a new column that, for each customer, returns their lifetime revenue. Then you must average this column to obtain your customers’ average lifetime revenue.

If you are able to use the customer\_entity table, each row is a single customer, and each customer only exists in that table one time. Therefore, when you have the lifetime revenue column, all you need is to create an average metric. However, if you use the sales\_order table as your customer table, a customer can potentially exist in numerous rows. After setting up the lifetime revenue column, each order (row) placed by a given customer will show that customer’s lifetime revenue; but you only want to include that customer once in your overall average metric.

The trick here is that you must add a filter to your metric that ensures you only include each customer one time. Adobe encourages you to create and use a filter set named Customers we count that filters for Customer’s order number = 1 (among other filters you may need to exclude unwanted customers). Adding this filter ensures you only include each customer one time in a customer-level metric.

Products and categories

Products can have multiple categories, and categories can be used for more than one product. Therefore, when setting up category-level analyses, you must be careful to use the correct definitions. Do you want the top-level category? Second-level category? What if the product can fall into multiple top-level categories?

Imagine a pair of jeans that falls into three different category levels, as defined by a Commerce implementation: ‘Clothing’ (top level), ‘Outerwear’ (second level), and ‘Pants’ (third level). You might wish to analyze your categories performance by number of units sold. The metric you need for this analysis is Items sold, which is built on the sales\_order\_item table. Therefore, you need to move category-level information onto the items table. Each row on the sales\_order\_item table has an associated product\_id, so if you know the categories associated with a product, you can bring that information over to the desired table.

Before moving any data, you must first know the proper joins and filters to ensure you grab the correct category. For some analyses, you may need to know ‘Pants’, but in other analyses, ‘Clothing’ might be more appropriate. These are distinct categories that are identified separately. Knowing how each category level is defined ensures you are able to attribute unit sales to the appropriate category for your specific analysis.

Now, imagine you also have an Our Favorites top-level category on the home page of your website. Perhaps you have implemented your Commerce store to include these jeans in both the Clothing category and the Our Favorites category. If so, this pair of jeans has more than one top-level category. In that case, moving a single top-level category over to the sales\_order\_item table does not quite make sense, as there are multiple options. To account for this, Adobe suggests creating yes/no columns that check for specific categories. For example, Is product in Clothing category? and Is product in Our Favorites category? columns allow you to check if a product falls into those specific categories.