The Studio

Home and Overview

Homelists every product surface, with this week's sessions, the device mix and whether capture is healthy. Add a project here when you want a second surface (a marketing site next to the app) with its own id, journeys and runs.

Overview is one project’s state right now: the one thing tripping up users most, the errors visitors are hitting, a shortcut to watch the clearest session showing it, recent activity, and a card to predict a change before you ship it.

Recordings

Every captured session, newest first, filtered by project. Open one to watch it: play, pause, 1× to 8×, skip idle stretches, and a timeline with markers where something went wrong. The Inspector beside the player has three tabs: a rundown of the session in plain words, the raw events, and the console with errors and failed requests as they happened. Share gives a link that opens the replay at that moment.

Heatmaps shows where people click and how far they scroll on each page.

Recordings of simulated people are separate: they appear under each run on the Simulate page and are kept for 24 hours.

Drop-offs

Recurring friction from the last seven days, ranked by impact: a JavaScript error many sessions hit, a button people click that does nothing, a request that keeps failing, a form that keeps rejecting. Each line says how many sessions and people it touched and opens a session that shows it, at the moment it happened. Failures that aren’t your product’s problem (an ad blocker, the visitor’s network) are counted but set aside.

Segments

Segments group your real sessions into the kinds of people who use your product: by what they came for, how they behave, what device they are on, whether they are signed in. Each segment carries a persona written from its sessions, its share of traffic, and the members it was built from. Build them once you have a week of recordings; rebuild when the product or the audience changes.

Segments are what a simulation draws from. “Everyone · your real mix” sends people in the proportions the segments actually occur; picking one segment sends only that kind of person. Each simulated person is grounded in one real session from the segment: its device, its pace, its patience, what it came to do.

Simulate

Simulate is the map of your product and the panel that sends people through it; see Simulate. The canvas header says where the map came from: Written from the repository’s code when a repository is connected, otherwise the explorer’s upload or your recordings. Write them from the code asks for a fresh set when the map was edited or pinned and would otherwise be kept; Restore previous map brings back the set before.

Settings and Workspace

Settings belongs to the project: the Behavior SDK tag, allowed origins, keys, the stored sign-in, integrations, and GitHub, where owners and admins install the GitHub App once and connect a repository to the project. From then on every pull request gets a check and the project’s journeys are written from the code; see GitHub App.

Workspace, in the sidebar, is the team, billing and your account. It is shared by every project on the workspace; see Workspace and settings.

Search

⌘K opens search from anywhere in the Studio: pages, sessions by id, runs, people, and settings. GitHub App is an entry too and opens Settings → GitHub.