How to implement a recommender system for a tools ecommerce store with limited user data? #2162
Replies: 1 comment
-
What you describe is very common, if you plot the distribution of popularity, you get a very long tail. There are two main approaches to recommend items that I will present with two over-simplified examples:
If you have lot of data on the items, you should go on the content-based approach. You can also combine both approaches in hybrid systems or use two recommenders and display them one on top of another in the web ui. In your case, where you don't have a lot of data from each user and it is stored in local storage, you can check out session-based recommender systems, which focus on recommending the "next item". Personally, I'd recommend you to try a couple models with the offline dataset, to check what works better. About the collecting more data part, you can use not only the history of reviewed products (explicit feedback) but the history of clicked/wishlisted/bought products (implicit feedback) to generate the recommendations. |
Beta Was this translation helpful? Give feedback.
-
I have an ecommerce site in the tools industry with about 60k products, but only a small percentage have reviews. We get around 5k visits per day, mostly from users who are not logged in, and we save the history of reviewed products in local storage. Given these constraints, what are the best approaches to implement a recommender system focused on product recommendations? Should I consider changing my infrastructure to collect more user data, and if so, how?
Beta Was this translation helpful? Give feedback.
All reactions