Skip to main content
Start receiving core insights on your product and users by getting an understanding of the core building blocks of Adora.

Replays

A Replay is a recording of a users’ session in your product. You can isolate down to a user and watch how they used your product and interacted with it. Each Replay has a sequence of steps and a timeline of key moments.

Actions

An Action is an interaction that a user has with an element on your app, captured during the Replay. Some examples of actions include clicking an upgrade Button, inputting into a text fields, or selecting an option on a question.

Screens

A Screen is a live snapshot of your product. Adora groups these snapshots based the URL of the screen and shows your exactly what your users see. If you have different screens that sit on the same URL (e.g. an onboarding flow with many steps that all sits on app.yourproduct.com/onboarding) Adora will automatically detect the differences and seperate them out.

Journeys

A Journey is a combination of Screens and Actions that show the path your users take through your product and are constructed off of real user sessions. You can create your own journeys by picking screens and actions or let Adora map them out for you.

Frustrations

A Frustration is a small, actionable finding that Adora automatically uncovers about your product, such as user friction or UI issues. They surface as bite-sized nuggets of understanding to help you identify problems and improve your product experience. Search is your command centre for quickly finding everything you need, from screens and journeys to actions and insights from replays. With plain text or query selectors, you can zero in on specific events, for example “in:replays payment failed” will surface replays where a user couldn’t complete a payment.
I