personalization
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
personalization [2017/10/02 15:23] florian [How to apply boosts] |
personalization [2019/05/28 15:35] florian [How to apply boosts] |
||
|---|---|---|---|
| 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.//** | ||
| + | |||
| + | ---- | ||
| ==== Boosting results per user ==== | ==== Boosting results per user ==== | ||
| Line 15: | Line 19: | ||
| ==== Example ==== | ==== Example ==== | ||
| - | The search form may look like this for user that likes //Red// a lot and //Nike// a little less: | + | The search form may look like this for user that likes //Red// a lot and //Summer// products a little less: |
| <code html> | <code html> | ||
| Line 23: | Line 27: | ||
| <input type="submit"> | <input type="submit"> | ||
| <input type="hidden" name="pushAttrib[Color][Red]" value="2.9"> | <input type="hidden" name="pushAttrib[Color][Red]" value="2.9"> | ||
| - | <input type="hidden" name="pushAttrib[vendor][Nike]" value="1.5"> | + | <input type="hidden" name="pushAttrib[Season][Summer]" value="1.5"> |
| ... | ... | ||
| </form> | </form> | ||
| Line 34: | Line 38: | ||
| ---- | ---- | ||
| - | ==== How to apply boosts ==== | + | ==== How to apply boosts ==== |
| - | The boosts can be applied by adding //hidden input fields// to the search form that contain the //attribute//, //attribute value// and a //boost factor (weight)//. **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. | + | 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. | ||
| + | |||
| + | 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.]] | ||
| 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. | ||
| Line 46: | 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 51: | 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> | ||
| \\ | \\ | ||
| If you have any questions or need further information please contact [[support@findologic.com]]. | If you have any questions or need further information please contact [[support@findologic.com]]. | ||
| + | |||
| + | ----- | ||
| + | |||
| + | ==== Example in a live shop ==== | ||
| + | |||
| + | The following screenshots show how results may change on attributes, which are being boosted based on information about the user. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | **A generic search** for the query ''jacke'' is submitted and results are shown. | ||
| + | |||
| + | {{:adler_generic.png?820x1000|generic search}} | ||
| + | |||
| + | ---- | ||
| + | |||
| + | The same search is being submitted and as the user in this case is identified as a man, **products for men are being pushed**. | ||
| + | \\ | ||
| + | The results now look like this: | ||
| + | |||
| + | {{:adler_men.png?750x1000|push men products}} | ||
| + | |||
| + | ---- | ||
| + | |||
| + | The same search is being submitted and as the user in this case is identified as a woman, **products for women are being pushed.** | ||
| + | \\ | ||
| + | The results now look like this: | ||
| + | |||
| + | {{:adler_women.png?750x1000|push women products}} | ||
| + | |||
| + | {{tag>personalization google_analytics google}} | ||