Boosting - Lucidworks documentation

Signals contain data about how users interact with search results. Once your Fusion app has accumulated a sufficient number of aggregated signals, they become useful for automatically producing recommendations and boosts for better relevance and higher conversion rates. The same data used to produce recommendations can also be used for automatic boosting. So although recommendations and boosts are different (as explained below), these topics use “recommender data” to refer to the data that can be used for boosting as well as for recommendations.

Recommendations vs boosts

Recommendations and boosts are two ways of presenting AI-powered estimations about which items are most likely to interest a user:

Recommendations	Boosts
Personalized search results from a special, automatic query, whether or not the user has performed a query. Recommendations can be based on a variety of criteria, as in the examples below: • “Based on your purchase history, you might be interested in these items.” • “People who viewed this item also viewed these items.” • “People who searched for ‘ipad’ also searched for these items.”	Modifications to the scores of the items in a query’s search results. The set of search results does not change, but their ranking does. For example: • Boost the most popular items • Boost items this user has clicked before • Boost seasonal items Boosts can also be configured manually, using the Query Workbench or the Query Rewriting UI . You can also perform boosts within a set of recommendations.

These topics explain how to configure and use recommendations and boosts:

Getting Started shows you how to quickly enable the basic feature set and see some results.
Recommendation Methods explains the available approaches to recommendations and boosting, including methods that do not rely on signals.

​Recommendations vs boosts

​See also

Recommendations vs boosts

See also