
The main advantage for us was being able to add personalized product recommendations without having to build and maintain the entire recommendation pipeline ourselves. We used our product catalog together with user interaction events such as product views, searches, add-to-cart events, and purchases. We mainly used the personalized recommendations on the homepage and product pages.
The integration with our backend was also convenient because our application could request recommendations for a particular user and use the returned products directly in the UI. This allowed us to focus on the application logic and user experience rather than implementing the recommendation model ourselves. Review collected by and hosted on G2.com.
The main difficulty was the initial data preparation and configuration. Getting the product catalog and user-event data into the expected structure required some work, and recommendation quality depended heavily on having enough clean behavioral data.
We also noticed that users with very little interaction history had less personalized recommendations. As more behavioral data became available, the recommendations became more relevant to the user's activity.
From the application side, the recommendations were straightforward to integrate into the existing UI, and we could present them as normal product sections without requiring a separate interface. In our testing, performance was adequate for the application, although recommendation relevance was more important to us than small differences in response time.
The initial setup also required some learning around the catalog, events, and configuration. The documentation helped us work through that process. From a value perspective, the main benefit was avoiding the need to build and maintain the complete recommendation infrastructure ourselves. Review collected by and hosted on G2.com.