Skip to main content

What this is

The LaunchDarkly destination sends audiences out of Zeotap CDP and into LaunchDarkly, where each audience arrives as a segment that a feature flag can target. Nothing flows back the other way: the Integrations Master List records LaunchDarkly as a Destination only, so there is no LaunchDarkly source page to read alongside this one. LaunchDarkly is a feature management platform that lets development teams deliver, control and measure their software through feature flags, and run experiments on any flag. A feature flag — also called a feature toggle or feature switch — turns a feature of an application on or off at runtime, so a team can control who sees a feature without deploying new code. Once a Zeotap CDP audience has arrived as a segment, you can add a targeting rule on a flag that serves a particular variation to everyone in that segment. Zeotap CDP ships two separate LaunchDarkly destinations:
  • LaunchDarkly — this page. A batch destination, linked to an audience in the Audiences application, that sends the audience as a segment.
  • LaunchDarkly Real Time Integration — a real-time destination, attached to a Send to Destinations node in a journey, that sends identifiers as customers flow through.
Both send data in the same direction — out of Zeotap CDP to LaunchDarkly. Choose the one that matches where you are activating from, Audiences or Journeys.
The destination catalogue in Zeotap CDP lists this integration as Launch Darkly, as two words. Search for it that way when you create the destination.

Supported identifiers and actions

This integration supports Custom IDs — any ID that is activated within LaunchDarkly, such as User IDs, CRM IDs or any other ID you hold for the same person on both sides. The destination exposes a single action. Because delta upload and delete are not supported, each refresh sends the audience membership as it stands when the refresh runs.

Prerequisites

In Zeotap CDP:
  • An account with permission to create and edit destinations. For the wider destination model — platforms, actions and mappings — see Destinations.
  • An audience holding the customers you want to target.
In LaunchDarkly:
  • A LaunchDarkly account.
  • Access to Settings → Authorization, so you can create the access token described below.
  • Access to Settings → All projects, so you can read the Client-side ID of the environment you want to send to.
  • A feature flag to hang the targeting rule on, in the project and environment you are sending to.
Gather both LaunchDarkly values — the access token and the Client-side ID — before you start creating the destination, because the destination form asks for both.

Get the LaunchDarkly details you need

Access token

An access token in LaunchDarkly authenticates calls and controls what they may do. Create one for this integration as follows.
1
Log into the LaunchDarkly console and navigate to Settings → Authorization.
2
Under Access tokens, click Create token.
The LaunchDarkly Authorization page, showing an empty Authorized applications panel above an Access tokens panel that lists two existing service tokens with the Writer role, with Authorization highlighted in the left navigation and the Create token button highlighted on the right

The Authorization page of LaunchDarkly Settings, with Create token highlighted

3
In the Create access token window that appears, provide the following details:a. Enter a Name for your access token.b. Choose Writer as the Role for the token from the drop-down menu.c. Choose the API version for the token from the drop-down menu. By default, API requests you send using this token use this API version. For how API versioning works in LaunchDarkly, see LaunchDarkly’s own Versioning documentation.d. If you are an Enterprise customer, select the This is a service token checkbox if you want to create a service token.
LaunchDarkly Create access token dialog showing a Name field containing the placeholder entry test, a Role drop-down set to Writer, an API version drop-down, a This is a service token checkbox with explanatory text, and a Save token button

The Create access token dialog, with the Name, Role and API version fields and the service token checkbox

4
Review the details and click Save token. The new token is listed on the Authorization page.Copy the token and store it somewhere safe now — LaunchDarkly hides the value once you leave the page, and you enter it in the Access Token field when you create the destination in Zeotap CDP. If you lose it, create a replacement token rather than trying to read the old one back.
LaunchDarkly Access tokens list showing three service token rows, each carrying the Writer role and a Created by you creator, with the newest row highlighted and a Copy and save this token callout below it warning that the token is hidden after you leave the page

The Access tokens list after saving, with the new token's Copy and save this token callout

Client-side ID

The Client-side ID identifies one environment of one LaunchDarkly project, so the value you copy decides which environment your audiences land in. Obtain it as follows.
1
Log into your LaunchDarkly account and navigate to Settings → All projects.
2
Select the project you want to link to Zeotap CDP. It opens on All environments.
The LaunchDarkly project list, showing a projects table with Name, Tags and Environments columns and one project row

The LaunchDarkly project list, reached from Settings

3
Click the … menu next to the environment you want to link with Zeotap CDP, select View SDK keys, and copy the value under Client-side IDs. You enter it in the Client Side ID field when you create the destination.
The LaunchDarkly SDK keys page for the Production environment, reached from Settings, showing a Client-side IDs section above the SDK keys and Mobile keys sections, with the client-side ID value redacted

The SDK keys page of a LaunchDarkly environment, with the Client-side IDs section at the top

A project can hold several environments, and each one has its own Client-side ID. Copy the ID of the environment whose feature flags you intend to target — a production audience sent with a test environment’s ID will only ever appear in that test environment.

Create the LaunchDarkly destination

1
Log in to the Zeotap CDP app and go to Integrate → Destinations.
2
Click + Create Destination.
Zeotap CDP Integrate Destinations screen listing existing destinations in a table, with the Create Destination button highlighted at the top right

The Zeotap CDP Destinations listing, with Create Destination highlighted

3
Under All Destinations, search for Launch Darkly.
Zeotap CDP All Destinations catalogue with the Search for a Destination box highlighted above a grid of destination tiles

The All Destinations catalogue, with the Search for a Destination box highlighted

