FeatBit

Segment-Based Releases

Let your beta users try the whole new experience.

New search, new filters, the same first audience. Define a reusable cohort so related features reach the people who opted in, while everyone else keeps the existing workflow.

Try FeatBit See the solution
BETA

A practical walkthrough with search-beta

The story · A search beta that stays together

A new search is only useful if its filters reach the same testers.

A team rewrites search and its filters together. A few customers have opted into the beta, but copying their identities into every flag would make it easy for the two experiences to drift apart.

Illustrative scenario · Real product configuration

Inside FeatBit · 3 steps

Keep a connected beta together in three steps.

Define the opt-in cohort once, reference it in targeting, and inspect its dependencies before expanding.

  1. 01Step 01 / 03

    Define who has opted into the beta.

    Create search-beta and give it an explicit membership rule. The demo uses betaOptIn = true, so joining the beta is a deliberate customer choice.

    Segment
    search-beta
    Membership
    betaOptIn equals true

    The beta has one audience definition that the team can review.

    Inside FeatBitLive app · Demo
    Swipe to inspect
    Segments → search-beta → Membership rules

    Customers who opt in

    search-beta

    One reusable membership rule

  2. 02Step 02 / 03

    Reference the segment from the feature.

    In search-config, add a targeting rule for users in search-beta. Serve Candidate search to that audience while the default remains Stable search.

    Condition
    User is in search-beta
    Rule serves
    Candidate search

    The candidate configuration reaches the cohort without copying a list of customer IDs.

    Inside FeatBitLive app · Demo
    Swipe to inspect
    search-config → Targeting → Segment rule

    search-beta

    Candidate search

    Reuse the audience in each related flag

  3. 03Step 03 / 03

    Check which flags depend on the cohort.

    Review the segment’s flag references before editing membership. Add the same segment to related filter flags when those features are ready to enter the beta together.

    Demo reference
    search-config
    Before expansion
    Review every referencing flag

    A cohort change becomes a deliberate release decision for the whole workflow.

    Inside FeatBitLive app · Demo
    Swipe to inspect
    Segments → search-beta → Flag references

    One audience change

    Related feature flags

    Review dependencies before expanding

The next decision

Add the next cohort when search and filters work together.

Review empty-result reports, task completion, and qualitative feedback. Expand the shared segment only when the complete beta experience is ready.

Build your own release in FeatBit

Treat a shared segment as a shared dependency

Give the segment an owner and review changes against all dependent flags. Keep attribute values consistent between your application and your targeting rules.

From idea to implementation

Build your release path.

Create and manage user segmentsUse segments in targeting rulesPlan the wider release

Keep the release moving.

All solutions

Customer & Role Targeting

Pilot an AI-built reporting workspace with one customer's admins. Keep members and other accounts on the existing path.

Progressive Rollouts

Start an AI-assisted checkout with a small canary. Review errors and completion before more users receive the candidate.

Feature Experimentation

Compare two experiences with a stable feature flag split. Follow Exposure and Measuring through the primary metric, posterior distribution, and guardrails.