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
Copy file name to clipboardExpand all lines: docs/personalization/recommendation_models.md
+25-1Lines changed: 25 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -212,4 +212,28 @@ The logic used for resolving a submodel is as follows:
212
212
213
213
You can specify a single or multiple attributes with multiple values for requesting recommendations.
214
214
Recommendation are fetched from all the submodels and merged based on the weight (relevance).
215
-
If one of the submodels delivers recommendations with better relevance, the results of other models can disappear from the list.
215
+
If one of the submodels delivers recommendations with better relevance, the results of other models can disappear from the list.
216
+
217
+
## Time-slot based models
218
+
219
+
Time-slot based models consider only a particular range of time rather than the full day when calculating recommendations.
220
+
They can be used for [popularity](recommendation_models#popularity-models) and [collaborative](recommendation_models#collaborative-models) types of models.
221
+
222
+
These models can be an optimum answer for customers who notice variable consumption of their content or products throughout the day, with different content being popular, for example, in the morning and afternoon.
223
+
Time-slot based models can cover these needs, as you can request to configure and set specific time slots.
224
+
225
+
In these models, recommendations are created for both configured time slots and for the main model (for example, for the last 30 days).
226
+
However, time-slot based recommendations are shown as priority in the hours for which time slots are configured (if requested in a recommendation call).
227
+
228
+
These time slots:
229
+
230
+
- can cover any time frame, including minutes (for example, 11 A.M. - 3:30 P.M.), and don't necessarily have to start and end at full hour
231
+
- cannot overlap, for example, you cannot set slots 8 A.M. - 11 A.M. and 9 A.M. - 12 A.M. at once
232
+
- cannot span between two days, for example, you cannot set a slot to 11 P.M. - 3 A.M.
233
+
234
+
To use time slot-based models, this feature must be enabled.
235
+
236
+
!!! note "Enable time slots"
237
+
238
+
Time slots must be enabled by and configured [[= product_name_base =]] Team.
239
+
To start using this functionality and request that a specific model is created, contact customer support ([email protected]).
0 commit comments