personalization
Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
personalization [2018/06/05 13:56] markus [Personalisation with FINDOLOGIC] |
personalization [2018/06/05 15:08] stefan [How to apply boosts] |
||
---|---|---|---|
Line 40: | Line 40: | ||
==== 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. |