Collect Data
When you install and configure SaaS-based Adobe Commerce features such as Product Recommendations or Live Search, the modules deploy behavioral data collection to your storefront. This mechanism collects anonymized behavioral data from your shoppers and powers product recommendations and Live Search results. For example, the view
event is used to compute the Viewed this, viewed that
recommendation type, and the place-order
event is used to compute the Bought this, bought that
recommendation type.
Data types and events
There are two types of data used in Product Recommendations:
- Behavioral - Data from a shopper’s engagement on your site, such as product views, items added to a cart, and purchases.
- Catalog - Product metadata, such as name, price, availability, and so on.
When you install the magento/product-recommendations
module, Adobe Sensei aggregates the behavioral and catalog data, creating Product Recommendations for each recommendation type. The Product Recommendations service then deploys those recommendations to your storefront in the form of a widget that contains the recommended product items.
Some recommendation types use behavioral data from your shoppers to train machine learning models to build personalized recommendations. Other recommendation types use catalog data only and do not use any behavioral data. If you want to quickly start using Product Recommendations on your site, you can use the following, catalog-only recommendation types:
More like this
Visual similarity
Cold start
When can you start using recommendation types that use behavioral data? It depends. This is referred to as the Cold Start problem.
The Cold Start problem refers to the time it takes for a model to train and become effective. For product recommendations, this means waiting for Adobe Sensei to gather enough data to train its machine learning models before deploying recommendation units on your site. The more data the models have, the more accurate and useful the recommendations are. Since data collection happens on a live site, it’s best to start this process early by installing and setting up the magento/production-recommendations
module.
The following table provides some general guidance for the amount of time that it takes to collect enough data for each recommendation type:
Most viewed
, Most purchased
, Most added to cart
)Viewed this, viewed that
Viewed this, bought that
, Bought this, bought that
Trending
Other variables that can impact the time needed to train:
- Higher traffic volume contributes to faster learning
- Some recommendation types train faster than others
- Adobe Commerce recomputes behavioral data every four hours. Recommendations become more accurate the longer they are used on your site.
To help you visualize the training progress of each recommendation type, the create recommendation page displays readiness indicators.
While data is being collected on your live site and the machine learning models are training, you can finish other testing and configuration tasks needed to set up recommendations. By the time you’re done with this work, the models will have enough data to create useful recommendations, allowing you to deploy them to your storefront.
If your site doesn’t get enough traffic (views, purchases, trends) for most product SKUs, there might not be enough data to complete the learning process. This can make the readiness indicator in the Admin seem stuck. The readiness indicators are meant to provide merchants with another data point in choosing what recommendations type is better for their store. The numbers are a guide and may never reach 100%. Learn more about readiness indicators.
Backup recommendations backuprecs
If the input data is insufficient for providing all requested recommendation items in a unit, Adobe Commerce provides backup recommendations to populate recommendation units. For example, if you deploy the Recommended for you
recommendation type to your homepage, a first-time shopper on your site has not generated enough behavioral data to accurately recommended personalized products. In this case, Adobe Commerce surfaces items based on the Most viewed
recommendation type to this shopper.
In the case of insufficient input data collection, the following recommendation types fallback to Most viewed
recommendation type:
Recommended for you
Viewed this, viewed that
Viewed this, bought that
Bought this, bought that
Trending
Conversion (view to purchase)
Conversion (view to cart)
Events
The Adobe Commerce Storefront Event Collector lists all the events deployed to your storefront. From that list, however, there is a subset of events specific to Product Recommendations. These events collect data when shoppers interact with recommendation units on the storefront and power the metrics used to help you analyze how well your recommendations are performing.
impression-render
impression-render
events are sent. This event is used to track the metric for impressions.rec-add-to-cart-click
rec-click
view
view
event is sent when one line plus one pixel of the second line becomes visible to the shopper. If the shopper scrolls the page up and down several times, the view
event is sent as many times as the shopper sees the whole recommendation unit again on the page.Required dashboard events
The following events are required to populate the Product Recommendations dashboard
page-view
, recs-request-sent
, recs-response-received
, recs-unit-render
unitId
page-view
, recs-request-sent
, recs-response-received
, recs-unit-render
, recs-unit-view
unitId
page-view
, recs-request-sent
, recs-response-received
, recs-item-click
, recs-add-to-cart-click
unitId
page-view
, recs-request-sent
, recs-response-received
, recs-item-click
, recs-add-to-cart-click
, place-order
unitId
, sku
, parentSku
page-view
, recs-request-sent
, recs-response-received
, recs-item-click
, recs-add-to-cart-click
, place-order
unitId
, sku
, parentSku
page-view
, recs-request-sent
, recs-response-received
, recs-unit-render
, recs-item-click
, recs-add-to-cart-click
unitId
, sku
, parentSku
page-view
, recs-request-sent
, recs-response-received
, recs-unit-render
, recs-unit-view
, recs-item-click
, recs-add-to-cart-click
unitId
, sku
, parentSku
The following events are not specific to Product Recommendations, but are required for Adobe Sensei to interpret shopper data correctly:
view
add-to-cart
place-order
Recommendation Type
This table describes the events used by each recommendation type.
page-view
product-view
page-view
complete-checkout
page-view
add-to-cart
Product listing page
Cart
Wish List
page-view
product-view
page-view
product-view
page-view
product-view
page-view
product-view
page-view
product-view
page-view
complete-checkout
page-view
product-view
page-view
add-to-cart
Caveats
- Ad blockers and privacy settings can prevent events from being captured and might cause the engagement and revenue metrics to be under-reported. Additionally, some events might not be sent due to shoppers leaving the page or network issues.
- Headless implementations must implement eventing to power the Product Recommendations dashboard.
- For configurable products, Product Recommendations use the image of the parent product in the recommendation unit. If the configurable product does not have an image specified, the recommendation unit will be empty for that specific product.