# FL0 Destination

## Destination Info

* Accepts [Page](/docs/segment/connections/spec/page), [Identify](/docs/segment/connections/spec/identify), [Track](/docs/segment/connections/spec/track) calls.
* Refer to it as **FL0** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object)
* This integration is **partner owned.** Please reach out to the partner's support for any issues.

[FL0](https://fl0.com/?utm_source=segmentio\&utm_medium=docs\&utm_campaign=partners) 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](mailto:support@fl0.com).

## Getting started

1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog) search for "FL0".
2. Select FL0 and click **Add Destination**
3. Select an existing source to connect to FL0.
4. Go to your [FL0 Organization](https://go.fl0.com).
5. Click on **Connections** in the left-hand menu.
6. Click **Add source** in the top-right of the page and select **Segment**.
7. Copy the **API Key** from the Segment properties.
8. 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](/docs/segment/connections/spec).

### Page

Send [Page](/docs/segment/connections/spec/page) calls to FL0 to measure what pages your users and companies are visiting. For example:

```js
analytics.page()
```

Segment sends Page calls to FL0 as automatically tagged events called `Page View`.

### Identify

Send [Identify](/docs/segment/connections/spec/identify) calls to notify FL0 of your logged-in users. For example:

```js
analytics.identify('userId123', {
  email: 'john.doe@example.com'
});
```

Segment sends Identify calls to FL0 as an `Identify` event.

### Track

Send [Track](/docs/segment/connections/spec/track) calls to measure custom events that happen within your app. For example:

```js
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](/docs/segment/engage) to this destination as a **user property**. To learn more about Engage, schedule a [demo](https://segment.com/contact/demo).

For user-property destinations, an [identify](/docs/segment/connections/spec/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.

> \[!NOTE]
>
> 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.

| Field   | Description      | Required | Type   |
| ------- | ---------------- | -------- | ------ |
| API Key | Your FL0 API key | Yes      | string |