Send your event data from RudderStack to LaunchDarkly.
3 minute read
LaunchDarkly is a popular feature management platform that offers cutting-edge A/B testing and experimentation functionalities. It lets you efficiently automate and manage feature flags and improve overall product workflow and software quality.
RudderStack supports LaunchDarkly as a destination to which you can seamlessly send your data for flag management.
In the web device mode integration, that is, using JavaScript SDK as a source, RudderStack loads the LaunchDarkly native SDK from thehttps://unpkg.com/ domain.
Based on your website’s content security policy, you might need to allowlist this domain to load the LaunchDarkly SDK successfully.
Get started
Once you have confirmed that the source platform supports sending events to LaunchDarkly, follow these steps:
From your RudderStack dashboard, add a source. Then, from the list of destinations, select LaunchDarkly.
Assign a name to the destination and click Continue.
Connection settings
To successfully configure LaunchDarkly as a destination, you will need to configure the following settings:
Client-side ID: Enter the client-side ID of your LaunchDarkly project.
For more information on getting the LaunchDarkly client-side ID, refer to the FAQ section below.
Identify
The identify call lets you create or update a user in LaunchDarkly.
You must call identify before making any track or alias calls.
RudderStack assigns the userId to LaunchDarkly’s key field to uniquely identify a user.
key is the only required field in LaunchDarkly’s identify call. If no unique identifier is provided, RudderStack will automatically assign anonymousId as key.
Supported traits
The following table lists the supported fields for the traits object in the identify call:
Field
Type
Presence
Description
anonymous
Boolean
Optional
Must be set to true.
avatar
String
Optional
User’s avatar image URL.
country
String
Optional
Country associated with the user.
custom
Object
Optional
Additional attributes associated with the user.
email
String
Optional
User’s email address.
firstName
String
Optional
User’s first name.
ip
String
Optional
User’s IP address.
lastName
String
Optional
User’s last name.
name
String
Optional
User’s full name.
privateAttributeNames
String Array
Optional
List of attribute names (built-in or custom) marked as private and not sent to LaunchDarkly as analytics events.
secondary
String
Optional
User’s secondary identifier.
If you have chosen to bucket the users by a specific attribute, the secondary field can be used to further distinguish the users who are otherwise identical as per that attribute.
Track
The track call lets you record user events and send them to LaunchDarkly as custom conversion metrics for your experiments.
As mentioned above, you must call identify before sending any track events to LaunchDarkly.
A sample track call is as shown:
rudderanalytics.track("Test Event",{foo:"bar"});
Alias
The alias call lets you merge different identities of a known user. You can explicitly change the identity of a user via this call.
A sample alias call is shown below:
rudderanalytics.alias("newUserId","userId");
FAQ
Where do I get the LaunchDarkly Client-side ID?
To get your LaunchDarkly client-side ID, follow these steps:
This site uses cookies to improve your experience while you navigate through the website. Out of
these
cookies, the cookies that are categorized as necessary are stored on your browser as they are as
essential
for the working of basic functionalities of the website. We also use third-party cookies that
help
us
analyze and understand how you use this website. These cookies will be stored in your browser
only
with
your
consent. You also have the option to opt-out of these cookies. But opting out of some of these
cookies
may
have an effect on your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. This
category only includes cookies that ensures basic functionalities and security
features of the website. These cookies do not store any personal information.
This site uses cookies to improve your experience. If you want to
learn more about cookies and why we use them, visit our cookie
policy. We'll assume you're ok with this, but you can opt-out if you wish Cookie Settings.