Omnichannel Personalized Search Action Request

here is an example of an engine api request for an omnichannel personalized search action see calling the personalized search api for full details about personalized search requests example omnichannel personalized search action request { "channel" "a 424w1216/p/example com", "events" \[ { "eventtype" "monetate\ decision\ decisionrequest", "requestid" "12345" } ] } the response to this request appears much like the following example example omnichannel personalized search action response { "meta" { "code" 200, "monetateid" "5 1290581234 1733503404082" }, "data" { "responses" \[ { "requestid" "12345", "actions" \[ { "actionevents" \[ "op click", "op impression" ], "actionid" {action id}, "searchtoken" "{searchtoken}", "actiontype" "monetate\ action\ sitesearchapiaction" } ] } ] } } recommendation strategies and context events the configuration of the recommendation strategy selected in the personalized search action may require you to send certain context events in the request if the selected recommendation strategy is configured with the viewed and also viewed or other collaborative recommendation algorithms , then 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 model monetate\ context\ productdetailview or model monetate\ context\ productthumbnailview first item viewed on current page model monetate\ context\ productdetailview or model monetate\ context\ productthumbnailview 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 model monetate\ context\ 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 model monetate\ context\ customvariables see user identity persistence in requests for more information about passing unique identifiers for customers in engine api requests example request here is an example of an engine api request for an omnichannel personalized search action that's configured with a recommendation strategy powered by the purchased and also purchased recommendation algorithm and with item(s) viewed on current page selected for base recommendation on example omnichannel personalized search action response { "channel" "a 12345/p/example com", "events" \[ { "eventtype" "monetate\ decision\ decisionrequest", "requestid" "12345" }, { "eventtype" "monetate\ context\ productdetailview", "products" \[ { "productid" "{pid}", "sku" "{sku}" } ] } ] }