蜜豆视频

Events

Events are a critical tool to enhance the shopping experience and drive conversions by leveraging real-time data insights.

蜜豆视频 Commerce Optimizer deploys storefront events to your site automatically. These events capture data from shoppers鈥 interactions on your site. This anonymized data powers recommendations, product discovery, and success metrics.

NOTE
Data collection does not include personally identifiable information (PII). All user identifiers, such as cookie IDs and IP addresses, are strictly anonymized. .

The Events page lets you observe the storefront event data being collected. Having a view into the event data collection lets merchants verify that they have implemented storefront events correctly and that events are being successfully captured. Merchants can use this page to identify potential problems and take steps to resolve any event issues.

Event Count

The Event Counts tab tracks shopper interactions, such as searches, clicks, and purchases, to help you analyze trends and improve the shopping experience.

Event Counts {modal="regular"}

Field
Description
Date range
Let鈥檚 you specify the date range to see a specific subset of data.
Storefront events per hour
Displays a graph of showing the number of events triggered on your storefront.
Total storefront events
A filterable table that shows details for all events triggered on your storefront.

Sanity Check

The Sanity Check tab offers insights into the health of each behavioral event, ensuring accurate data collection and functionality. 鈥

Sanity Check {modal="regular"}

Field
Description
Date range
Let鈥檚 you specify the date range to see a specific subset of data.
Product discovery
Displays the required events to personalize product search results. The Status column indicates if the events were received.
Recommendations
Displays the required events to personalize product recommendations. The Status column indicates if the events were received.

The following sections describe event details for product discovery and recommendations.

Product discovery

Product discovery uses events to power search algorithms such as 鈥淢ost Viewed鈥, and 鈥淰iewed This, Viewed That鈥.

This table describes the events used by product discovery ranking strategies.

Ranking Strategy
Events
Page
Most Viewed
page-view
product-view
Product detail page
Most Purchased
page-view
place-order
Cart/Checkout
Most added to cart
page-view
add-to-cart
Product detail page
Product listing page
Cart
Wish List
Viewed this, viewed that
page-view
product-view
Product detail page

Required dashboard events

Some events are required to populate the search performance dashboard

Dashboard area
Events
Join field
Unique searches
page-view, search-request-sent, search-response-received
searchRequestId
Zero results searches
page-view, search-request-sent, search-response-received
searchRequestId

Recommendations

There are two types of data used in recommendations:

  • Behavioral - Data from a shopper鈥檚 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.

蜜豆视频 Sensei aggregates the behavioral and catalog data, creating Recommendations for each recommendation type. The 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 Recommendations on your site, you can use the More like this recommendation type.

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 recommendations, this means waiting for 蜜豆视频 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鈥檚 best to start this process early.

The following table provides some general guidance for the amount of time that it takes to collect enough data for each recommendation type:

Recommendation type
Training Time
Notes
Popularity-based (Most viewed, Most purchased, Most added to cart)
Varies
Depends on volume of events - views are most common, and therefore learns faster; then adds to cart, then purchases
Viewed this, viewed that
Requires more training
Product views are decently high in volume
Viewed this, bought that, Bought this, bought that
Requires the most training
Purchase events are the most rare events on a commerce site, especially compared to product views
Trending
Requires three days of data to establish a popularity baseline
Trending is a measure of recent momentum in a product鈥檚 popularity compared with its own popularity baseline. A product鈥檚 trending score is computed using a foreground set (recent popularity over 24 hours) and a background set (popularity baseline over 72 hours). If the popularity of an item increases significantly within a 24 hour period as compared with its baseline popularity, then it receives a high trending score. Every product has this score, and the items with the highes score at any time comprise the set of top trending products.

Other variables that can impact the time needed to train:

  • Higher traffic volume contributes to faster learning
  • Some recommendation types train faster than others
  • 蜜豆视频 Commerce Optimizer 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鈥檙e 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鈥檛 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 on the Recommendations workspace 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

If the input data is insufficient for providing all requested recommendation items in a unit, 蜜豆视频 Commerce Optimizer 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, 蜜豆视频 Commerce Optimizer 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)

Recommendation-specific events

The following table lists the events that are triggered when shoppers interact with recommendation units on the storefront. The event data collected powers the metrics to analyze how well your recommendations are performing.

Event
Description
impression-render
Sent when the recommendation unit is rendered on the page. If a page has two recommendation units (bought-bought, view-view), then two impression-render events are sent. This event is used to track the metric for impressions.
rec-add-to-cart-click
The shopper clicks the Add to cart button for an item in the recommendation unit.
rec-click
The shopper clicks a product in the recommendation unit.
view
Sent when the recommendation unit becomes at least 50 percent viewable, such as by scrolling down the page. For example, if a recommendation unit has two lines, a 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 Recommendations Performance dashboard

Dashboard column
Events
Join field
Impressions
page-view, recs-request-sent, recs-response-received, recs-unit-render
unitId
Views
page-view, recs-request-sent, recs-response-received, recs-unit-render, recs-unit-view
unitId
Clicks
page-view, recs-request-sent, recs-response-received, recs-item-click, recs-add-to-cart-click
unitId
Revenue
page-view, recs-request-sent, recs-response-received, recs-item-click, recs-add-to-cart-click, place-order
unitId, sku, parentSku
LT Revenue
page-view, recs-request-sent, recs-response-received, recs-item-click, recs-add-to-cart-click, place-order
unitId, sku, parentSku
CTR
page-view, recs-request-sent, recs-response-received, recs-unit-render, recs-item-click, recs-add-to-cart-click
unitId, sku, parentSku
vCTR
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 Recommendations, but are required for 蜜豆视频 Sensei to interpret shopper data correctly:

  • view
  • add-to-cart
  • place-order

Recommendation Type

This table describes the events used by each recommendation type.

Recommendation Type
Events
Page
Most Viewed
page-view
product-view
Product detail page
Most Purchased
page-view
place-order
Cart/Checkout
Most added to cart
page-view
add-to-cart
Product detail page
Product listing page
Cart
Wish List
Viewed this, viewed that
page-view
product-view
Product detail page
Viewed this, bought that
page-view
product-view
Product detail page
Cart/Checkout
Bought this, bought that
page-view
product-view
Product detail page
Trending
page-view
product-view
Product detail page
Conversion: View to purchase
page-view
product-view
Product detail page
Conversion: View to purchase
page-view
place-order
Cart/Checkout
Conversion: View to cart
page-view
product-view
Product detail page
Conversion: View to cart
page-view
add-to-cart
Product detail page
Product listing page
Cart
Wishlist

Support

If you notice any data discrepancies or if recommendations and search results are not working as expected, submit a support ticket.

recommendation-more-help
0c009cf6-d957-4a6a-b642-3577df53e8cb