Skip to contentSkip to navigationSkip to topbar
Page tools
Useful for sharing or LLM
Accelerate development with AI

On this page
Looking for more inspiration?Visit the

Reflag Destination


Destination Info
  • Accepts Group, Identify and Track calls.
  • Refer to it as Bucket, or Reflag in the Integrations object
  • This integration is partner owned. Please reach out to the partner's support for any issues.

Reflag(link takes you to an external page) 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(link takes you to an external page).


Getting Started

getting-started page anchor
  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(link takes you to an external page) 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.

Segment sends Identify calls to Reflag as an Identify event that updates User profiles. To learn what the Identify method does, see the Segment Spec. An example call looks like:

1
analytics.identify('userId123', {
2
name: 'John Doe',
3
email: 'john.doe@example.com',
4
});

Segment sends Group calls to Reflag as a Group event that updates Company profiles. To learn what the Group method does, see the Segment Spec. An example call looks like:

1
analytics.group('groupId123', {
2
name: 'Acme, Inc',
3
});

Segment sends Track calls to Reflag as a Track event that updates the Features page. To learn what the Track method does, see the Segment Spec. An example call looks like:

analytics.track('Login Button Clicked', {});

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(link takes you to an external page).

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.


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

Property nameTypeRequiredDescription
Publishable Keystring
required

The publishable key for your Bucket environment, found on the tracking page on app.bucket.co.