1Flow Web (Actions) Destination
Destination Info
- Accepts Page, Alias, Group, Identify and Track calls.
- Refer to it as 1Flow Web (Actions) in the Integrations object
- This destination is not compatible with Destination Insert Functions.
- This integration is partner owned. Please reach out to the partner's support for any issues.
- This destination is in Beta
1Flow is a leading in-app user survey and messaging platform for Mobile app and SaaS businesses.
1Flow is an easy-to-use, yet powerful in-app survey and messaging software. Using 1Flow, you can reach users in-the-moment while they are interacting with your website or mobile app, to collect highly contextual user insights that help you improve your product offering and customer experience.
When you use the 1Flow Web (Actions) Destination, Segment loads the 1Flow SDK for you. The 1Flow library enables you to track and identify user events on your website and interact with the 1Flow messenger window.
- From Segment, navigate to Connections > Catalog, then select Destinations.
- Search for and select 1Flow Web (Actions) Destination.
- Select the web source that will send data to 1Flow web (Actions) and follow the steps to name your destination. The web source chosen must use Analytics.js 2.0.
- On the Settings tab, input your 1Flow PROJECT API KEY and other destinations settings.
- Follow the step in the Destinations Actions docs to customize your mappings.
- Enable the destination and configured mappings.
This is the unique app_id for your 1Flow application, serving as the identifier for data storage and retrieval. This field is mandatory.
1Flow Web (Actions) has the following presets
| Preset Name | Trigger | Default Action |
|---|---|---|
| Track Event | Event type = "track" | Track Event |
| Identify User | Event type = "identify" | Identify User |
Build your own Mappings. Combine supported triggers with the following 1Flow Web-supported actions:
Mapping limits per destination
Create or update a user in 1Flow.
Identify User is a Web action. The default Trigger is type = "identify"
Optional
A unique identifier for the user.
Optional
The user's custom attributes.
Submit an event to 1Flow.
Track Event is a Web action. The default Trigger is type = "track"
The name of the event.
Optional
A unique identifier for the user.
Optional
An anonymous identifier for the user.
Optional
Information associated with the event
The 1Flow destination will automatically ingest a User ID and any values sent over your Identify spec as traits, as long as session capture is enabled in 1Flow.
When you call Segment's Identify method, it will be equivalent to logUser of 1Flow. Identify calls that do not have a User ID value are not sent to 1Flow.
- Segment's
userIdisuserIDin 1Flow - Segment's
traitsisuserDetailsin 1Flow
The 1Flow destination automatically ingests any user actions tracked over your Track spec as events, as long as session capture is enabled in 1Flow.
If you are seeing 404 responses in your browser's network tab, you've likely encountered one of two issues:
- You set the wrong App ID on the 1Flow Actions (Web) destination settings page.
- You set the wrong Regional Data Hosting value on the 1Flow Actions (Web) destination settings page. 1Flow gates regional endpoints by plan level, so you may not have access to EU data hosting.
Segment lets you change these destination settings from the Segment app without having to touch any code.
This is the unique app_id for your 1Flow application, serving as the identifier for data storage and retrieval. This field is mandatory.