Skip to content

Commit fe18c24

Browse files
authored
Merge pull request #2840 from ldhenry/ld-actions-docs
Add LaunchDarkly (Actions) documentation.
2 parents 35ce83b + c0f486e commit fe18c24

File tree

1 file changed

+53
-0
lines changed
  • src/connections/destinations/catalog/actions-launchdarkly

1 file changed

+53
-0
lines changed
Lines changed: 53 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
---
2+
title: LaunchDarkly (Actions) Destination
3+
hide-boilerplate: true
4+
hide-dossier: true
5+
---
6+
7+
{% include content/plan-grid.md name="actions" %}
8+
9+
[LaunchDarkly](https://launchdarkly.com) is a feature management platform that empowers development teams to safely deliver, control, and measure their software through feature flags.
10+
11+
With LaunchDarkly, you can run experiments on any feature flag. This destination allows you to connect existing Segment events to LaunchDarkly custom metrics for use in LaunchDarkly experiments.
12+
13+
> success ""
14+
> **Good to know**: This page is about the [Actions-framework](/docs/connections/destinations/actions/) LaunchDarkly Segment destination. There's also a page about the [non-Actions LaunchDarkly destination](/docs/connections/destinations/catalog/launchdarkly-events/). Both of these destinations receives data from Segment.
15+
16+
<!-- This include describes the requirement of A.js 2.0 or higher for Actions compatibility, and is required if your destination has a web component. -->
17+
18+
{% include content/ajs-upgrade.md %}
19+
20+
<!-- In the section below, explain the value of this actions-based destination over the classic version, if applicable. If you don't have a classic version of the destination, remove this section. -->
21+
22+
## Benefits of LaunchDarkly (Actions) vs LaunchDarkly Classic
23+
24+
LaunchDarkly (Actions) provides the following benefits over the classic LaunchDarkly destination:
25+
26+
- **Improved customization**. You determine the mapping between the data Segment receives from your source and the data Segment sends to LaunchDarkly. For example, you can map an arbitrary event property to the LaunchDarkly metric key.
27+
- **Increased transparency**. You can see the data that is sent to LaunchDarkly and when Segment sends it. Additionally, you can subscribe to alerts when the delivery rate to LaunchDarkly dips below a configurable threshold.
28+
29+
<!-- The section below explains how to enable and configure the destination. Include any configuration steps not captured below. For example, obtaining an API key from your platform and any configuration steps required to connect to the destination. -->
30+
31+
## Getting started
32+
33+
To get started with LaunchDarkly (Actions):
34+
1. In LaunchDarkly, navigate to [Account settings](https://app.launchdarkly.com/settings/projects) and copy the client-side ID for the project and environment that you would like to connect to Segment.
35+
2. From the Segment web app, click **Catalog**, then click **Destinations**.
36+
3. Search for **LaunchDarkly (Actions)** and select it.
37+
4. Click **Configure LaunchDarkly**.
38+
5. Select the Source you want to connect to LaunchDarkly (Actions).
39+
6. Paste the LaunchDarkly client-side ID you copied in step 1 into the **LaunchDarkly client-side ID** field on the destination settings page.
40+
41+
<!-- The line below renders a table of connection settings (if applicable), Pre-built Mappings, and available actions. -->
42+
43+
{% include components/actions-fields.html %}
44+
45+
## Creating LaunchDarkly metrics
46+
47+
In order to take full-advantage of the LaunchDarkly (Actions) Destination, you need to create metrics in LaunchDarkly that correspond to Segment track events. Read [Creating metrics](https://docs.launchdarkly.com/home/experimentation/metrics/index){:target="_blank"} to learn how to create metrics in LaunchDarkly.
48+
49+
<!-- If applicable, add information regarding the migration from a classic destination to an Actions-based version below -->
50+
51+
## Migration from the classic LaunchDarkly destination
52+
53+
Be sure to disconnect the classic LaunchDarkly destination before enabling the LaunchDarkly (Actions) destination to avoid duplicate experimentation events in LaunchDarkly.

0 commit comments

Comments
 (0)