Flag audiences is only available to customers on select plans and work with both regular flag rollouts and guarded rollouts. To learn more, read about our pricing. To upgrade your plan, contact Sales.
This topic explains how to use flag audiences to understand who evaluated a flag, which variation they received, and what occurred during those evaluations, based on sessions and observability data.
LaunchDarkly automatically generates flag audiences based on incoming evaluation data. You do not need to configure or create audiences for a flag.
This capability helps teams answer important questions during releases, such as who evaluated a flag, which variation they received, and what they experienced around the evaluation. It reduces the need to cross-reference logs, traces, or history across multiple tools and provides clearer visibility during investigations.
The Audience tab combines context information, session replays, and observability data to give teams a clear view of rollout activity and impact. It helps teams:
You can access flag audiences from the Audience tab for any flag. This tab displays the contexts that evaluated the flag, the variations they received, and related session and observability data. From this tab, you can identify who was affected by a change, confirm rollout targeting, and understand evaluation behavior without switching between tools.
Use flag audiences to explore who evaluated a flag and how those evaluations changed over time. This information helps you confirm that rollouts target the right contexts, verify which variations users received, and identify patterns in evaluation activity.
Follow these steps to open the Audience tab and review evaluation details:
The audience table lists the contexts that evaluated the flag within the selected time range. Each row displays key evaluation details for a single context, including:
The audience table provides a traceable record of who evaluated the flag and what occurred during those evaluations. By default, the table shows evaluations from the last seven days. Data is retained for 30 days.
The audience table displays up to 250 contexts at a time. If more than 250 contexts are available, add or adjust filters to narrow your results.
When a flag is part of a guarded release, the Audience tab includes a selector that lets you filter evaluations by rollout stage. Guarded release filters help you focus on evaluations that occurred during a specific rollout.
Selecting a guarded release updates the audience table and chart to show only the contexts that evaluated the flag during that release. The selected rollout is added as a URL parameter so refreshing the page preserves your selection. The variation list updates to show only the variations observed during that release.
The audience table displays a separate row for each context and variation pair recorded during the rollout. When metric data is available, the table adds a dynamic column for each metric associated with the release.
If context attributes include a name, firstName and lastName, or email, the name appears in its own column. Clicking a key opens a dialog with all available attributes for that context.
A flag may have multiple guarded releases. If a flag includes many releases, the selector provides a search field to help you find a specific release.
If no evaluations are available for the selected rollout, the audience table and chart appear empty with guidance to adjust or clear the rollout filter.
Use the controls at the top of the Audience tab to modify what data appears in the audience table and chart. You can:
The Audience tab includes a chart that summarizes evaluation activity over time. You can update the chart by adjusting the audience, variation, or date range filters, or by selecting a guarded release.
If no data is available for the chosen time range, LaunchDarkly disables the search field and variation selector until data becomes available.
You can refine or expand your view of audience data in several ways:
name, email, or device type.Charts update dynamically when you apply filters or specify particular contexts within a context kind.
When an observability SDK is installed, LaunchDarkly adds a session replay link beside each context. A session replay shows what a user or context experienced in your application at the time of evaluation, including actions that occurred before and after the evaluation event.
To learn more, read Session replay.
The replay opens in the session viewer, allowing you to inspect what happened at the time of evaluation.
Each context shows only the most recent session. LaunchDarkly links this session data to the corresponding context and retains it for 30 days.
When viewing audiences during a guarded release, session replay links appear when session data is available for that evaluation.
LaunchDarkly stores audience and session data for a limited time to ensure performance and accuracy. The following details describe how this data is retained and displayed:
Use the following information to troubleshoot common issues with flag audiences and sessions: