Feature Flags
A feature flag is a setting in your code that you can turn on, off, or change from the A vs B dashboard, without a new deploy. This section covers everything: core concepts, installing the SDK, building targeting rules (the conditions that decide which visitors see which value), and reading rule results.
Start with the Feature Flags Quickstart. It walks the whole path once: create a flags project, then read a flag from your own code. It hands you back to this section for the detail afterward.
What feature flags are in A vs B
Your application code asks a flag for its value. That value decides whether a feature shows, which variant (one specific version being tested, control or a challenger) to display, or what configuration to use. A flag can hold several environments, such as production and staging, each with its own targeting rules. Changes sit in a draft until you publish them. A rule can be a fixed targeted delivery (serve one variation to a named group of visitors) or a measured A/B test. Both kinds share the same audiences, scheduling, and analytics as web experiments.