Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

recommendation_models.md: Fix anchor links #323

Merged
merged 1 commit into from
Dec 3, 2024
Merged

recommendation_models.md: Fix anchor links #323

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/personalization/recommendation_models.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -224,8 +224,8 @@ They work best in straightforward cases when you filter by the value of the attr

Dynamic attribute submodels:

- operate only on [nominal attributes](recommendation_models#nominal-attributes) (numeric attributes are not supported)
- can be used for [popularity](recommendation_models#popularity-models) and [collaborative](recommendation_models#collaborative-models) types of models (as they support submodels)
- operate only on [nominal attributes](#nominal-attributes) (numeric attributes are not supported)
- can be used for [popularity](#popularity-models) and [collaborative](#collaborative-models) types of models (as they support submodels)
- have limitation of max. 50 attribute values (if more, you need to follow the procedure of manual configuration by [[= product_name_base =]] Team)
- operate on scenarios with the selected `Submodels` data type option
- require sending a request and building a model
Expand All @@ -248,7 +248,7 @@ Dynamic attribute submodels:
## Time-slot based models

Time-slot based models consider only a particular range of time rather than the full day when calculating recommendations.
They can be used for [popularity](recommendation_models#popularity-models) and [collaborative](recommendation_models#collaborative-models) types of models.
They can be used for [popularity](#popularity-models) and [collaborative](#collaborative-models) types of models.

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.
Time-slot based models can cover these needs, as you can request to configure and set specific time slots.
Expand All @@ -267,4 +267,4 @@ To use time slot-based models, this feature must be enabled.
!!! note "Enable time slots"

Time slots must be enabled and configured by [[= product_name_base =]] Team.
To start using this functionality and request that a specific model is created, contact customer support ([email protected]).
To start using this functionality and request that a specific model is created, contact customer support ([email protected]).
Loading