You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@param filter: Boolean-returning [ReQL](https://docs.recombee.com/reql.html) expression which allows you to filter recommended items based on the values of their attributes.
57
-
58
-
@param booster: Number-returning [ReQL](https://docs.recombee.com/reql.html) expression which allows you to boost recommendation rate of some items based on the values of their attributes.
56
+
@param scenario: Scenario defines a particular application of recommendations. It can be for example "homepage", "cart" or "emailing".
59
57
60
-
@param cascade_create: If item of given *itemId* or user of given *targetUserId* doesn't exist in the database, it creates the missing entity/entities and returns some (non-personalized) recommendations. This allows for example rotations in the following recommendations for the user of given *targetUserId*, as the user will be already known to the system.
61
58
62
-
@param scenario: Scenario defines a particular application of recommendations. It can be for example "homepage", "cart" or "emailing". You can see each scenario in the UI separately, so you can check how well each application performs. The AI which optimizes models in order to get the best results may optimize different scenarios separately, or even use different models in each of the scenarios.
59
+
You can set various settings to the [scenario](https://docs.recombee.com/scenarios.html) in the [Admin UI](https://admin.recombee.com). You can also see performance of each scenario in the Admin UI separately, so you can check how well each application performs.
63
60
64
-
@param logic: Logic specifies particular behavior of the recommendation models. You can pick tailored logic for your domain (e-commerce, multimedia, fashion ...) and use case.
65
61
66
-
See [this section](https://docs.recombee.com/recommendation_logic.html) for list of available logics and other details.
62
+
The AI which optimizes models in order to get the best results may optimize different scenarios separately, or even use different models in each of the scenarios.
67
63
68
64
69
-
The difference between `logic` and `scenario` is that `logic` specifies mainly behavior, while `scenario` specifies the place where recommendations are shown to the users.
70
-
65
+
@param cascade_create: If item of given *itemId* or user of given *targetUserId* doesn't exist in the database, it creates the missing entity/entities and returns some (non-personalized) recommendations. This allows for example rotations in the following recommendations for the user of given *targetUserId*, as the user will be already known to the system.
71
66
72
67
@param return_properties: With `returnProperties=true`, property values of the recommended items are returned along with their IDs in a JSON dictionary. The acquired property values can be used for easy displaying of the recommended items to the user.
@param filter: Boolean-returning [ReQL](https://docs.recombee.com/reql.html) expression which allows you to filter recommended items based on the values of their attributes.
166
+
167
+
168
+
Filters can be also assigned to a [scenario](https://docs.recombee.com/scenarios.html) in the [Admin UI](https://admin.recombee.com).
169
+
170
+
171
+
@param booster: Number-returning [ReQL](https://docs.recombee.com/reql.html) expression which allows you to boost recommendation rate of some items based on the values of their attributes.
172
+
173
+
174
+
Boosters can be also assigned to a [scenario](https://docs.recombee.com/scenarios.html) in the [Admin UI](https://admin.recombee.com).
175
+
176
+
177
+
@param logic: Logic specifies particular behavior of the recommendation models. You can pick tailored logic for your domain and use case.
178
+
179
+
See [this section](https://docs.recombee.com/recommendation_logics.html) for list of available logics and other details.
180
+
181
+
182
+
The difference between `logic` and `scenario` is that `logic` specifies mainly behavior, while `scenario` specifies the place where recommendations are shown to the users.
183
+
184
+
185
+
Logic can be also set to a [scenario](https://docs.recombee.com/scenarios.html) in the [Admin UI](https://admin.recombee.com).
186
+
187
+
170
188
@param user_impact: **Expert option** If *targetUserId* parameter is present, the recommendations are biased towards the given user. Using *userImpact*, you may control this bias. For an extreme case of `userImpact=0.0`, the interactions made by the user are not taken into account at all (with the exception of history-based blacklisting), for `userImpact=1.0`, you'll get user-based recommendation. The default value is `0`.
Copy file name to clipboardExpand all lines: recombee_api_client/api_requests/recommend_items_to_user.py
+44-22
Original file line number
Diff line number
Diff line change
@@ -7,35 +7,34 @@ class RecommendItemsToUser(Request):
7
7
"""
8
8
Based on user's past interactions (purchases, ratings, etc.) with the items, recommends top-N items that are most likely to be of high value for a given user.
9
9
10
+
The most typical use cases are recommendations at homepage, in some "Picked just for you" section or in email.
11
+
10
12
It is also possible to use POST HTTP method (for example in case of very long ReQL filter) - query parameters then become body parameters.
11
13
12
14
The returned items are sorted by relevancy (first item being the most relevant).
@param user_id: ID of the user for which personalized recommendations are to be generated.
21
+
@param user_id: ID of the user for whom personalized recommendations are to be generated.
20
22
21
23
@param count: Number of items to be recommended (N for the top-N recommendation).
22
24
23
25
24
-
Optional parameters:
25
-
@param filter: Boolean-returning [ReQL](https://docs.recombee.com/reql.html) expression which allows you to filter recommended items based on the values of their attributes.
26
26
27
-
@param booster: Number-returning [ReQL](https://docs.recombee.com/reql.html) expression which allows you to boost recommendation rate of some items based on the values of their attributes.
27
+
Optional parameters:
28
+
@param scenario: Scenario defines a particular application of recommendations. It can be for example "homepage", "cart" or "emailing".
28
29
29
-
@param cascade_create: If the user does not exist in the database, returns a list of non-personalized recommendations and creates the user in the database. This allows for example rotations in the following recommendations for that user, as the user will be already known to the system.
30
30
31
-
@param scenario: Scenario defines a particular application of recommendations. It can be for example "homepage", "cart" or "emailing". You can see each scenario in the UI separately, so you can check how well each application performs. The AI which optimizes models in order to get the best results may optimize different scenarios separately, or even use different models in each of the scenarios.
31
+
You can set various settings to the [scenario](https://docs.recombee.com/scenarios.html) in the [Admin UI](https://admin.recombee.com). You can also see performance of each scenario in the Admin UI separately, so you can check how well each application performs.
32
32
33
-
@param logic: Logic specifies particular behavior of the recommendation models. You can pick tailored logic for your domain (e-commerce, multimedia, fashion ...) and use case.
34
33
35
-
See [this section](https://docs.recombee.com/recommendation_logic.html) for list of available logics and other details.
34
+
The AI which optimizes models in order to get the best results may optimize different scenarios separately, or even use different models in each of the scenarios.
36
35
37
36
38
-
The difference between `logic` and `scenario` is that `logic` specifies mainly behavior, while `scenario` specifies the place where recommendations are shown to the users.
37
+
@param cascade_create: If the user does not exist in the database, returns a list of non-personalized recommendations and creates the user in the database. This allows for example rotations in the following recommendations for that user, as the user will be already known to the system.
39
38
40
39
41
40
@param return_properties: With `returnProperties=true`, property values of the recommended items are returned along with their IDs in a JSON dictionary. The acquired property values can be used for easy displaying of the recommended items to the user.
@param filter: Boolean-returning [ReQL](https://docs.recombee.com/reql.html) expression which allows you to filter recommended items based on the values of their attributes.
139
+
140
+
141
+
Filters can be also assigned to a [scenario](https://docs.recombee.com/scenarios.html) in the [Admin UI](https://admin.recombee.com).
142
+
143
+
144
+
@param booster: Number-returning [ReQL](https://docs.recombee.com/reql.html) expression which allows you to boost recommendation rate of some items based on the values of their attributes.
145
+
146
+
147
+
Boosters can be also assigned to a [scenario](https://docs.recombee.com/scenarios.html) in the [Admin UI](https://admin.recombee.com).
148
+
149
+
150
+
@param logic: Logic specifies particular behavior of the recommendation models. You can pick tailored logic for your domain and use case.
151
+
152
+
See [this section](https://docs.recombee.com/recommendation_logics.html) for list of available logics and other details.
153
+
154
+
155
+
The difference between `logic` and `scenario` is that `logic` specifies mainly behavior, while `scenario` specifies the place where recommendations are shown to the users.
156
+
157
+
158
+
Logic can be also set to a [scenario](https://docs.recombee.com/scenarios.html) in the [Admin UI](https://admin.recombee.com).
159
+
160
+
139
161
@param diversity: **Expert option** Real number from [0.0, 1.0] which determines how much mutually dissimilar should the recommended items be. The default value is 0.0, i.e., no diversification. Value 1.0 means maximal diversification.
0 commit comments