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
personalization [2019/05/28 15:35]
florian [How to apply boosts]
personalization [2020/06/17 09:50] (current)
amil
Line 1: Line 1:
-===== Personalization with FINDOLOGIC ​=====+===== Personalization with Findologic ​=====
  
 **With this short manual you can easily learn how to boost certain products based on user information //provided by a webshop.//​** ​ **With this short manual you can easily learn how to boost certain products based on user information //provided by a webshop.//​** ​
Line 7: Line 7:
 ==== Boosting results per user ==== ==== Boosting results per user ====
  
-FINDOLOGIC ​provides an interface to boost certain products based on their attributes so they are ranked higher in the search results. \\+Findologic ​provides an interface to boost certain products based on their attributesso they are ranked higher in the search results. \\
 The interface can be used for many different purposes: The interface can be used for many different purposes:
  
    * Boost products from the preferred vendor or with the favorite color based on data from personalization providers.    * Boost products from the preferred vendor or with the favorite color based on data from personalization providers.
-   * Boost products for men / women based on the user profile of the currently logged in users.+   * Boost products for men / women based on the user profile of the currently logged-in users.
    * Boost new products when searching from a blog page where the latest trends for the new season are described.    * Boost new products when searching from a blog page where the latest trends for the new season are described.
  
Line 42: Line 42:
 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//​.
  
-For the first option, a hidden ​imput field that contains the //​attribute//,​ //attribute value// and a //boost factor (weight)// need to be added to the search form. **This must happen on the shop side.** The fields can be injected using Javascript ​or rendered server side, as long as they are available before the search form is submitted.+For the first option, a hidden ​input field that contains the //​attribute//,​ //attribute value// and a //boost factor (weight)// need to be added to the search form. **This must happen on the shop side.** The fields can be injected using JavaScript ​or rendered server side, as long as they are available before the search form is submitted.
  
-To boost within the API-request the //​attribute//,​ the //attribute value// and the //boost factor// needs to be attachted ​to the request which is send. How this is done can be looked up [[integration_documentation:​request#​push_attributes|in our request documentation.]]+To boost within the API-request the //​attribute//,​ the //attribute value// and the //boost factor// needs to be attached ​to the request which is sent. How this is done can be looked up [[integration_documentation:​request#​push_attributes|in our request documentation.]]
  
 The actual attributes and weights may be fetched from the current user's profile or a personalization provider, but can also be static depending on the current page. The actual attributes and weights may be fetched from the current user's profile or a personalization provider, but can also be static depending on the current page.
  
-<​note>​For entirely static boosts the FINDOLOGIC ​push rules are better suited.</​note>​+<​note>​For entirely static boosts the Findologic ​push rules are better suited.</​note>​
  
-The //​attribute//​ and //attribute value// need to **exactly match the attributes in the FINDOLOGIC ​export** (not the display name in the filter configuration).+The //​attribute//​ and //attribute value// need to **exactly match the attributes in the Findologic ​export** (not the display name in the filter configuration).
  
 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:
Line 62: Line 62:
 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**. 
  
-Negative values will push products down to the end of the productlisting+Negative values will push products down to the end of the product listing
  
 **We recommend using weights between -0.9 and 3.** **We recommend using weights between -0.9 and 3.**