-
Notifications
You must be signed in to change notification settings - Fork 86
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
IBX-9124: Dynamic attribute submodels described in Developer Document…
…ation (#2523) * Dynamic attribute submodels * Update * fix * fix after doc review
- Loading branch information
1 parent
a5c7dcb
commit 7ab238a
Showing
1 changed file
with
11 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -88,6 +88,17 @@ For more information, see [Submodels]([[= user_doc =]]/personalization/recommend | |
|
||
`GET https://reco.perso.ibexa.co/api/v2/00000/john.doe/landing_page.json?numrecs=50&outputtypeid=1&width-range=10:30&color=green` | ||
|
||
!!! note "Dynamic attribute submodels" | ||
|
||
If dynamic attribute submodels are enabled, you only need to add submodel parameters to the request to trigger dynamic submodels in the upcoming model build. | ||
|
||
Dynamic attribute submodels must be enabled by [[= product_name_base =]] Team. | ||
To start using this functionality, contact [email protected]. | ||
|
||
When enabled, to build dynamic attribute submodels, you need to send the request (which includes `"ATTRIBUTE_NAME=VALUE"` query parameters) to the scenario with model you want to use submodels for: | ||
|
||
`GET https://reco.perso.ibexa.co/api/v2/00000/john.doe/{SCENARIO_NAME}?numrecs=50&outputtypeid=1&color=red` | ||
|
||
##### Segment parameters | ||
|
||
If you have configured segments, you can use them in the recommendation model. Pass the following parameter | ||
|