|
| 1 | +--- |
| 2 | +title: 1Flow (Actions) Destination |
| 3 | +--- |
| 4 | + |
| 5 | +[1Flow](https://1flow.ai/?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. |
| 6 | + |
| 7 | +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 |
| 8 | + |
| 9 | +This destination is maintained by 1Flow. For any issues with the destination, [contact their Support team ](mailto:[email protected]). |
| 10 | + |
| 11 | +## Getting started |
| 12 | + |
| 13 | +1. From the Segment web app, click **Catalog**, then click **1Flow**. |
| 14 | +2. Find the Destinations Actions item in the left navigation, and click it. |
| 15 | +3. Click **Configure 1Flow**. |
| 16 | +4. Select an existing Source to connect to 1Flow (Actions). |
| 17 | +5. Copy 1Flow project key and paste it into the Connection Settings in Segment. |
| 18 | + |
| 19 | + |
| 20 | +## Supported methods |
| 21 | + |
| 22 | +### Identify |
| 23 | +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: |
| 24 | + |
| 25 | +```swift |
| 26 | +analytics. identify( userId: "[email protected]", traits: [ |
| 27 | + "name": "Peter Gibbons", |
| 28 | + |
| 29 | + "mobile": 1234567890 |
| 30 | +]) |
| 31 | +``` |
| 32 | +When you call identify method of segment, it will be equivalent to `logUser` of 1Flow. `userId` will be `userID` and `traits` will be `userDetails`. |
| 33 | + |
| 34 | +### Track |
| 35 | +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: |
| 36 | + |
| 37 | +```swift |
| 38 | +analytics.track(name: "ButtonClicked") |
| 39 | +``` |
| 40 | +Any value passed in `name`, will be eventName and if you have passed any event property, then it will be event `parameters`. |
| 41 | + |
| 42 | +### Screen |
| 43 | + |
| 44 | +Send [Screen](/docs/connections/spec/screen) calls to record which mobile app screens users have viewed. For example: |
| 45 | + |
| 46 | +```swift |
| 47 | +analytics.screen(title: "Home") |
| 48 | +``` |
| 49 | + |
| 50 | +Segment sends Screen calls to 1Flow as a `screen_[name]` event (or `screen_view` if a screen name isn't provided). |
0 commit comments