Omnichannel Recommendations Action Requests
When selecting recommendation strategies for this type of action, be aware of the following conditions related to the recommendation algorithm configured as part of the recommendation strategy:
- When using the Most Viewed (Product Detail Page), Top Selling by Purchase Count, Top Selling by Gross Revenue, or other noncollaborative recommendation algorithm, you don't need to send any product-specific information in the request.
- When using the Viewed and Also Viewed or other collaborative recommendation algorithms, the option selected from Base Recommendation on determines what context events you must include in the request.
The following table contains guidance for which context events you must include in the request when the recommendation strategy uses a collaborative recommendation algorithm, based on the option selected from Base Recommendation on in the strategy configuration.
Base Recommendation on | Event Required |
---|---|
Item(s) viewed on current page | |
First item viewed on current page | |
Last item viewed in any session | No additional events required so long as the customer's unique identifier is associated with a previous completed purchase |
Item(s) viewed in past sessions | No additional events required so long as the customer's unique identifier is associated with a previous completed purchase |
Item(s) currently in the cart | |
Abandoned cart items in past sessions | No additional events required so long as the customer's unique identifier is associated with a previous completed purchase |
Last item carted in any session | No additional events required so long as the customer's unique identifier is associated with a previous completed purchase |
Item(s) purchased in current session | No additional events required so long as the customer's unique identifier is associated with a previous completed purchase |
Item(s) purchased in previous sessions | No additional events required so long as the customer's unique identifier is associated with a previous completed purchase |
Last item purchased in any session | No additional events required so long as the customer's unique identifier is associated with a previous completed purchase |
Item group ID(s) in custom variable |
See User Identity Persistence in Requests for more information about passing unique identifiers for customers in Engine API requests.
This request example is for an Omnichannel recommendations action configured with recommendation strategies that use the Most Viewed (Product Detail Page), Top Selling by Purchase Count, or Top Selling by Gross Revenue recommendation algorithm.
This example is for recommendation strategies that use a collaborative recommendation algorithm with recommendations based on First item viewed on the current page or Item(s) viewed on current page. It includes the monetate:context:ProductDetailView event.
Like the previous example, this one is also for recommendation strategies that use a collaborative recommendation algorithm with recommendations based on First item viewed on the current page or Item(s) viewed on current page. This one, however, includes the monetate:context:ProductThumbnailView event.
This example is for recommendation strategies that use the Viewed and Also Viewed and the Viewed and Later Purchased recommendation algorithms based on the last item purchased in any session.
You must send the product ID of the last purchase.
This example is for recommendation strategies that use the Viewed and Also Viewed and the Viewed and Later Purchased recommendation algorithms based on the last item carted in any session.
You must send the product ID of the last item added to the cart.
If your site uses a hybrid implementation, keep in mind these best practices when configuring an Omnichannel Product Recommendation action:
- You only have to send product IDs if you base recommendations on a specific product (for example, a recommendation strategy configured with the Viewed and Also Viewed recommendation algorithm based on the last item viewed in any session or the first item viewed on the current page).
- monetate:context:ProductDetailView, CartLine, and PurchaseLine events are obtained from the Monetate tag. You're not required to send these.
If your site uses a pure Engine API implementation, keep in mind that you must send all ProductDetailView, cartLine, and purchaseLine events.