LaunchDarkly Audiences Destination

1. In LaunchDarkly, navigate to Account settings and copy the client-side ID for the project and environment where you would like to create an Engage Audience synced segment.
2. In LaunchDarkly, create a service token with either a Writer role or a custom role. If your service token has a custom role, it must have the actions createSegment and updateIncluded to sync a segment from an Engage Audience. To learn how to create a service token, read Creating API access tokens.
3. From the Segment web app, navigate to Engage > Audiences. Ensure you are in the Engage space you plan to use with the LaunchDarkly Audiences destination. Either choose an existing Engage audience or create a new one. This is the audience you plan to sync with LaunchDarkly.
4. Navigate to Engage > Engage Settings and click Destinations. Ensure you are still in the correct Engage space.
5. Search for LaunchDarkly Audiences and select the destination. Click Add destination.
6. On the Select Source screen, your Engage space should already be selected as the source. Click Confirm Source.
7. On the Destination Settings tab, name your destination and provide your LaunchDarkly client-side ID and service token.
8. Toggle Enable Destination on and click Save Changes.
9. Navigate to the Mappings tab, click New Mapping, and select the Sync Engage Audience to LaunchDarkly pre-built mapping.
10. Under Select mappings, modify the default mappings as needed. In most cases, you shouldn't need to make any changes.
11. Click Save.
12. Ensure the Status toggle on the Mappings tab is enabled.

LaunchDarkly Audiences has the following presets

Build your own Mappings. Combine supported triggers with the following LaunchDarkly Audiences-supported actions:

• Sync Audience

Sync Engage Audiences to LaunchDarkly segments

Sync Audience is a Cloud action. The default Trigger is type = "identify" or type = "track"

You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.

For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to false.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

Segment lets you change these destination settings from the Segment app without having to touch any code.