| Name | Type | Description | Notes |
|---|---|---|---|
| key | string | The user key. This is the only mandatory user attribute. | [optional] |
| secondary | string | If provided, used with the user key to generate a variation in percentage rollouts | [optional] |
| ip | string | The user's IP address | [optional] |
| country | string | The user's country | [optional] |
| string | The user's email | [optional] | |
| first_name | string | The user's first name | [optional] |
| last_name | string | The user's last name | [optional] |
| avatar | string | An absolute URL to an avatar image. | [optional] |
| name | string | The user's full name | [optional] |
| anonymous | bool | Whether the user is anonymous. If true, this user does not appear on the Contexts list in the LaunchDarkly user interface. | [optional] |
| custom | array<string,mixed> | Any other custom attributes for this user. Custom attributes contain any other user data that you would like to use to conditionally target your users. | [optional] |
| private_attrs | string[] | A list of attribute names that are marked as private. You can use these attributes in targeting rules and segments. If you are using a server-side SDK, the SDK will not send the private attribute back to LaunchDarkly. If you are using a client-side SDK, the SDK will send the private attribute back to LaunchDarkly for evaluation. However, the SDK won't send the attribute to LaunchDarkly in events data, LaunchDarkly won't store the private attribute, and the private attribute will not appear on the Contexts list. | [optional] |