Policies and Clients
Configure recording policies under Recordings > Settings in the Confidence UI. Create one recording policy for each client. A policy contains an ordered list of rules for that client. Confidence evaluates enabled rules in order. A rule matches when its environment, targeting, audience allocation, and session sample all pass. The first matching rule applies. If a rule does not match, Confidence evaluates the next rule. If no rule matches, the SDK does not record the session. Account capacity can also prevent capture.Required Roles
A user with only Creator or Recording Policy Creator access can manage a policy that
they create because they own it. They cannot edit policies that other users own.
Rule Types
You can add three types of rules.A/B Test Rule
Select an existing A/B test. The rule uses the experiment segment, allocation, and targeting. The Limited to value controls the percentage of matched sessions to record.Rollout Rule
Select an existing rollout. The rule uses the rollout segment, allocation, and targeting. The Limited to value controls the percentage of matched sessions to record.Conditional Targeting Rule
Define conditions with context attributes and segments.- Record controls the percentage of the matched audience eligible for recording.
- Of selects the context field that identifies a user or another targeting entity.
- Limited to controls the percentage of sessions recorded for each included target.
Recording rules select who and what to record. They do not change the flag
variant that a user receives.
Environments
All rule types can apply to selected environments. Environment selection uses the environments associated with the client secret. It does not use a customcontext.environment value unless you also target that value in a condition.
Manage Rule State and Order
You can create a rule as a draft or create and activate it immediately. You can also:- Enable or disable a rule
- Edit or delete a rule
- Drag rules to change their evaluation order