4
Click the Launch Darkly tile. A panel describing the destination appears on the left, and the fields the integration needs appear on the right. Enter:a. A Destination Name. Choose a name that identifies the LaunchDarkly account and environment it connects to, so the destination is easy to pick out when you link an audience.b. The Access Token you created in the Authorization tab of your LaunchDarkly account — see Access token.c. The Client Side ID of the LaunchDarkly environment you want to send to — see Client-side ID.d. Review the values you entered, then click Next.
Zeotap CDP Enter Destination Details screen for Launch Darkly, showing Destination Name, Access Token and Client Side ID fields holding placeholder entries, a description panel for the destination on the left, a Destination Details and Mapping progress indicator, and a Next button

The Enter Destination Details step for Launch Darkly, with the Destination Name, Access Token and Client Side ID fields

5
On the Mapping screen, choose the action and the field mapping:a. Under Choose your Action, select Send Identifiers to Launch Darkly.b. Under Map the Fields, map the Catalogue field that carries the ID to the matching LaunchDarkly destination field — in the capture below, the Catalogue field User Id is mapped to the destination field User ID under Identifiers. The output identifiers the platform accepts are shown by default, and you can edit, add or remove an identifier from the list; for the rules that govern actions and mappings across every destination, see Define the mapping.
Zeotap CDP Mapping screen with Send Identifiers to Launch Darkly selected under Choose your Action, and a Map the Fields table under an Identifiers heading pairing the Catalogue field User Id with the destination field User ID, above a Create Destination button

The Mapping step, with Send Identifiers to Launch Darkly chosen and a Catalogue field mapped to a LaunchDarkly destination field

6
Click Create Destination. The destination is then listed in the Audiences application, ready to be linked to an audience.
For the two entry points into destination configuration and what each part of the configuration does, see Configure a destination. Once the destination is created, link it to the audience you want to activate from the Audiences application — see Activate in Audiences for the end-to-end workflow, including refresh frequency and the output identifier mapping.
The terms Audiences and Segments are used interchangeably to refer to customer cohorts belonging to a specific category. For example, an audience or a segment can be a specific group of customers who are over 18 years of age and have performed an addToCart event within the last 30 days.
The destination form notes that segments can take up to two business days to become available on the LaunchDarkly side. Allow for that before treating a missing segment as a failure.

Target the segment on a feature flag

Once an audience has been linked to the destination and the segment has arrived, add a targeting rule in LaunchDarkly so a flag serves a variation to the people in it.
1
Log into LaunchDarkly and navigate to Feature flags.
2
Choose the feature flag you want to target from the list.
LaunchDarkly Feature flags list showing one flag row with its key, creation date, serving variation, targeting-modified date and an on-off toggle, with Feature flags highlighted in the left navigation

The LaunchDarkly Feature flags list

3
On the flag’s Targeting tab, click the Add rule drop-down and choose Target segments. This creates a new rule section.
LaunchDarkly flag Targeting tab with the Add rule drop-down open, listing Target segments, Target individuals, Target mobile, Build a custom rule and Set prerequisites, with Target segments highlighted above an existing rule and the Default rule section

The Add rule drop-down on a flag's Targeting tab, with Target segments highlighted

4
In the new rule, open the Segments drop-down to see the audiences pushed from Zeotap CDP.
A Zeotap CDP audience only appears in this list once the LaunchDarkly destination has been created and linked to at least one audience.
5
Choose the audience you want the flag to apply to, set the variation the rule serves, and save the flag.
LaunchDarkly flag targeting rule with a Context is in Segment condition above a second rule whose Segments drop-down is open, showing a Most targeted segments group and a Recently updated segments group listing several named segments with their last-modified dates

The Segments drop-down on a targeting rule, listing the segments available to the flag

Verify the audience reached LaunchDarkly

Check both sides after the first refresh has run.
  1. In Zeotap CDP — open the audience–destination pair in the Audiences application and confirm the run has completed with a non-zero qualified count. For what the statuses mean across destinations, see Verify the activation worked.
  2. In LaunchDarkly — open a feature flag in the target environment, add or edit a rule that targets segments, and confirm the audience is listed in the Segments drop-down. The list groups the most targeted segments above the recently updated ones, with the date each was last modified, so you can tell a fresh delivery from a stale one.
Allow up to two business days between a successful Zeotap CDP run and the segment appearing in LaunchDarkly.

Troubleshoot the LaunchDarkly destination

For delivery errors that are not specific to LaunchDarkly — no customers qualified, a terminated refresh, a rejected payload — see Why deliveries fail and When to contact support.

FAQ

They are two integrations for the same vendor, distinguished by where you activate from. LaunchDarkly — this page — is a batch destination linked to an audience in the Audiences application. LaunchDarkly Real Time Integration is a real-time destination attached to a Send to Destinations node in a journey. Both send data out of Zeotap CDP to LaunchDarkly.
The one whose Client-side ID you entered on the destination. A LaunchDarkly project can hold several environments and each has its own Client-side ID, so the value on the destination decides where the segments appear. To send to more than one environment, create a separate destination for each.
No. Link the audience to the destination and the segment becomes available to target on the LaunchDarkly side; you then add the targeting rule on the flag that should use it.
No. None of the three is supported on this integration, so each refresh sends the audience as it stands at that moment. See Delta upload and delete functions for the destinations where delta upload and delete are available.
Yes. The destination stores the LaunchDarkly credential, the environment and the mapping, so it can be linked to as many audiences as you need. Each audience arrives as its own segment and can be targeted by a different flag.

Next steps

Last modified on November 5, 2026