Skip to main content
Flags let you remotely control the behavior in your application, like a website or a mobile app.

​
Flag Schema

Flags in Confidence don’t just describe a boolean decision to enable or disable a feature. Instead, flags have multiple properties that you use to control multiple aspects of the experience. The flag schema defines the available properties and their data type. The schema lets applications consume the flag value while knowing what to expect. Confidence supports the following data types in the schema:
TypeDescriptionExample values
StringA string"HELO"
IntegerAn integer42, 199932
DoubleA double3.14, 50.0
BooleanBooleantrue, false
StructNested structure{ age: 23, country: "SE" }

​
Variants

A variant is a named set of values for the properties of the flag. Workflows, like A/B tests and rollouts, use variants to give users different experiences. If a variant doesn’t specify the value of a property, the SDK uses the default value specified when a client resolves the flag.

​
Client Association

Not all clients should have access to all flags. For example, some flags might be sensitive and should only be available to clients that are running in an trusted environment. Mobile apps and websites batch resolve flags to reduce the number of requests made to Confidence. Associate a flag with as few clients as possible to limit the number of resolved flags. Doing so also reduces costs.

​
Archive Flags

When a flag is no longer needed, you can archive it. Archiving a flag prevents clients from resolving and using it.

Create a Flag

Step-by-step flag creation guide

Define Rules

Control how variants are assigned

Flag Quickstart

End-to-end flag setup tutorial

SDKs Reference

Integrate flags in your application