LaunchDarkly Developer Documentation

Get started in under 30 minutes.
LaunchDarkly provides feature flags as a service for Java · Python · Ruby · Go · Node.js · PHP · .NET. Control feature launches -- who sees what and when -- without multiple code deploys. Easy dashboard for phased rollouts, targeting and segmenting.
Need more help? write us at support@launchdarkly.com

Get Started    Documentation

Anonymous users

Overview

This topic explains what anonymous users are and how their information is handled in LaunchDarkly.

Anonymous users are identical to regular users but they are not stored in your dashboard. One of the primary reasons that users are sent anonymously is to avoid unauthenticated users diluting the useful data in the user dashboard.

Ensuring user privacy

You can use anonymous users to hide personally identifiable information (PII), but we recommend using private user attributes instead.

To learn more, read Private user attributes.

Best practices for using unique keys

Sometimes it is useful to generate a unique key for anonymous users. We recommend using unique keys for the following reasons:

  • If you are targeting users individually by key.
  • If you are using LaunchDarkly's A/B testing feature.
  • If you are using the Analytics Data Stream.
  • If you are conducting percentage rollouts.

If you do not have a need to uniquely identify your anonymous users, you could use a shared key for them.


Anonymous users


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.