Meet Recombee at IBC 2023 Amsterdam · 15–18 September 2023 · Read More
Frequently Asked Questions

Explore the Most Asked Questions

A recommender system is a technology that is deployed in the environment where items (products, movies, events, articles) are to be recommended to users (customers, visitors, app users, readers) or the opposite. Typically, there are many items and many users present in the environment making the problem hard and expensive to solve.

Check our blog post explaining the topic in further detail here.

By default, content-based models (text processing, image processing, and other types of meta-data) are turned for the cold start user or item with no prior interactions. As soon there is at least one interaction from the user or with the item, personalized models start to being used. This way our solution seamlessly tackles the cold-start problem.

Yes. We maintain a priority list of new features based on customer suggestions. We are quite strong in research, innovations, and inventing new functionality is our passion. Check out our articles on the Recombee blog to find out more about recently launched inverse recommendations and other features.

Yes. Definitely.

Anonymous users are very important and Recombee is built to learn from them and adapt in real-time as they make interactions. You can use whatever unique identifier for userID, such as the session ID, or GA clientID. You can learn more here.

We never share data with third parties, neither we share data between individual clients (there is no cross-database data enrichment).

It’s fine to have missing fields if the items do not have such properties by their nature. These items should be still recommendable.

Yes, they do. Recombee solution is composed of a mixture of models, including collaborative filtering and content-based models. While collaborative filtering has a higher weight/priority, some of the recommendations are generated with the help of the content-based models (based on the item and user properties).

Collaborative filtering algorithms are used when a large portion of the items is covered with interactions (having at least tens of interactions).

Tracking users is up to you. We only require a unique string ID for each of the users. Please note, Recombee is fully GDPR compliant.

Besides item properties and user interactions, user properties can be also used for producing recommendations. Sending user properties is optional. User properties are used mainly for new (cold-start) users without any previous interactions. When the user has interactions, the results produced by more sophisticated collaborative filtering models are preferred as they usually have better performance.

Yes, we have functionality using the logic parameter for the recommendation endpoints in our API. You can use logic=recombee:popular for this. See more here.

If you have some items that you wish to recommend with less probability return e.g. 0.3 for them while you return 1 for the others in the booster.

The minimum is 0 and the maximum is not exactly defined, but the greater number the booster returns, the greater the boost is. You can test which constants work the best according to your preferences.

Unlimited. :) In the Free Plan, the maximum amount of databases you can have is two. If you’d like to have more, we would recommend upgrading your plan.

You can erase all the contents by using the Reset Database option in the settings section of your database in the Admin UI.

Our standard pricing is purely usage-based. All plans are pay-as-go plans - you never pay more than you use.

The Standard account starts at $99/mth -- you'll get separate instance on our enterprise infrastructure with high availability guarantees, and also API integration support.

The price list consists of three components: a number of active users, recommendation requests, and items in your catalog. When properly integrated, the number of active users is roughly equivalent to the number of users you can find in Google Analytics for a given period of 1 month. For the Recommendation requests, only the number of invoked requests counts, no matter the number of returned items per request.

In Recombee a user is counted as active only if there was at least one recommendation request or interaction (view, purchase, etc.) within the period of one month generated for the user.

When your trial expires, your account will be automatically downgraded to a Free Plan. You don’t need to do anything. You can always upgrade when needed.

In a Free Plan, you will get up to 20,000 Active Users and up to 100,000 recommendation requests per month. Please note that the Free Plan option does not contain any support, guarantees nor SLAs.

If you plan to put a Recombee solution to production, we strongly advise you to upgrade to our Standard Plan.

For more info visit this link.

You will receive the invoice one month after the day you upgrade. For e.g. if you upgrade on November 16, you will receive the invoice on December 16th. Recombee charges its clients for the services provided in the previous month/period, thus the invoice is sent after a month’s usage.

Yes, you will still need to pay for the services, despite not using Recombee’s services for a full month. When a Recombee account is upgraded to a Standard Plan, it is moved to an "upgraded/paid/premium" server which has priority support from our tech team, and guarantees: 99.5% uptime for the recommender, average response time less than 500 milliseconds, and 95% Admin User Interface availability.

The easiest way is:

  1. Start sending interactions (views, cart additions, purchases, bookmarks) to Recombee using Recombee Javascript SDK. Learn more here.
  2. Synchronize your catalog, learn more here.
  3. Show the recommendations on your website via the code which is automatically generated by our HTML widget that is accessible through our Admin UI.

The server-side integration has numerous advantages, such as complete control over sent requests (they are all sent from your own servers) or easy monitoring of the response times and availability.

We have, however, listened to our clients and realized that many portals prefer requesting recommendations directly from a web browser. Understanding our customers’ needs, we introduced a second integration option - integration using a Javascript library. By adding only a few lines of code, this new library allows you to send interactions (clicks, purchases …) to Recombee and request recommendations directly from a web browser or mobile application.

You can invite teammates to your account easily in your Recombee Admin Interface. There is a “Manage Access” button on your “Organization” page. Once you click on it, you can add collaborators and give them specific permissions (what they can or can’t see/do). See more here.

If you already have an existing Google merchant catalog implemented, provided that to Recombee means less work for you. Otherwise, using the API is the preferred way for multiple reasons:

  • Full control of the set of attributes and their data types.
  • Real-time behavior. While product feed is periodically re-fetched, when using the API, as soon as the data update requests are acknowledged, you can be sure they are used by the models, ReQL, etc.

Please see this link to learn how to delete an item from the database.

However, if the item is just not available anymore, you should rather use a ReQL filter and don’t delete the item entirely, in order to keep the data (mainly interactions) associated with the item for the recommendation models.

Hundreds of item properties and dozens of kilobytes of texts per item should be fine.The vast majority of our clients fit into these numbers, but we can always do individual adjustments.

Providing some structured properties (like categories, tags, etc.) is helpful for both the models and possible ReQL filtering/boosting when requesting recommendations, but plaintext properties are fine. We have NLP models capable of processing raw texts.

You can do it easily using our innovative query language ReQL. Each recommendation request has a parameter filter, where you can specify a condition based on the values of the properties. For example, if you have specified a string item property called category and want to get only books, the filter is ‘category’==”books”. You can also do it in your Recombee Admin Interface.

Data Quality Score is just an estimate based mainly on the fact of whether there are interactions with each of your items.

Recommendations can work flawlessly even if the Data Quality Score is not at 100 %.

We use an ensemble of collaborative filtering (matrix factorization, nearest neighbors …) algorithms, which work on the interactions (views, purchases…), and content-based algorithms, which work on the item properties (titles, descriptions…).

The decision about used algorithms is automated - if there is not a lot of interactions (for example in the case of new (cold start) items), content-based algorithms are chosen. In case of a sufficient number of interactions, collaborative filtering algorithms are preferred as they in most cases give the best results. You can learn more here.

In order to get precise success metrics in the Admin UI (how many clicks there were from the recommendations in a particular scenario etc.), it’s good to set optional parameter recommId of the interaction requests whenever the interaction is due to clicking a recommended item. You can learn more here.

Haven't Found The Information You Are Looking For?

Ask us