Before You Begin
You need:- A Confidence account with Recordings enabled
- A browser client secret for the environment you want to record
- Permission to create or edit a recording policy
- A recording policy with an active rule for your client
Set Up the SDK
1
Install the package
2
Review the privacy controls
The SDK masks input values by default. Review privacy and data masking
before you enable recording in a production environment.
3
Initialize the recorder
appVersion stores an application version or commit hash on the recording.
Confidence uses context to evaluate recording rules before capture starts. Do not
add direct personal identifiers, access tokens, or secrets to context.The SDK uses automatic mode by default. It starts capture when the session matches
an active recording rule.4
Verify recording
Interact with the application and check
recorder.isRecording. It becomes true
after capture starts.A false value does not always indicate an error. A rule, sample rate, or
account capacity can exclude the session.5
Finish the test session
Close the test tab. If other tabs share the browser session, close those tabs too.
Each tab appears as a separate recording. Allow several minutes after the browser
session ends before you check Recordings.
Add Debug Logs
Pass a logger while you set up the SDK:Customize Recordings
Configure privacy
Mask or block sensitive content before it leaves the browser.
Configure recording rules
Control which users and sessions the SDK records.
Add custom data
Add context, tags, and measurements.
Parameterize routes
Group dynamic application routes.
Integrate feature flags
Keep recording and feature flag targeting context consistent.
Related Resources
Explore recordings
Learn what you can review in the Confidence UI.
SDK reference
Review all SDK options and methods.
Troubleshoot recordings
Diagnose SDK setup and capture problems.

