Skip to content

Session replay: record/ignore screens via remote config #558

Open

Description

@ioannisj

Description

Today recording starts and ends automatically.
We need to give the option to either choose which screens have to be recorded/ignored, or the ability to start/pause dynamically as well.

Activity

  1. turnipdabeets commented on Jul 10, 2026

    @turnipdabeets
    Contributor
  2. turnipdabeets commented on Jul 10, 2026

    @turnipdabeets
    Contributor

    Reopening and reframing this one.

    The manual way to control which screens get recorded — wiring start/stopSessionRecording to navigation — is now documented for all four mobile SDKs:
    👉 https://posthog.com/docs/session-replay/how-to-control-which-sessions-you-record#programmatically-start-and-stop-recordings

    But that's only the imperative workaround, and on mobile it has a real limitation: because the screen list lives in app code, changing which screens are recorded requires shipping a new app release.

    What this issue is really asking for is remote-config-driven screen recording — the mobile equivalent of web's URL trigger conditions: configure which screens to record/ignore in the PostHog UI, delivered to the SDK via remote config, with no app release needed.

    That's net-new, coordinated work:

    • remote config payload changes to carry screen-name trigger conditions
    • UI changes in PostHog to configure them (cc @PostHog/team-replay)
    • per-SDK support to honor them (iOS / Android / React Native / Flutter)

    Keeping this open to track the remote-config version — the documented manual approach above is the interim.

  3. changed the title [-]Screen by screen basis recording[/-] [+]Session replay: record/ignore screens via remote config[/+] on Jul 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions