Set up FlagSync
The guide below will walk you through creating and configuring your first feature flag.
Last updated
The guide below will walk you through creating and configuring your first feature flag.
Last updated
Start your free 14 day trial of FlagSync. No credit card required, no minimum seat requirement.
Design your first flag in the Flags dashboard.
Choose a flag name. This is a human-readable name for the flag. It can be changed after creation.
Choose a flag key. This is a unique identifier for the flag, and will be used in code to retrieve the flag value.
Enter a description. Optionally describe the functionality of the flag.
Choose flag type. The flag type controls the data type of variant values. See below:
Define flag variants: Define the variants that will be served for this feature flag.
FlagSync gives you granular controls over the rollout of your feature flag.
Target all users.
Target specific user segments.
Distributed (percentage) rollouts.
With every flag, you're able to define the default disabled variant, and default enabled variant.
The default enabled variant is served to all users when the flag is enabled.
The default disabled variant is served to all users when the flag is disabled.
Additionally, you're able to define targeting rule for user segments that you define with custom attributes, such a "department" or "job title".
A use case would be to target "QA Testers" for a feature under test, while all other users are served the baseline variant (i.e. existing experience).
Lastly, FlagSync offers dead-simple distributed rollouts. Simply define the percentages that should be served for each variant, and save the flag.
You can also choose to serve a default variant when the flag is enabled.
Users are bucketed deterministically and will be consistently served the same flag variant, ensuring the same experience for the duration of the rollout.
Simply toggle the flag, and you're good to go!
Head over to the SDK quickstart guide to start evaluating your flags in code
Boolean
Simple on/off switches for features
Perfect for:
Enabling/disabling features
Beta feature toggles
Maintenance modes
String
Predefined options for feature behavior
Common uses:
Color theme: light-mode, dark-mode
Button text: Register, Join Now, Sign Up
Env mode: development, staging, production
Number
Configurable numeric values
Common uses:
API rate limits: 100, 500, 1000
Compression levels: 70 (70%)
Page sizes: 10, 25, 50
JSON
Complex configuration objects
Example config:
