Skip to content

Commit 187df95

Browse files
tcgilbertmarkzegarelli
andauthored
update 1flow destination name (#3866)
* update 1flow destination name * Hide and unpublish old page * Add redirect Co-authored-by: markzegarelli <[email protected]>
1 parent 28fde75 commit 187df95

File tree

2 files changed

+73
-0
lines changed

2 files changed

+73
-0
lines changed

src/connections/destinations/catalog/1flow-analytics/index.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,8 @@
11
---
22
title: 1Flow Analytics Destination
33
id: 62bf80378e3d0241ab190594
4+
hidden: true
5+
published: false
46
---
57

68
[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.
Lines changed: 71 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,71 @@
1+
---
2+
title: 1Flow Destination
3+
id: 62bf80378e3d0241ab190594
4+
redirect_from:
5+
- '/connections/destinations/catalog/1flow-analytics'
6+
---
7+
8+
[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.
9+
10+
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.
11+
12+
This destination is maintained by 1Flow. For any issues with the destination, [contact the 1Flow Support team](mailto:[email protected]).
13+
14+
## Getting Started
15+
16+
1. From the Destinations catalog page in the Segment App, click **Add Destination**.
17+
2. Search for **1Flow** in the Destinations Catalog, and select the **1Flow** destination.
18+
3. Choose which Source should send data to the 1Flow destination.
19+
4. Go to the [1Flow dashboard](https://dashboard.1flow.app/){:target="\_blank"} and find the **API Key** in Project Settings.
20+
5. Enter the **API Key** in the 1Flow destination settings in Segment.
21+
22+
## Supported methods
23+
24+
1Flow supports the following methods, as specified in the [Segment Spec](/docs/connections/spec).
25+
26+
### Identify
27+
28+
Send [Identify](/docs/connections/spec/identify) calls to create new user profile or update existing users with new trait values. For example:
29+
30+
```js
31+
analytics.identify("userId123", {
32+
33+
});
34+
```
35+
36+
Segment sends Identify calls to 1Flow as an `identify` event.
37+
38+
### Track
39+
40+
Send [Track](/docs/connections/spec/track) calls to record user behavior in your app. For example:
41+
42+
```js
43+
analytics.track("Login Button Clicked");
44+
```
45+
46+
Segment sends Track calls to 1Flow as a `track` event.
47+
48+
### Page
49+
50+
Send [Page](/docs/connections/spec/page) calls to record which website pages users have visited. For example:
51+
52+
```js
53+
analytics.page("Pricing", {
54+
title: "Segment Pricing",
55+
url: "https://segment.com/pricing",
56+
path: "/pricing",
57+
referrer: "https://segment.com/warehouses",
58+
});
59+
```
60+
61+
Segment sends Page calls to 1Flow as a `page_[name]` event. (or `page_view` if a page name isn’t provided).
62+
63+
### Screen
64+
65+
Send [Screen](/docs/connections/spec/screen) calls to record which mobile app screens users have viewed. For example:
66+
67+
```obj-c
68+
[[SEGAnalytics sharedAnalytics] screen:@"Home"];
69+
```
70+
71+
Segment sends Screen calls to 1Flow as a `screen_[name]` event (or `screen_view` if a screen name isn't provided).

0 commit comments

Comments
 (0)