Skip to main content

​
FlagSync Basics

Master the building blocks of feature control:

Feature Flags

A feature flag toggles features on or off without redeploying code.

Hide beta-feature until ready, then enable for testing.

User Segments

Group users by attributes (e.g., location, role) to target flags or experiments.

Show beta-feature to premium users in Boston.

Percentage Rollouts

Release features gradually to a fraction of users for safe testing.

Enable beta-feature for 10% of users, scale up if stable.

​
Data and Insights

Understand how to measure your features:

Impressions

Record flag evaluations automatically when flag() is called.

flag('beta-feature') logs if a user saw Enabled.

Events

Track user actions (e.g., clicks) via the SDK’s track() function.

Log a purchase_event to measure beta-feature’s impact.

Metrics

Measure flag impact (e.g., conversion rates) using events and impressions.

Track beta-feature’s click-through rate for engagement.

Experiments

Compare feature variations to measure impact via metrics.

Test two beta-feature designs and pick the winner by clicks.

​
How FlagSync Works

FlagSync’s components work together to launch and optimize features—like a new checkout flow—with data-driven confidence:
1

Flags control what’s live (e.g., `New Feature`)

2

Segments decide who sees it (e.g., premium users)

3

Rollouts pace the release (e.g., 25% at a time)

4

Events and Impressions capture data (e.g., clicks, views)

5

Metrics reveal the impact (e.g., higher engagement)

6

Experiments test variations (e.g., A/B designs)

FlagSync lets you roll out, measure, and optimize features in one seamless flow.

​
Next Steps