Skip to main content
Lucent analyzes replay data from Lucent SDKs and supported third-party replay providers.

​
Supported sources

​
Mobile replay handling

Lucent normalizes supported mobile payloads before video generation:
  • DOM-like rrweb payloads pass through.
  • Screenshot-style payloads are converted into web-compatible rrweb.
  • Wireframe-style payloads are converted into web-compatible rrweb.
  • Unknown mobile payloads are skipped.
Lucent React Native replay uses screenshot payloads with snapshotSource: "mobile", snapshotLibrary: "lucent-react-native", and snapshotMode: "screenshot". After normalization, supported mobile sessions follow the same analysis path as web sessions.

​
Processing controls

Product Context and processing filters apply to the current project selected in the app header. Filters and sampling usually control whether a session is analyzed, not whether an SDK can send events. Required URL filters apply before full analysis and are fail-closed. If the selected project has Required URL patterns and a session has no matching URL or screen evidence, Lucent skips that session from analysis as required_url_missing while still allowing SDK replay ingestion. For first-party React Native and Expo replay, use path-style screen names such as /onboarding when you want mobile sessions to match Required or Excluded URL filters. See React Native processing controls.

​
Provider metadata

Lucent preserves replay source metadata such as replay provider, provider project, replay URL, platform, and feature flag values when available.

Sentry replay

Connect Sentry Session Replay and import web, mobile, and Expo sessions.

React Native SDK

Capture first-party mobile replay with @lucenthq/react-native.

Feature flag filters

Filter Signals by evaluated feature flags from SDK sessions and integrations.