This topic explains how to create segments that sync with an Amplitude cohort. Segment syncing lets you import audiences from Amplitude to LaunchDarkly to more efficiently target and deliver feature flags. You manage the membership of these segments in Amplitude.
The primary benefit of syncing segments with Amplitude is the automatic syncing between Amplitude and LaunchDarkly. This lets you concentrate more on deploying features and less on managing end users between platforms.
The general prerequisites for synced segments apply to syncing segments with Amplitude cohorts.
In order to sync segments with Amplitude cohorts, you must additionally meet the following prerequisites:
With synced segments, you can connect a new or existing Amplitude cohort to LaunchDarkly. LaunchDarkly interprets this cohort as a synced segment, which makes it convenient for you to target flags to specific context groups or demographics.
You can configure segments to sync automatically in LaunchDarkly at regular intervals, which keeps them current with the existing cohort. We recommend setting up your segment to sync every hour. The process for doing this is documented below.
By syncing segments, you can deliver flags to the right context groups precisely and on time.
To configure a segment that syncs with an Amplitude cohort, you must choose a cohort in Amplitude and tell it to send data to LaunchDarkly. When you do this correctly, the cohort appears as a segment in LaunchDarkly.
To do this, first add LaunchDarkly as a destination and then sync the cohort to the LaunchDarkly destination.
To create a destination in Amplitude, you must have Admin or Manager credentials.
To add LaunchDarkly as a destination:
If LaunchDarkly is not on the destinations list, contact your Amplitude Customer Success Manager to enable the LaunchDarkly integration. If you do not have Admin or Manager credentials Amplitude displays an error message:
Enter a destination name and add the access token and client-side ID for your LaunchDarkly project and environment.
Select a matching user property in Amplitude to map to LaunchDarkly’s User Key. This will most likely be your Amplitude user ID but it depends on your Amplitude configuration:
Users in Amplitude must have a value in the field you map to the LaunchDarkly User Key to be included in a LaunchDarkly segment.
Click save.
Verify that LaunchDarkly shows as “Connected”:
LaunchDarkly is now an Amplitude data destination.
To connect a cohort to LaunchDarkly:
Click next. The destination configuration screen appears.
Select your LaunchDarkly destination and set the scheduled sync frequency. An hourly sync frequency ensures your segments are kept up to date with your Amplitude cohorts. A one-time sync exports the cohort into a segment once:
Click Sync.
The sync process begins and might take a few minutes to complete:
When the sync finishes Amplitude sends you an email and LaunchDarkly appears in the list of Destinations connected to that cohort.
Users in Amplitude must have a value in the field you map to the LaunchDarkly User Key field, typically the Amplitude user ID, to be included in a LaunchDarkly segment. The value in the LaunchDarkly User Key field becomes the context key in LaunchDarkly. Any Amplitude users missing a value in the mapped field are not included in the LaunchDarkly segment. To learn how to view the contexts in a segment synced with Amplitude, read View synced Amplitude cohorts in LaunchDarkly.
To check for users in your Amplitude cohort missing user IDs, you can download a CSV file with user ID information. Here’s how:
user_id. If you mapped user_id to the LaunchDarkly User Key, any user without a value in this column is not included in the LaunchDarkly segment.You can view your synced Amplitude cohort as a segment in LaunchDarkly. It appears on the Segments list with the Amplitude logo next to its name.
Click into that segment’s details page for more information about its targeting. You cannot edit rules for a segment synced with an Amplitude cohort because they are managed by Amplitude.