personalization

personalization

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
personalization [2018/06/05 15:08]
stefan [How to apply boosts]
personalization [2019/05/28 15:35]
florian [How to apply boosts]
Line 38: Line 38:
 ---- ----
  
-==== How to apply boosts ====+ ==== How to apply boosts ====
  
 The boosts can be done via a //hidden input fields// or directly within the //​API-request//​. The boosts can be done via a //hidden input fields// or directly within the //​API-request//​.
Line 54: Line 54:
 A constant factor of 1 is added to the weight, this value is then multiplied with the score of every matching result. The weight may be any non-negative number, where: A constant factor of 1 is added to the weight, this value is then multiplied with the score of every matching result. The weight may be any non-negative number, where:
  
 +    * ''​weight<​0''​ means a //decreased score//.
     * ''​weight=0''​ means that the resulting //score will stay the same// ((score*(0+1) = score.))     * ''​weight=0''​ means that the resulting //score will stay the same// ((score*(0+1) = score.))
     * ''​weight>​0''​ means an //increased score//.     * ''​weight>​0''​ means an //increased score//.
Line 59: Line 60:
  
  
-For example ''​pushAttrib[gender][female]=5.0''​ will multiply the scores of all results matching the attribute ''​gender=female''​ by a factor of **5+1 = 6**.+For example ''​pushAttrib[gender][female]=5.0''​ will multiply the scores of all results matching the attribute ''​gender=female''​ by a factor of **5+1 = 6**. 
  
-//We recommend using weights between 1 and 3.//+Negative values will push products down to the end of the productlisting
  
-<note important>​The number of results stays the same, only the order of results is changed. \\ This also means that the available filters do not change when boosting.</​note>​+**We recommend using weights between -0.9 and 3.** 
 + 
 +<note important>​Values below -0.9 are automatically turned into -0.9 due to technical constraints.</​note>​ 
 + 
 +<note important>​The number of results stays the same, only the order of results is changed.</​note>​
  
 \\ \\