From e74351ca8c09b5d2c4a95d965adf5dd3b5c14280 Mon Sep 17 00:00:00 2001 From: Todd Baert Date: Thu, 8 Sep 2022 13:04:08 -0400 Subject: [PATCH] Add provider links Signed-off-by: Todd Baert --- docs/reference/concepts/03-evaluation-context.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/reference/concepts/03-evaluation-context.mdx b/docs/reference/concepts/03-evaluation-context.mdx index 9835395b..f265f7e5 100644 --- a/docs/reference/concepts/03-evaluation-context.mdx +++ b/docs/reference/concepts/03-evaluation-context.mdx @@ -110,8 +110,8 @@ Many providers serialize the evaluation context as part of their operation. Be c ## Targeting Key -Many feature flag management systems require an identifier for the subject of flag evaluation. For many feature flag systems this is required in order to perform fractional evaluation or percentage-based rollouts deterministically. In the case of web applications or mobile apps, the subject is frequently an end user, but in other cases it could be a service or client application. The `evaluation context` includes an optional `targeting key` field for this purpose. The targeting key should contain a string uniquely identifying the subject (i.e.: a UUID, a hash of some user attribute such as an email, or a the hostname of an application or service). Some providers may require this field to be set to function correctly. +Many feature flag management systems require an identifier for the subject of flag evaluation. For many feature flag systems this is required in order to perform fractional evaluation or percentage-based rollouts deterministically. In the case of web applications or mobile apps, the subject is frequently an end user, but in other cases it could be a service or client application. The `evaluation context` includes an optional `targeting key` field for this purpose. The targeting key should contain a string uniquely identifying the subject (i.e.: a UUID, a hash of some user attribute such as an email, or a the hostname of an application or service). Some [providers](/docs/reference/concepts/provider) may require this field to be set to function correctly. ## Personally Identifiable Information (PII) Considerations -Be thoughtful in your inclusion of personal data in the `evaluation context`. Such data is useful for targeting and dynamic evaluation, but you should consider how the provider in use may handle or persist this data. Hooks (specifically hooks implementing the _before_ stage) can be useful to restrict, filter or anonymize data in the `evaluation context`. +Be thoughtful in your inclusion of personal data in the `evaluation context`. Such data is useful for targeting and dynamic evaluation, but you should consider how the [provider](/docs/reference/concepts/provider) in use may handle or persist this data. Hooks (specifically hooks implementing the _before_ stage) can be useful to restrict, filter or anonymize data in the `evaluation context`.