Feature Request: Persistent URL for Session Replay Filters
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 39.9k
- Forks
- 3.4k
- Avg merge
- 6h 51m
- Merged PRs (30d)
- 232
Description
Feature request
Is your feature request related to a problem?
Currently, when navigating to the Session Replay page, you must manually click the filter button each time to access the search/filter interface. This creates friction when frequently searching for specific sessions (e.g., by email address). Additionally, there's no way to save or bookmark a URL that opens directly to the Session Replay page with filters already applied or the filter panel already open.
Describe the solution you'd like
Enable URL parameters for Session Replay filters so that:
The filter panel state (open/closed) can be preserved in the URL
Specific filters (like email address) can be pre-populated via URL parameters
Users can bookmark or share these URLs to quickly access filtered session replay views
Example: replay/recordings?filter_open=true&email=user@example.com
Describe alternatives you've considered
Creating cohorts for frequently searched users (workaround, but adds extra steps)
Using the API to fetch filtered sessions programmatically (not suitable for quick UI access)
Additional context
From: https://posthoghelp.zendesk.com/agent/tickets/59024 (moved to PostHog: https://us.posthog.com/project/2/support/tickets/60415)
Debug info
- [ ] PostHog Cloud, Debug information: [please copy/paste from https://us.posthog.com/settings/project-details#variables]
- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]
- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Session Replay page route, replay/recordings, and inspect how the filter panel state and current filters are handled. Done means the URL can preserve whether the panel is open, restore supported filters such as email, and produce bookmarkable or shareable filtered views.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100