> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lucenthq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Session replay integrations

> Import sessions from supported replay providers and use them in Lucent Signals.

Lucent analyzes replay data from Lucent SDKs and supported third-party replay
providers.

## Supported sources

| Source     | Web replay | Mobile replay                                                                 | Notes                                                                            |
| ---------- | ---------- | ----------------------------------------------------------------------------- | -------------------------------------------------------------------------------- |
| Lucent SDK | Supported  | Supported with `@lucenthq/react-native` screenshot replay                     | Browser and React Native sessions captured directly by Lucent.                   |
| PostHog    | Supported  | Supported when the payload contains DOM, screenshot, or wireframe replay data | Unknown mobile payloads are skipped.                                             |
| Datadog    | Supported  | Supported when exported events are renderable as rrweb                        | Source metadata is preserved on imported sessions.                               |
| Amplitude  | Supported  | Supported when exported events are renderable as rrweb                        | Source metadata is preserved on imported sessions.                               |
| Sentry     | Supported  | Beta for Sentry mobile and Expo replay payloads                               | Mobile screenshot and wireframe payloads are transformed before video rendering. |

## 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

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 a source 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](/sdk/react-native#processing-controls).

## Provider metadata

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

## Related guides

<CardGroup cols={2}>
  <Card title="Sentry replay" icon="sentry" href="/integrations/sentry">
    Connect Sentry Session Replay and import web, mobile, and Expo sessions.
  </Card>

  <Card title="React Native SDK" icon="mobile" href="/sdk/react-native">
    Capture first-party mobile replay with `@lucenthq/react-native`.
  </Card>

  <Card title="Feature flag filters" icon="toggle-on" href="/signals/feature-flags">
    Filter Signals by evaluated feature flags from SDK sessions and integrations.
  </Card>
</CardGroup>