Flagship.io Destination

Flagship.io lets engineering teams deploy continuously and monitor the impact of features on technical infrastructure. It also enables product teams to control how features are released and how they impact user experience and business KPIs.

Flagship.io maintains this destination. For any issues with the destination, contact the Flagship Support team.

Getting Started

1. From the Destinations catalog page in the Segment App, click Add Destination.
2. Search for Flagship.io in the Destinations Catalog, and select the Flagship.io destination.
3. Choose which Source should send data to the Flagship.io destination.
4. Go to the Flagship.io settings interface under Settings > Integrations and choose Segment in the dropdown. Click Add Tool and copy the API key displayed.
5. Enter the API Key in the Flagship.io destination settings in Segment.

Supported methods

Flagship.io supports the following methods as specified in the Segment Spec.

Identify

Send Identify calls to the Flagship.io webhook. For example:

analytics.identify('userId123', {
  email: 'john.doe@example.com',
  trait1: 1,
  trait2: "test",
  trait3: true
  },    
});

Segment sends Identify calls to Flagship.io as an identify event. The Flagship.io data engine then ingests the different traits associated to the identified user.

The received traits are available in the Flagship use case builder.

Group

Send Group calls to Flagship.io webhook. The Flagship.io data engine then ingests the different traits associated to the identified group. For example:

analytics.group("0e8c78ea9d97a7b8185e8632", {
  name: "Initech",
  industry: "Technology",
  employees: 329,
  plan: "enterprise",
  "total billed": 830
});

Segment sends Track calls to Flagship.io as a group event. The Flagship.io data engine then ingests the different traits associated to the identified user.

The received traits are available in the Flagship use case builder.

Engage

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.

Settings

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