• Home
  • Integrations
  • SDKs
  • Guides
  • API docs
No results for ""
EXPAND ALL

EDIT ON GITHUB

Data Export

Read time: 2 minutes
Last edited: May 20, 2022
Data Export is an add-on feature

Data Export is available as an add-on for customers on an Enterprise plan. To learn more, read about our pricing. To add Data Export to your plan, contact Sales.

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.

A diagram of Data Export with supported destinations.
A diagram of Data Export with supported destinations.

You can also use the REST API: Data Export destinations

How Data Export 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:

  • Amazon Kinesis
  • Azure Event Hubs
  • Google Cloud Pub/Sub
  • mParticle
  • Segment

To learn more about event formatting, read Schema reference.

Some Data Export destinations have different event formatting schema. If you use mParticle or Segment as your event destination, we have specific documentation for their event schema.

  • mParticle schema reference
  • Segment schema reference

Exporting event data for flags and environments

You must configure your SDKs to send events

To use Data Export, all of your SDKs must be configured to send events. If you have disabled sending events for testing purposes, you must re-enable it. To learn more about the events SDKs send to LaunchDarkly, read Analytics events.

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

Exporting flag event data

To export data from a specific flag to a destination:

  1. Navigate to the flag dashboard.
  2. Click the name of the flag you wish to export data from.
  3. Click the Settings tab.
  4. Select the Send detailed events to data export destinations 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.

Understanding Data Export and Experimentation events

If you check a flag's Send detailed events to data export destinations checkbox, then LaunchDarkly exports evaluation events for all users that encounter the flag.

If you do not check the Send detailed events to data export destinations checkbox, then LaunchDarkly does not export evaluation events, unless you are using the flag in an experiment with audience allocation. If you are using the flag in an experiment with audience allocation, then LaunchDarkly will still export evaluation events for users included in the experiment, but no other users.

You can tell if a user evaluation was part of an experiment from the optional inExperiment attribute. Evaluations that were part of an experiment have the inExperiment attribute on the evaluation reason set to true. To learn more, read Evaluation reasons.

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 Account settings page.
  2. Click the Projects tab.
  3. Find the environment you wish to export data from.
  4. From the overflow menu, choose "Edit environment." The "Edit environment" panel appears.
  5. Select the Send detailed events to data export destinations checkbox.
  6. Click Save environment:
The "Edit environment" panel, with the Data Export checkbox called out.
The "Edit environment" panel, with the Data Export checkbox called out.

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 five times over a 30 minute period.