SDK Configuration

Flashduty RUM’s session replay feature is integrated into the RUM SDK. By simply configuring sampling rates and privacy rules, you can quickly enable the replay feature.

Enable Collection

Automatic Collection
Manual Collection
Force Enable

The replay SDK is integrated into the RUM SDK. Configure the sampling rate to enable the replay feature:

window.FC_RUM.init({
  applicationId: "YOUR_APPLICATION_ID",
  clientToken: "YOUR_CLIENT_TOKEN",
  // ...
  sessionReplaySampleRate: 10, // Default session replay sampling rate 10%
  // ...
});

Sampling Method: When initializing a session in the client SDK, a random number between 0-1 is generated and compared with rate/100. If it falls within the range, the session becomes a sample and replay data is collected and reported throughout the session lifecycle.Based on the session being sampled, the session replay sampling rate (sessionReplaySampleRate) is calculated and sampled a second time.

After configuring the default sampling rate, automatic collection starts after RUM.init() executes. If you want to manually control collection timing (such as collecting data only after user login), you can enable the manual collection switch and then manually call the record method:

window.FC_RUM.init({
  applicationId: "YOUR_APPLICATION_ID",
  clientToken: "YOUR_CLIENT_TOKEN",
  // ...
  sessionReplaySampleRate: 10, // Sampling rate 10%
  startSessionReplayRecordingManually: true, // Enable manual collection switch
  // ...
});

if (userIsShouldRecord()) {
  // If certain conditions are met, enable replay
  window.FC_RUM.startSessionReplayRecording(); // Start data collection when called
}

After enabling collection, you can stop collection using the stopSessionReplayRecording() method.

In some scenarios, even if the sampling rate doesn’t hit, you may want to collect data for that session (such as closely monitoring newly launched features, or capturing subsequent operations after catching an exception). You can force enable replay by calling startSessionReplayRecording({ force: true }).

Force enable only works when the current session is sampled but sessionReplay is not sampled. If the session itself is not sampled, force enabling replay will have no effect.

Disable Collection

If you need to disable the collection feature, set the corresponding replay sampling rate to 0 or simply remove the configuration item:

window.FC_RUM.init({
  applicationId: "YOUR_APPLICATION_ID",
  clientToken: "YOUR_CLIENT_TOKEN",
  // ...
  sessionReplaySampleRate: 0, // Disable replay feature
  // ...
});

How It Works

The session replay SDK is based on rrweb.

Recording Phase

The recording SDK takes snapshots of the current DOM and CSS styles, and collects corresponding events when user behaviors occur (DOM changes, mouse movement, clicks, form input, etc.). Data is reported after serialization, compression, and sensitive information removal.

Replay Phase

The playback SDK reconstructs the DOM based on snapshots and converts event behaviors into DOM changes for display at appropriate times.

Before data reporting, the SDK compresses data in advance and executes this CPU-intensive operation in a Web Worker, without affecting main thread rendering
SDK compatibility is consistent with RUM SDK, supporting IE11 and above browsers

Quick Start

Analytics

SDK Integration

Performance

Error Tracking

Explorer

Session Replay

Best Practices

Others

Enable Collection

Disable Collection

How It Works

Next Steps

View Session Replay

Privacy Protection

Quick Start

Analytics

SDK Integration

Performance

Error Tracking

Explorer

Session Replay

Best Practices

Others

​Enable Collection

​Disable Collection

​How It Works

​Next Steps

View Session Replay

Privacy Protection

Enable Collection

Disable Collection

How It Works

Next Steps