Skip to content

Commit bfe9aeb

Browse files
Merge pull request #209079 from jcodella/main
Fixed Personalizer feature concept page
2 parents 9ab2817 + 9e5a7bc commit bfe9aeb

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

articles/cognitive-services/personalizer/concepts-features.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,8 @@ Personalizer does not prescribe, limit, or fix what features you can send for ac
3131
* There must be at least one feature for the context. Personalizer does not support an empty context. If you only send a fixed context every time, Personalizer will choose the action for rankings only regarding the features in the actions.
3232
* For categorical features, you don't need to define the possible values, and you don't need to pre-define ranges for numerical values.
3333

34+
Features are sent as part of the JSON payload in a [Rank API](https://westus2.dev.cognitive.microsoft.com/docs/services/personalizer-api/operations/Rank) call. Each Rank call is associated with a personalization _event_. By default, Personalizer will automatically assign an event ID and return it in the Rank response. This default behavior is recommended for most users, however, if you need to create your own unique event ID (for example, using a GUID), then you can provide it in the Rank call as an argument.
35+
3436
## Supported feature types
3537

3638
Personalizer supports features of string, numeric, and boolean types. It is very likely that your application will mostly use string features, with a few exceptions.
@@ -168,7 +170,6 @@ You can use several other [Azure Cognitive Services](https://www.microsoft.com/c
168170

169171
Each action:
170172

171-
* Has an _event_ ID. If you already have an event ID, you should submit that. If you do not have an event ID, do not send one, Personalizer creates one for you and returns it in the response of the Rank request. The ID is associated with the Rank event, not the user. If you create an ID, a GUID works best.
172173
* Has a list of features.
173174
* The list of features can be large (hundreds) but we recommend evaluating feature effectiveness to remove features that aren't contributing to getting rewards.
174175
* The features in the **actions** may or may not have any correlation with features in the **context** used by Personalizer.

0 commit comments

Comments
 (0)