Skip to content

fix(replay): Document searchable properties screen and alias screens #14603

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Aug 11, 2025
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -244,6 +244,10 @@ The reason a replay was triggered. For example, `session` when `replaysSessionSa

- **Type:** string

### `screen`

A specific Screen or View that the user visited during the replay. You can also search for multiple Screens at once using `screens` and passing in an array of strings. Alias of `url`, suited for mobile.

### `sdk.name`

Name of the Sentry SDK that sent the event.
Expand Down Expand Up @@ -271,7 +275,7 @@ A trace represents the record of the entire operation you want to measure or tra

### `url`

A specific URL that the user visited during the replay. You can also search for multiple URLs at once using `urls` and passing in an array of strings.
A specific URL that the user visited during the replay. You can also search for multiple URLs at once using `urls` and passing in an array of strings. Alias of `screen`, suited for web.

- **Type:** string

Expand Down