LaunchDarkly Source

LaunchDarkly is a feature management platform that empowers development teams to safely deliver and control software through feature flags.

This is an Event Cloud Source which can not only export data into your Segment warehouse, but they can also federate the exported data into your other enabled Segment Destinations.

This source is maintained by LaunchDarkly. For any issues with the source, please reach out to their team.

NOTE: The LaunchDarkly Source is currently in beta, which means that they are still actively developing the source. This doc was last updated on September 11, 2019. If you are interested in joining their beta program or have any feedback to help improve the LaunchDarkly Source and its documentation, please let their team know!

Getting Started

  1. From your Segment UI’s Sources page click on “Add Source”.
  2. Search for “LaunchDarkly” within the Sources Catalog and confirm by clicking “Connect”.
  3. Give the Source a nickname and follow the setup flow to “Add Source”. The nickname will be used to designate the source in the Segment interface, and Segment will create a related schema name. The schema name is the namespace you’ll be querying against in your warehouse. The nickname can be whatever you like, but we recommend sticking to something that reflects the source itself and distinguishes amongst your environments (eg. SourceName_Prod, SourceName_Staging, SourceName_Dev).
  4. Copy the Write key from the Segment UI and log in to your LaunchDarkly account - navigate to Integrations > Data Export Destinations
  5. Select “Add destination” and select “Segment” in the dropdown menu.
  6. Choose a name for the destination and the LaunchDarkly environment for which events will be forwarded to Segment
  7. Paste the Segment key into the “Write Key” textbox.
  8. Click “Save Destination”

Events

Below is a table of events that LaunchDarkly sends to Segment. These events will show up as tables in your warehouse, and as regular events in your other Destinations. LaunchDarkly will send through the userId if available.

Event NameDescription
featureA feature flag has been evaluated
clickA user clicked on a CSS selector for which they have configured a LaunchDarkly experimentation goal
PageA user has loaded a page which is associated with a LaunchDarkly experimentation goal
CustomA custom event was sent by the LaunchDarkly SDK

Event Properties

Below are tables outlining the properties included in the events listed above.

Property NameDescription
eventEmail event type
Common PropertiesProperties common to all event types
environmentThe LaunchDarkly environment ID corresponding to event
projectThe LaunchDarkly project ID corresponding to the event
keyThe flag key corresponding to the event. In the case of experimentation events, this will be the goal key for the experiment.
Feature Request Event Properties
valueThe value the flag evaluated to
flagVersionThe version of the flag when it was evaluated
reasonKindThe evaluation reason for the flag.
prereqOfSet to another flag’s key if this flag evaluation was only performed in order to determine whether the prerequisite values were met for the indicated flag. See flag prerequisites.
defaultIndicates whether the flag value was the result of the default variation being selected
Page View Event Properties
urlThe URL the user was on when the flag was evaluated
Click Event Properties
urlThe URL the user was on when the flag was evaluated
selectorContains the CSS selector corresponding to the click event
Custom Event PropertiesCustom Events have no additional properties besides the common properties

Adding Destinations

Now that your Source is set up, you can connect it with Destinations.

Log into your downstream tools and check to see that your events are populating and they contains all the properties you expect. If all your events and properties are not showing up, refer to the Destination docs for troubleshooting.

If there are any issues with how the events are arriving to Segment, please contact the LaunchDarkly team.



Questions? Need help? Contact us!
Can we improve this doc?
Email us: docs-feedback@segment.com!