Skip to content

Commit c531277

Browse files
authored
Merge pull request #685 from segmentio/repo-sync
repo sync
2 parents 937b68e + fd8032f commit c531277

File tree

2 files changed

+152
-4
lines changed
  • src/connections/destinations/catalog

2 files changed

+152
-4
lines changed
Lines changed: 70 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,70 @@
1+
---
2+
title: 1Flow Analytics Destination
3+
id: 62bf80378e3d0241ab190594
4+
---
5+
6+
[1Flow](https://1flow.app/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) is a leading in-app user survey and messaging platform for Mobile app and SaaS businesses.
7+
8+
Using 1Flow, you can reach users _in-the-moment_ while they are interacting with your website or application, to collect highly contextual user insights that help you improve your product offering and customer experience.
9+
10+
This destination is maintained by 1Flow. For any issues with the destination, [contact the 1Flow Support team](mailto:[email protected]).
11+
12+
## Getting Started
13+
14+
15+
1. From the Destinations catalog page in the Segment App, click **Add Destination**.
16+
2. Search for **1Flow** in the Destinations Catalog, and select the **1Flow** destination.
17+
3. Choose which Source should send data to the 1Flow destination.
18+
4. Go to the [1Flow dashboard](https://dashboard.1flow.app/){:target="\_blank"} and find the **API Key** in Project Settings.
19+
5. Enter the **API Key** in the 1Flow destination settings in Segment.
20+
21+
## Supported methods
22+
23+
1Flow 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 create new user profile or update existing users with new trait values. For example:
28+
29+
```js
30+
analytics.identify("userId123", {
31+
32+
});
33+
```
34+
35+
Segment sends Identify calls to 1Flow as an `identify` event.
36+
37+
### Track
38+
39+
Send [Track](/docs/connections/spec/track) calls to record user behavior in your app. For example:
40+
41+
```js
42+
analytics.track("Login Button Clicked");
43+
```
44+
45+
Segment sends Track calls to 1Flow as a `track` event.
46+
47+
### Page
48+
49+
Send [Page](/docs/connections/spec/page) calls to record which website pages users have visited. For example:
50+
51+
```js
52+
analytics.page("Pricing", {
53+
title: "Segment Pricing",
54+
url: "https://segment.com/pricing",
55+
path: "/pricing",
56+
referrer: "https://segment.com/warehouses",
57+
});
58+
```
59+
60+
Segment sends Page calls to 1Flow as a `page_[name]` event. (or `page_view` if a page name isn’t provided).
61+
62+
### Screen
63+
64+
Send [Screen](/docs/connections/spec/screen) calls to record which mobile app screens users have viewed. For example:
65+
66+
```obj-c
67+
[[SEGAnalytics sharedAnalytics] screen:@"Home"];
68+
```
69+
70+
Segment sends Screen calls to 1Flow as a `screen_[name]` event (or `screen_view` if a screen name isn't provided).
Lines changed: 82 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,85 @@
11
---
2-
title: 'Akita User Tracking Destination'
3-
hidden: true
2+
title: Akita User Tracking Destination
43
id: 5fc76defdde39f67d4fa85de
5-
published: false
6-
beta: true
74
---
5+
6+
[Akita](https://www.akitaapp.com.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} provides Customer Success Management tools for Software-as-a-Service applications--helping you nurture, retain and grow your customer base.
7+
8+
This destination is maintained by Akita. For any issues with the destination, contact [Akita support](mailto:[email protected]).
9+
10+
> info ""
11+
> The Akita Destination is in beta, which means that they are still actively developing the destination. To join their beta program, or if you have any feedback to help improve the Akita Destination and its documentation, [contact the Akita support team](mailto:[email protected])!
12+
13+
## Getting Started
14+
15+
1. From the Destinations catalog page in the Segment App, click **Add Destination**.
16+
2. Search for "Akita" in the Destinations Catalog, and select the "Akita User Tracking" destination.
17+
3. Choose which Source should send data to the "Akita User Tracking" destination.
18+
4. Go to the ["Connect Segment" Page](https://beta.akitaapp.com/segment){:target="_blank"}, find and copy the "Segment.com API Key".
19+
5. Enter the "API Key" in the "Akita User Tracking" destination settings in Segment.
20+
21+
## Identify
22+
23+
If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](/docs/connections/spec/identify/) to learn about what it does. An example call would look like:
24+
25+
```js
26+
analytics.identify("contact_123", {
27+
28+
groupId: "account_123" /** Optional **/,
29+
});
30+
```
31+
32+
Segment sends Identify calls to Akita as a `contact` event.
33+
34+
You may find a list of useful information to send as traits in your Identify call in the [Segment > Configure](https://beta.akitaapp.com/segment){:target="_blank"} tab in Akita.
35+
36+
Akita adds contacts described using Identify events as Contacts associated with the correct account.
37+
38+
> success ""
39+
> Akita is primarily an Account management tool. All Contacts in Akita must be associated with one-and only one-Account. You must also use the Segment Group event (see below).
40+
41+
For best results, Akita recommends you also send the `groupId` (the identifier you send with Group) as a trait in all Identify events. This allows Akita to identify the Contact if you have not yet made the required Group call.
42+
43+
## Group
44+
45+
If you aren't familiar with the Segment Spec, take a look at the [Group method documentation](/docs/connections/spec/group/) to learn about what it does. An example call would look like:
46+
47+
```js
48+
analytics.group("account_123", {
49+
name: "Initech",
50+
plan: "Enterprise",
51+
});
52+
```
53+
54+
Segment sends Group calls to Akita as an `account` event.
55+
56+
You may find a list of useful information to send as traits in your Group call in the [Segment > Configure](https://beta.akitaapp.com/segment){:target="_blank"} tab in Akita.
57+
58+
Accounts described using the Group event are added to Akita as Accounts.
59+
60+
> info ""
61+
> Groups identified through Segment Group events become Accounts in Akita.
62+
63+
## Track
64+
65+
If you aren't familiar with the Track Spec, take a look at the [Track method documentation](/docs/connections/spec/track/) to learn about what it does. An example call would look like:
66+
67+
```js
68+
analytics.track("search:submit");
69+
```
70+
71+
Segment sends Track calls to Akita as a `event` event.
72+
73+
## Page
74+
75+
If you aren't familiar with the Page Spec, take a look at the [Page method documentation](https://segment.com/docs/connections/spec/page/) to learn about what it does. An example call would look like:
76+
77+
```js
78+
analytics.page();
79+
```
80+
81+
Segment sends Page calls to Akita as a `page` event.
82+
83+
> success ""
84+
> You must send either `event` or `page` events (or both) for Akita to recognize and store your users Sessions.
85+

0 commit comments

Comments
 (0)