Skip to main content
Confidence Flags is a managed service for feature flagging. It provides sophisticated targeting and coordination capabilities.
Looking to get started with creating your first feature flag? Follow this quickstart
In Confidence Flags, a flag is a way to control what experience a user should receive. A flag has multiple variants, one for each intended experience, and these variants describe the specifics of the experience. This video gives a quick overview of how feature flags works in 2 minutes and 2 seconds. Clients resolve flags to decide which experience to serve to a user. Common types of clients are mobile apps, web sites, and backend services. A set of rules define what variant to assign to which users in what situations. The resolver evaluates the rules and decide which variant to return to the client using data in the evaluation context. The evaluation context is data about the user, such as their country, age, or subscription status, and the environment the client is running in, such as the browser type. The client feeds the context to the resolver in the resolve request. If the context meets a rule’s targeting condition, the client receives the variant specified in the rule.

​
Flag Anatomy

A flag has a name and a value. In Confidence Flags, the flag value is a structure with named properties. Think of it as a JSON object. This makes it possible to control multiple aspects of the behavior of a client with a single flag. Flags have a schema that describe the structure of the value: available properties and their data types. Variants give a name to a value of the flag which defines a possible behavior of the thing the flag is controlling. Imagine a flag that controls the various aspects of the Spotify’s home screen. The flag has a name, home-screen, and the value has properties:
  • The size of the title (title-font-size).
  • Show the settings button or not (show-settings).
  • Show shortcuts or not (show-shortcuts).
  • Number of shortcuts to show (shortcut-count).
*/} The schema for this flag is as follows:
PropertyTypeDescription
title-font-sizeStringSize of the title font.
show-settingsBooleanWhether to show the settings button.
show-shortcutsBooleanWhether to show shortcuts.
shortcuts-countIntegerHow many shortcuts to show.
The flag has two variants: default and large-title. The default variant has the following values:
PropertyValue
title-font-size"small"
show-settingstrue
show-shortcutstrue
shortcuts-count9
The large-title variant has the following values:
PropertyValue
title-font-size"large"
show-settingsfalse
show-shortcutstrue
shortcuts-count6
With the flag and its variants in place, a client can resolve the flag to a value. For example, a website can resolve the flag to the large-title variant, and show a large title, hide the settings button, and show six shortcuts. When you use a flag to control an experience, the flag is applied and the client emits a flag applied event. The resolver writes flag applied events, in the form of assignment decision records, to a data warehouse for later use in analysis of experiments.
Learn how to create a Flag

​
Client Types

Resolving a flag to value and applying the flag value to control an experience are two distinct operations. The type of client decides when these operations happen. Single-user clients, such as mobile apps or single-page web applications, resolve multiple flags (1, 2) at the start of a session. They later use locally cached flag values when using flags throughout the session. The reason for this is to reduce flickering of the user experience during the session. Multi-user clients, such as backend services, resolve flags as requests come in.

​
Confidence SDKs

Confidence provides SDKs for flag resolving with support for multiple languages and platforms. More information about the Confidence SDKs is available in the dedicated section.
Looking to get started with creating your first feature flag? Follow this quickstart