Browser privacy settings block analytic events to LaunchDarkly

Affected: JavaScript, React, and Vue client-side SDKs

Symptoms

The following issue occurs when using the JavaScript SDK or another client-side SDK built off of the browser JavaScript SDK:

• A context does not appear in the dashboard, but flags are being evaluated correctly.

Cause

Many browsers have some capability to prevent events from being sent to LaunchDarkly. Usually, this comes in the form of the "Do Not Track" browser option or one of the many available ad-blocking browser extensions. 

LaunchDarkly does not circumvent end-users privacy settings, so any of your end-users who have "Do Not Track" enabled or have any ad-blocking extensions installed will not send events back to LaunchDarkly.

This only affects analytic events and does not affect the API necessary for flag evaluation, so your end-users will still receive the correct variations even with "Do Not Track" enabled or with ad-blocking extensions installed.

Solution

Developers can disable "Do Not Track" and/or any ad-blocking extensions to test that events get sent back to LaunchDarkly.

1. Turn off your "Do Not Track" browser option.

   • How to manage "Do Not Track"

2. Disable or uninstall all ad-blocking browser extensions.

   • How to manage browser extensions

3. Rerun the test and check if context info appears in the dashboard.