FL0 Destination
Destination Info
- Accepts Page, Identify, and Track calls
- Refer to it as FL0 in the Integrations object
Partner Owned
- This integration is partner owned. Please reach out to the partner's support for any issues.
FL0 is the Product Intelligence Platform that converts customer interactions into revenue opportunities.
This destination is maintained by FL0. For any issues with the destination, contact the FL0 Support team.
Getting started
- From your workspace’s Destination catalog page search for “FL0”.
- Select FL0 and click Add Destination
- Select an existing source to connect to FL0.
- Go to your FL0 Organization.
- Click on Connections in the left-hand menu.
- Click Add source in the top-right of the page and select Segment.
- Copy the API Key from the Segment properties.
- Enter the API Key in the FL0 destination settings in Segment.
Supported methods
The FL0 destination supports the following methods, as specified in the Segment Spec.
Page
Send Page calls to FL0 to measure what pages your users and companies are visiting. For example:
analytics.page()
Segment sends Page calls to FL0 as automatically tagged events called Page View
.
Identify
Send Identify calls to notify FL0 of your logged-in users. For example:
analytics.identify('userId123', {
email: 'john.doe@example.com'
});
Segment sends Identify calls to FL0 as an Identify
event.
Track
Send Track calls to measure custom events that happen within your app. For example:
analytics.track('Login Button Clicked')
Segment sends Track calls to FL0 as a tagged event with the same name as the event, for example Login Button Clicked
.
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.
Real-time to batch destination sync frequency
Real-time audience syncs to FL0 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.
Setting | Description |
---|---|
API Key (required) |
string . Your FL0 API key |
This page was last modified: 16 Jul 2024
Need support?
Questions? Problems? Need more info? Contact Segment Support for assistance!