Appearance
Welcome to Replora
Replora records what visitors do on your website (where they click, how they scroll, what they type, which errors they hit) and lets you replay each visit like a video. On top of the recordings you get heatmaps, funnels, form analytics, surveys, A/B tests, alerts and AI answers, so you can see why people leave instead of guessing.
What you can do with it
Watch visitsEvery session as a replay, with the visitor’s clicks, pages, errors and network calls beside it.OpenSee patternsHeatmaps of clicks, scrolling and mouse movement on each page.OpenFind the drop-offFunnels and form analytics show the step or field where people give up.OpenAsk visitorsShort surveys on your pages, at the moment that matters.OpenTest a changeA/B tests show two versions and measure which one converts.OpenAsk in plain wordsAsk AI answers questions about your visitors and summarizes sessions.Open
How it works, in one minute
- Someone in your team adds your website to Replora.
- A small piece of code, the tracking code, is put on your pages (by pasting it, through Google Tag Manager, or by your developers).
- When a visitor opens a page, the tracking code records the page and every change on it (not a video: the page itself, rebuilt later in the player) and sends it to Replora.
- A few seconds later the visit shows up in Session recordings. You can watch it while the visitor is still on the site.
Privacy first
Everything visitors type is masked (recorded as ***) unless you allow a field, and passwords and card numbers are never recorded. You choose what else to hide in the website settings.
Key ideas
These words come back on almost every page of the dashboard.
| Word | What it means |
|---|---|
| Website (or site) | One website you record, with its own tracking code, settings and data. An account can have several (your plan sets how many). Everything else (recordings, heatmaps, funnels…) belongs to one website. |
| Session (or recording) | One visit: everything a visitor did from arriving until they left. A session ends after 30 minutes without activity, or at the latest after 24 hours; coming back later starts a new session. A session can span many pages. |
| Page view | One page opened during a session. The replay shows them as Page 2 of 7 and the Activity tab lists each one. Single-page apps that change the address without loading a new page count each address change as a page view. |
| Visitor | The person (more exactly: the browser) behind sessions. A visitor is new on their first session and returning after that. If your site tells Replora who someone is (for example their email, with the identify command your developers add), that identity is shown instead of “New visitor”, and you can search by it. |
| Entry page / exit page | The first and the last page of a session. Filters call the first one the landing page. |
| Tag | A fact attached to a session, such as plan = pro or coupon = SPRING. Your site can add tags automatically; you can also add them by hand. You filter and show columns by tags. |
| Event | Something your site reports as it happens (for example signup), used in custom events, funnels and alerts. |
Frustration signals
Replora watches for moments where a visit went wrong. They are counted for every session, shown as small coloured badges in the session list and marked on the replay’s timeline.
| Signal | What it is | Why it matters |
|---|---|---|
| Rage click | Three or more clicks within a second on the same spot. | The visitor expected something to happen and it didn’t, or it was too slow. |
| Dead click | A click on something that looks clickable, after which nothing changes on the page. | A broken button, a picture people think is a link, a disabled control without explanation. |
| JavaScript error | An error in the page’s code (shown in the replay’s Console tab). | Something on the page may have stopped working for this visitor. |
| Failed request | A call the page made to a server that failed or got no answer (Network tab). | A form that didn’t send, a cart that didn’t update. |
| Page loop | Going back and forth between the same pages. Three or more loops count as confusion. | The visitor can’t find what they are looking for. |
Using these signals, Replora sorts every session into a group:
| Group | When |
|---|---|
| Confused | At least one rage click, two dead clicks, three errors and failed requests together, or three page loops. |
| Engaged | Not confused, and an interest score of 40 or more out of 100. Interest grows with the pages viewed (up to 10), the time spent (up to 5 minutes) and the clicks (up to 20). |
| Routine | Everything else: a short visit that went as expected. |
The frustration rate above the session list is the share of sessions with a rage click, a dead click or a JavaScript error.
Retention
Recordings are not kept forever. Each website has a Keep recordings for setting (7, 30, 90, 180 or 365 days, limited by your plan); older sessions are deleted automatically. The session list shows the current value under its title, for example 53 sessions · kept for 90 days. Change it in the website settings.
Starred sessions too
Retention applies to every session, starred or not. To keep a visit for longer, download it as a file.
Who can do what
Everyone in your account works with the same websites. Your role decides what you can change:
| Role | What they can do |
|---|---|
| Manager | Everything, including the team and billing. |
| Member | Works with sites, recordings and reports. Not the team or billing. |
| Viewer | Watches recordings and reads reports. Changes nothing (no starring, tagging, deleting or sharing). |
A member or viewer can also be limited to some websites only. See Team & roles.
