LaunchDarkly Source
Good to know: Event Cloud source
The LaunchDarkly Source is an event source. This means that it sends data as events, which are behaviors or occurrences tied to a user and a point in time. Data from these sources can be loaded into your Segment warehouses, and also sent to Segment streaming destinations. Learn more about cloud sources.
This source is supported in US data processing regions.
The LaunchDarkly source is only supported in workspaces configured to process data in the US region. Workspaces configured with data processing regions outside of the US cannot connect to this source. For more information, see Regional Segment.
LaunchDarkly is a feature management platform that empowers development teams to safely deliver and control software through feature flags.
This source is maintained by LaunchDarkly. For any issues with the source, contact the LaunchDarkly Support team.
Getting Started
- From your Segment UI’s Sources page click on “Add Source”.
- Search for “LaunchDarkly” within the Sources Catalog and confirm by clicking “Connect”.
- Give the Source a nickname and follow the set up 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).
- Copy the Write key from the Segment UI and log in to your LaunchDarkly account - navigate to Integrations > Data Export Destinations
- Select “Add destination” and select “Segment” in the dropdown menu.
- Choose a name for the destination and the LaunchDarkly environment for which events will be forwarded to Segment
- Paste the Segment key into the “Write Key” textbox.
- 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 Name | Description |
feature |
A feature flag has been evaluated |
click |
A user clicked on a CSS selector for which they have configured a LaunchDarkly experimentation goal |
Page |
A user has loaded a page which is associated with a LaunchDarkly experimentation goal |
Custom |
A custom event was sent by the LaunchDarkly SDK |
Event Properties
Below are tables outlining the properties included in the events listed above.
| Property Name | Description |
event |
event type |
| Common Properties | Properties common to all event types |
environment |
The LaunchDarkly environment ID corresponding to event |
project |
The LaunchDarkly project ID corresponding to the event |
key |
The 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 | |
value |
The value the flag evaluated to |
flagVersion |
The version of the flag when it was evaluated |
reasonKind |
The evaluation reason for the flag. |
prereqOf |
Set 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. |
default |
Indicates whether the flag value was the result of the default variation being selected |
variation |
The variation of the flag requested. Flag variation values are stored in an array. This value corresponds to the index of the variation the array. Boolean flags show as 0 or 1 for true and false, and other flag types are numbered starting with 0 for their different variations. |
| Page View Event Properties | |
url |
The URL the user was on when the flag was evaluated |
| Click Event Properties | |
url |
The URL the user was on when the flag was evaluated |
selector |
Contains the CSS selector corresponding to the click event |
| Custom Event Properties | Custom 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 you experience any issues with how the events arrive in Segment, contact the LaunchDarkly team.
This page was last modified: 20 Mar 2024
Need support?
Questions? Problems? Need more info? Contact Segment Support for assistance!