Skip to content

Commit d324814

Browse files
[index.md] destination docs for new Flagshipio destination (#2861)
* [index.md] destination docs for new Flagshipio destination * [index.md] fix typo * update syntax Co-authored-by: stayseesong <[email protected]> * Apply suggestions from code review Co-authored-by: stayseesong <[email protected]> Co-authored-by: stayseesong <[email protected]>
1 parent a249629 commit d324814

File tree

1 file changed

+60
-0
lines changed
  • src/connections/destinations/catalog/flagshipio

1 file changed

+60
-0
lines changed
Lines changed: 60 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,60 @@
1+
---
2+
title: Flagship.io Destination
3+
rewrite: true
4+
id: 626153e34fb8f47a32f8deab
5+
---
6+
7+
[Flagship.io](https://www.Flagship.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} 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.
8+
9+
Flagship.io maintains this destination. For any issues with the destination, [contact the Flagship Support team](mailto:[email protected]).
10+
11+
## Getting Started
12+
13+
{% include content/connection-modes.md %}
14+
15+
1. From the Destinations catalog page in the Segment App, click **Add Destination**.
16+
2. Search for **Flagship.io** in the Destinations Catalog, and select the **Flagship.io** destination.
17+
3. Choose which Source should send data to the Flagship.io destination.
18+
4. Go to the [Flagship.io settings interface](https://app.flagship.io/env/c92t23fode700aontbvg/settings/integrations){:target="_blank"} under **Settings > Integrations** and choose **Segment** in the dropdown. Click **Add Tool** and copy the API key displayed.
19+
5. Enter the **API Key** in the Flagship.io destination settings in Segment.
20+
21+
## Supported methods
22+
23+
Flagship.io supports the following methods as specified in the [Segment Spec](/docs/connections/spec).
24+
25+
### Identify
26+
27+
Send [Identify](/docs/connections/spec/identify) calls to the Flagship.io webhook. For example:
28+
29+
```js
30+
analytics.identify('userId123', {
31+
32+
trait1: 1,
33+
trait2: "test",
34+
trait3: true
35+
},
36+
});
37+
```
38+
39+
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.
40+
41+
The received traits are available in the [Flagship use case builder](https://docs.developers.flagship.io/docs/getting-started-with-flagship#4-create-your-first-campaign-on-the-platform){:target="_blank"}.
42+
43+
44+
### Group
45+
46+
Send [Group](/docs/connections/spec/group) calls to Flagship.io webhook. The Flagship.io data engine then ingests the different traits associated to the identified group. For example:
47+
48+
```js
49+
analytics.group("0e8c78ea9d97a7b8185e8632", {
50+
name: "Initech",
51+
industry: "Technology",
52+
employees: 329,
53+
plan: "enterprise",
54+
"total billed": 830
55+
});
56+
```
57+
58+
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.
59+
60+
The received traits are available in the [Flagship use case builder](https://docs.developers.flagship.io/docs/getting-started-with-flagship#4-create-your-first-campaign-on-the-platform){:target="_blank"}.

0 commit comments

Comments
 (0)