Personalization cannot work for users with no behavioral data. Your app should be sending events in real time to the EventServer. That way the events below will already be in HBase. Then you just query with the user-id. Item-sets are meant for shopping carts, not events that you know about but have not been sent to the EventServer yet. If you know them on your side of the app—send them immediately to the EventServer, this will work to give results based on real time events.
If there truly are no events for a user, the below method has nothing to send and so the UR will fall back to use popular items in recommendations. Item-based recs work fine since there is only some contextual info in the query like the item that is being looked at on-site. Getting real time context and events is be the best way to use the system, in which case no special query is needed. On Jul 17, 2017, at 9:36 AM, Cody Kimball <[email protected]> wrote: I am using the Universal Recommender, and I have a use case where I would need to query for a given user (as if that user had performed certain events, but technically hasn't yet, meaning the event data hasn't been pushed into the Event Store). I originally thought this would be accomplished via itemSets, but the documentation seems to suggest otherwise. My hope is to be able to pass a list of events with the query, without those events technically existing yet (nor will be created as a result of the query), and getting a different result set as a result. An example payload may be: { "user": "userID123", "eventList": [{"event":"view", "targetEntityType":"item", "targetEntityId";"targetID15"}, {"event":"view", "targetEntityType":"item", "targetEntityId";"targetID23"}, {"event":"interaction", "targetEntityType":"item", "targetEntityId";"targetID23"}] } -- Cody Kimball Revenue Engineer Don't Just Keep Up With Technology. Master It! <https://www.pluralsight.com/>
