Skip to main content
Confidence offers two options for flags: a managed resolver and a sidecar resolver. With the managed resolver, Confidence operates the flag resolver service for you. With the sidecar resolver, you operate the resolver. Confidence doesn’t persist any user-identifiable information on the Confidence side. An identifier and a context transiently passes through the flags service so that Confidence can give aggregate information.

​
Data That Confidence Persists

The information that you pass to the resolver is:
  • A unique ID to randomize on.
  • A context with information to use for targeting. For example, country or is_employee.
Information that Confidence persists is:
  • The number of resolves and the timestamp of the last resolve.
  • The number of applies and the timestamp of the last apply.
  • The names of the fields available in the context. The values of the fields in the context are never stored.
The information that Confidence persists in your data warehouse is:
  • The ID used for randomization.
  • The context used in the resolve.
  • The name of the flag.
  • The name of the rule that determined what variant to give.
  • The name of the variant that the user was exposed to.

​
Managed Resolver

If you use the managed resolver, Confidence operates the flag resolver for you. The following figure gives more details on how data flows through Confidence Flags in this case. How data flows through Confidence The sequence of events are:
  • A client resolves a flag by passing an ID and a context. It receives a variant.
  • Confidence passes the ID and context to other internal services, but without storing the ID or the values in the context. It only stores the schema of the context and aggregated information about the number of resolves.
  • When the client uses the variant, it also applies it by calling the apply endpoint. The apply event similarly passes through Confidence, but only storing the number of applies.
  • Confidence eventually writes the event to your data warehouse. At this point, neither the ID nor the context is present in any part of Confidence.

​
Sidecar Resolver

When using the sidecar resolver, you operate the flag resolver. The following figure gives more details on how data flows through Confidence Flags in this case, and how the sidecar communicates information back to Confidence. How data flows through Confidence The sequence of events are:
  • A client resolves a flag by passing an ID and a context to the sidecar resolver. It receives a variant.
  • At regular time intervals, the sidecar resolver sends the number of resolves and the schema of the context to Confidence.
  • When the client uses the variant, it also applies it by calling the apply endpoint. The sidecar resolver forwards the apply event to Confidence, which only stores the number of applies.
  • Confidence eventually writes the event to your data warehouse. At this point, neither the ID nor the context is present in any part of Confidence.
Read more about how to set up a local sidecar resolver.

Set Up Local Resolver

Deploy the sidecar resolver

Local Resolver Reference

Resolver configuration options

Warehouse Setup

Configure your data warehouse