Synced segments capability

Overview

This topic explains how to use the synced segments integration framework capability.

About synced segments

In LaunchDarkly, segments are lists of contexts that are used to manage flag targeting behavior in bulk. As a partner, you can use the synced segments integration framework capability to create and synchronize resources contained in external services, such as Amplitude cohorts or Segment Audiences, with LaunchDarkly segments. To learn more about segments, read Segments.

The syncedSegment capability consists of a request parser. The properties of the parser describe the information about the segment to create or update.

Many of the parser properties are required, for example, the properties that specify the name and ID of the cohort you are updating.

Then, you have three options for how to send cohort information:

• Use a boolean property to indicate whether a member should be added or removed
• Use separate named arrays, one for members being added and one for members being removed
• Use a single action property to indicate whether the set of members should be added or removed

The combination of the request parser’s memberArrayPath, addMemberArrayPath, removeMemberArrayPath, and memberArrayParser properties describe which option you are using and where the integration framework can expect to find the cohort information.

Request parser properties

The following properties specify the requestParser:

The following properties specify the embedded memberArrayParser:

Examples

The following sections contain examples of different types of request bodies and the manifest definitions of synced segment capabilities that would successfully parse them.

Boolean property

In the request body, use a boolean property to indicate whether a member is added or removed:

1
    {
2
      "environmentId": "abcd123",
3
      "contextKind": "organization",
4
      "batch": [
5
        {
6
            "userId": "user-1234",
7
    		"cohortName": "Segment 1234",
8
        	"cohortId": "segment-1234",
9
        	"cohortUrl":  "https://example.com",
10
        	"value": true
11
        },
12
        {
13
            "userId": "user-5678",
14
            "cohortName": "Segment 1235",
15
            "cohortId": "segment-12345",
16
            "cohortUrl":  "https://example.com",
17
            "value": false
18
        }
19
      ]
20
    }

Separate named arrays

In the request body, use separate named arrays containing lists of members to add and remove. In the manifest, the memberArrayParser describes how to parse the addMemberArrayPath and removeMemberArrayPath arrays:

1
    {
2
      "id_token": "CustomerIdToken",
3
      "action_type": "segment.users.sync",
4
      "customer_config": {
5
        "fields": [
6
          {
7
            "field_id": "workspace",
8
            "field_display_name": "Workspace",
9
            "value": {
10
              "id": "abcd123",
11
              "display_name": "Workspace 1"
12
            }
13
          }
14
        ]
15
      },
16
      "data": {
17
        "segment": {
18
          "id": "segment-1234",
19
          "name": "Segment 1234"
20
        },
21
        "add": [
22
          {
23
            "id": "user-123"
24
          },
25
          {
26
            "id": "user-456"
27
          }
28
        ],
29
        "remove": [
30
          {
31
            "id": "user-789"
32
          },
33
          {
34
            "id": "user-101112"
35
          }
36
        ]
37
      }
38
    }

Single property

In the request body, use a single action property for the entire batch to indicate whether the batch should be added or removed:

1
{
2
  "action": "add_members",
3
  "parameters": {
4
    "integration_project_id": "abcd123",
5
    "integration_cohort_name": "Segment 1234",
6
    "integration_cohort_id": "segment-1234",
7
    "integration_cohort_description": "description",
8
    "integration_session_id": "integration_session_id",
9
    "members": [
10
      {
11
        "email": "user-1234@customer.com",
12
        "integration_distinct_id": "user-1234",
13
        "first_name": "John",
14
        "last_name": "Doe",
15
        "phone_number": "xxx-xxx-xxxx"
16
      },
17
      {
18
        "email": "user-5678@customer.com",
19
        "integration_distinct_id": "user-5678",
20
        "first_name": "Jane",
21
        "last_name": "Doe",
22
        "phone_number": "xxx-xxx-xxxx"
23
      }
24
    ]
25
  }
26
}

Response codes and custom responses

By default, LaunchDarkly returns one of the following response codes:

• 204, success
• 400, parsing problem
• 403, unauthorized
• 409, conflict
• 429, rate limited, read Rate limiting for details on the X-Ratelimit-Reset header
• 500, internal error

If you require a custom response, you can specify that with the jsonResponseBody in the syncedSegments object in your integration manifest. The jsonResponseBody supports Handlebars templating directly in the manifest.

Here is an example manifest excerpt that specifies a jsonResponseBody:

1
    "capabilities": {
2
        "syncedSegment": {
3
          "requestParser": {
4
            ...
5
          },
6
          "jsonResponseBody": "{ \"environmentId\": \"{{requestBody.environmentId}}\", \"projectKey\": \"{{projectKey}}\", \"envKey\": \"{{environmentKey}}\", \"segmentKey\": \"{{segmentKey}}\", \"segmentUrl\": \"{{segmentUrl}}\", {{#if errorMessage}}\"status\":\"failure\", \"error\": {\"message\": \"{{{errorMessage}}}\", \"code\": {{statusCode}} }{{else}}\"status\": \"success\"{{/if}} }"
7
        }
8
      }

Testing

After you have an initial implementation of your synced segments capability, you can test it using LaunchDarkly’s integration validation server. To learn more, read Validating an integration.