By default, all of the attributes in your user objects will be sent back to LaunchDarkly. This data lets LaunchDarkly calculate the current flag settings for users on your Users pages:
This data is also used to power the autocomplete functionality on the flag settings pages. In some cases, you may not wish to send attribute values back to LaunchDarkly. For example, you may need to target by customer PII data like e-mail addresses, without disclosing your end-users' e-mail addresses to LaunchDarkly.
LaunchDarkly's private user attributes feature allows you to choose which attributes get sent back to LaunchDarkly. This allows you to create targeting rules based on these attributes without having to send them to LaunchDarkly.
You can configure private attribute settings in your SDK. There are three different ways to configure private attributes:
- You can mark all attributes private globally in your
- You can mark specific attributes private by name globally in your
- You can also mark specific attributes private by name for individual users when you construct
Note that user
keys cannot be marked private.
See your SDK's documentation for instructions on setting these configuration options.
Implications of using private attributes
If a feature flag contains targeting rules that reference private attributes, LaunchDarkly will not be able to calculate flag settings for your users. The Users page will note when we're unable to calculate flag settings because of private attributes.
In addition, we will not be able to provide autocomplete values for attributes marked private.