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

Data Export

Data Export is an Enterprise feature

Data Export is only available to customers on our Enterprise plans. If you're interested in learning more about our Enterprise plans, contact sales@launchdarkly.com.

Overview

This topic explains how to use LaunchDarkly's Data Export feature to export and store flag, user, and experimentation event data.

Data Export provides a real-time export of raw analytics data, including feature flag requests, analytics events, custom events, experimentation events, and more. By exporting your data to a location of your choice, you can use your own data warehouse and tools to analyze event data.

How it works

Data Export works by sending data to one of our supported destinations. A destination is an external service which can receive and store the data.

We support the following export destinations:

To learn more about event formatting, read Export format reference.

Exporting event data for flags and environments

After you create a data export destination, you can send data for individual flags or for all the flags in an environment to it.

Exporting flag event data

To export data from a specific flag to a destination:

  1. Navigate to the dashboard.
  2. Click the name of the flag you wish to export data from. The flag menu appears.
  3. Click Settings.
  4. Select the Send detailed event information for this flag checkbox.
  5. Click Save Changes.
The flag's Settings page, with the data export checkbox called out.

The flag's Settings page, with the data export checkbox called out.

Exporting environment event data

When you export event data from an environment, LaunchDarkly exports all data from every new flag you create after you enable data export. It does not send event data from flags created before you enabled data export.

To export data from an environment to a destination:

  1. Navigate to the dashboard.
  2. Click Account settings.
  3. Find the environment you wish to export data from.
  4. Click Edit. The "Edit production environment" screen appears.
  5. Select the Send detailed event information for new flags checkbox.
  6. Click Save Environment.
The Edit production environment screen, with the data export checkbox called out.

The Edit production environment screen, with the data export checkbox called out.

Customizing which data LaunchDarkly exports

You can control which users send event data to destinations by choosing a group of users affected by certain flag targeting rules. To learn more, read Controlling experiment populations.

Enabling data export population targeting

If you can't see this feature, your SDKs may be out of date. To solve this problem:

  1. Update your SDKs to the latest version.
  2. Contact support@launchdarkly.com to enable the feature.

To customize which users send event data to data export destinations:

  1. Identify which flag you wish to export events from.
  2. Navigate to the flag's Settings page.
  3. Click N of N targeting rules in the "Exporting events from" line. The "Configure event settings" screen appears.
The flag's Settings tab with the targeting rules link called out.

The flag's Settings tab with the targeting rules link called out.

  1. Click the Custom selection radio box to modify the users whose events are exported. When you click Custom selection, you can choose which targeting rules you wish to include or exclude in data exports.
  2. Select the checkboxes of rules you wish to include in the experiment. This refines the population of users whose events are exported.
The Configure event settings screen.

The Configure event settings screen.

  1. Click Save Changes. A confirmation modal appears.
  2. Type the name or key of the environment in the text box and click Confirm.

Delivery guarantees

After your application has successfully sent an event to our servers, we will send the event to your configured destinations at least once.

An event is sent to your destinations exactly once, with some exceptions. In the event of a hardware failure or networking issue, we may send events multiple times.

Additionally, if your configured destination does not acknowledge receipt of the event, we will retry sending the message 5 times over a 30 minute period.


Data Export


Suggested Edits are limited on API Reference Pages

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