You're in the right place! Segment documentation is now part of Twilio Docs. The content you are used to is still here—just in a new home with a refreshed look.

1Flow Destination

Destination Info

Accepts Page, Alias, Identify and Track calls.
Refer to it as 1Flow in the Integrations object
This integration is partner owned. Please reach out to the partner's support for any issues.

1Flow is a leading in-app user survey and messaging platform for Mobile app and SaaS businesses.

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.

This destination is maintained by 1Flow. For any issues with the destination, contact the 1Flow Support team.

Getting Started

From the Destinations catalog page in the Segment App, click Add Destination.
Search for 1Flow in the Destinations Catalog, and select the 1Flow destination.
Choose which Source should send data to the 1Flow destination.
Go to the 1Flow dashboard and find the API Key in Project Settings.
Enter the API Key in the 1Flow destination settings in Segment.

Supported methods

1Flow supports the following methods, as specified in the Segment Spec.

Identify

Send Identify calls to create new user profile or update existing users with new trait values. For example:

1analytics.identify("userId123", {
2  email: "john.doe@example.com",
3});

Segment sends Identify calls to 1Flow as an identify event.

Track

Send Track calls to record user behavior in your app. For example:

analytics.track("Login Button Clicked");

Segment sends Track calls to 1Flow as a track event.

Page

Send Page calls to record which website pages users have visited. For example:

1analytics.page("Pricing", {
2  title: "Segment Pricing",
3  url: "https://segment.com/pricing",
4  path: "/pricing",
5  referrer: "https://segment.com/warehouses",
6});

Segment sends Page calls to 1Flow as a page_[name] event. (or page_view if a page name isn't provided).

Screen

Send Screen calls to record which mobile app screens users have viewed. For example:

[[SEGAnalytics sharedAnalytics] screen:@"Home"];

Segment sends Screen calls to 1Flow as a screen_[name] event (or screen_view if a screen name isn't provided).

Engage

You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.

For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to false.

When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

(information)

Real-time to batch destination sync frequency

Real-time audience syncs to 1Flow may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.

Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.

Property nameTypeRequiredDescription

API Keystring

required

Your API key can be found in your 1Flow dashboard -> Settings -> Project Settings page.