Contexts missing from dashboard

Affected: Contexts

Symptoms

• Contexts that were in the dashboard are no longer there.
• There has been a decrease/drop-off in contexts in the dashboard.

Cause

The following could cause this issue:

• Single shared key for many contexts
• Anonymous contexts do not appear in the dashboard
• Contexts expire when not used for 30 days
• Change may not be immediately reflected on the dashboard for a few minutes
• SDK not configured to send events
• Ad blockers or Do Not Track (DNT) settings enabled

Solution

Single shared key for many contexts

If one or a few contexts are making significantly more flag requests than others and lack other attributes, it could be due to using a single shared key.

• Check how you are creating contexts in the SDKs and verify whether the same key attribute is being used for multiple contexts.

Anonymous contexts do not appear in the dashboard

Anonymous contexts can be used with features such as percentage rollouts, experimentation, analytics, and targeting individual contexts by key. However:

• Anonymous contexts are not stored in LaunchDarkly and will not appear in the dashboard.
• Anonymous contexts still count toward your client-side monthly contexts or Monthly Active Users (MAU) allotment. Read more in the Anonymous Contexts documentation.

Contexts expire when not used for 30 days

Contexts that have not had their key evaluated for 30 days expire from the dashboard and the primary context count. This applies to both server-side and client-side SDKs.

• Check logs for any errors in sending events.
• To make a context reappear, use it again by evaluating it with a feature flag.

Change may not be immediately reflected on the dashboard for a few minutes

After LaunchDarkly receives an event, it may take a few minutes for the information to appear in the Context section of the dashboard.

Using Live Events lets you directly monitor user data and flag evaluations, ensuring they are processed correctly. To verify user data in real-time, using Live Events:

1. Access Live Events: Log in to your LaunchDarkly account and navigate to the Live Events section.

2. Select the Relevant Project or Environment: Choose the project or environment for observation.

3. Trigger Flag Evaluations: Simulate user interactions or events to trigger evaluations.

4. Monitor Real-Time Updates: View user data and flag evaluation results as they appear in Live Events.

SDK not configured to send events

Most LaunchDarkly SDKs are configured by default to send events, enabling context data and flag evaluations to be transmitted back to LaunchDarkly and appear in the dashboard.

If the SDK has been configured not to send events—for example, by setting sendEvents: false or using a similar configuration depending on the SDK—events will not be sent back to LaunchDarkly. This will result in:

• Context data and evaluations not appearing on the dashboard.
• Contexts seeming to be "missing."

To resolve this issue:

1. Verify the SDK configuration is set to allow events to be sent to LaunchDarkly.

2. Adjust the configuration if necessary to enable event transmission.

Ad blockers or Do Not Track (DNT) settings enabled

LaunchDarkly does not circumvent end-users' privacy settings, so if any of your end-users have "Do Not Track" enabled or have any ad-blocking extensions installed, events will not be sent to LaunchDarkly, which will prevent contexts from appearing in the dashboard.

Read Browser privacy settings block analytic events to LaunchDarkly to learn more.