---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/segment/connections/destinations/catalog/bucket#article
headline: Reflag Destination
description: Connect the Reflag destination to Segment to send Identify, Group, and Track events to Reflag's feature flag platform for SaaS.
url: https://www.twilio.com/docs/segment/connections/destinations/catalog/bucket
inLanguage: en
dateModified: 2026-07-15T17:40:17.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# Reflag Destination

## Destination Info

* Accepts [Group](/docs/segment/connections/spec/group), [Identify](/docs/segment/connections/spec/identify), [Track](/docs/segment/connections/spec/track) calls.
* Refer to it as **Bucket**, **Reflag** 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.

[Reflag](https://reflag.com/?utm_source=segmentio\&utm_medium=docs\&utm_campaign=partners) is feature flags for SaaS that run on TypeScript.

With Reflag, you can:

* Release features gradually with simple flags.
* Gate features based on customer subscriptions.
* Iterate fast with adoption metrics and feedback.

This destination is maintained by Reflag. For any issues with the destination, [contact the Reflag Support team](mailto:support@reflag.com).

## Getting Started

1. From the Destinations catalog page in the Segment App, click **Add Destination**.
2. Search for "Reflag" in the Destinations Catalog, and select the Reflag destination.
3. Choose which Source should send data to the Reflag destination.
4. Go to [Reflag's Environment Settings](https://app.reflag.com/envs/current/settings/app-environments) and find and copy the "Publishable Key" for the Production environment.
5. Enter the "Publishable Key" as "Publishable Key" in the "Reflag" destination settings in Segment.

## Identify

Segment sends Identify calls to Reflag as an Identify event that updates User profiles. To learn what the [Identify method](/docs/segment/connections/spec/identify/) does, see the Segment Spec. An example call looks like:

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

## Group

Segment sends Group calls to Reflag as a Group event that updates Company profiles. To learn what the [Group method](/docs/segment/connections/spec/group/) does, see the Segment Spec. An example call looks like:

```js
analytics.group('groupId123', {
  name: 'Acme, Inc',
});
```

## Track

Segment sends Track calls to Reflag as a Track event that updates the Features page. To learn what the [Track method](/docs/segment/connections/spec/track/) does, see the Segment Spec. An example call looks like:

```js
analytics.track('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.

## Settings

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

| Field           | Description                                                                                   | Required | Type   |
| --------------- | --------------------------------------------------------------------------------------------- | -------- | ------ |
| Publishable Key | The publishable key for your Bucket environment, found on the tracking page on app.bucket.co. | Yes      | string |