Skip to main content
The Recordings search bar turns “I need the sessions where checkout broke on mobile” into a precise query in a few keystrokes. It combines free-text search with a small, well-defined filter grammar: every filter you can type is one Replayfy can actually apply, so the list you get back always matches the chips above it. This page covers the full grammar — the filter keys, their values, and how to combine them — plus the scoped views you land in when you drill in from a playlist, funnel, incident, or issue.
1

Go to Recordings

Open app.replayfy.app and select Recordings in the sidebar.
2

Focus the search field

Click the search field at the top of the recordings rail, or press ⌘K (macOS) / Ctrl+K (Windows/Linux) anywhere on the page.
3

Pick or type a filter

An empty field shows Suggested filters, Saved filters, and your Recent searches. Start typing a key (like user: or has:) and Replayfy autocompletes the values from your own workspace data.
Everything Replayfy offers in the dropdown is a filter it can apply. If a dimension can’t be filtered on yet, it simply isn’t suggested — so a chip never quietly returns unfiltered results.

​
The filter grammar

A filter is a key, an operator, and a value — for example browser:Chrome. Most keys use : (“is”); duration uses > (“greater than”).
Filters combine with AND — each chip you add narrows the result set further. There is no OR or “is not”; to explore an alternative, clear a chip and try the other value. Free-typed text that isn’t a recognized key:value is treated as a search term.

​
Signals — has:

The has: filter finds sessions that contain a specific experience signal. These are the moments worth watching: errors, frustration, and slow performance. Values with spaces are typed exactly as shown — has:dead click, has:slow lcp, has:long tasks. Pick them from the dropdown to avoid typos.
Examples

​
Filter by user

user: scopes the list to one identified person. Start typing an email or name and pick the match from the Users group — Replayfy then filters by that exact user.
When you pick a user from the suggestions, Replayfy matches that specific person precisely. If you type a user string by hand without selecting a suggestion, it falls back to a text match. Free-text search, a page: filter, and a hand-typed user: all share a single text slot — so combine at most one of them per query, and pick the user from the list when you also want a page filter in the same search.

​
Filter by page

page: matches sessions that visited a given path. Paths come from your workspace’s own traffic as you type.
A page value matches by substring, so page:/checkout finds every session that visited a URL containing /checkout.

​
Device, browser, platform & country

These describe where a session happened. Browser, device, device model, and country values are drawn from what your workspace has actually recorded, so the dropdown only ever offers real values.
Filter by browser name. Values are suggested from your recorded sessions.

​
Duration

duration: filters by session length and always uses the > operator — it’s a minimum: duration:>2m returns sessions at least two minutes long. There’s no upper bound or “equals”. Values accept a number and a unit — s (seconds, the default), m (minutes), h (hours), or ms (milliseconds):
Longer sessions often signal confusion or a user fighting the UI. Pair duration with a signal — duration:>2m has:rage — to surface the sessions most worth reviewing.

​
Combine filters

Stack chips to narrow in on exactly the sessions you want. Each filter is ANDed with the rest.
Use the keyboard to move fast: To clear everything, use the ✕ at the end of the field.

​
Saved filters & recent searches

The empty dropdown gives you two shortcuts:
  • Suggested filters — every filterable dimension, each with a worked example, so the grammar is legible without memorizing keys. Clicking one drops you into that filter.
  • Saved filters — ready-made starting points: Has errors, Rage clicks, and Slow sessions. Selecting one adds its chips to your current search.
  • Recent searches — your last few queries, stored per workspace in this browser. Selecting one re-runs it exactly, including a user filter’s precise match.
Recent searches are local to your browser and are cleared when you sign out, so a shared machine never leaks one account’s customers into another’s search box.

​
Scoped views

Sometimes you arrive at Recordings already filtered — because you drilled in from somewhere else. In these cases the list is scoped to a specific set of sessions and a banner names the scope. Dismiss the banner to return to all recordings.
Scoped views and the search bar work together — a scope sets the starting set, and any filter chips you add narrow within it. Opening a recording keeps the scope, so the rail stays filtered while you review.
Some links elsewhere in the app (for example, drilling in from a Segments band) open Recordings with filter chips already applied via a ?q= link — the same chips you’d build by hand, pre-filled for you.

Session replay

Everything you can see and do inside a recording.

Funnels

Build a funnel and drill from any step into the sessions behind it.

Crashlytics

Track errors, crashes, and freezes, then jump to the sessions where they happened.