|
| 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). |
0 commit comments