Heatmaps, videos & behaviour
Clicks, scrolling, mouse moves and a video of each test, for all your testers together: see what they really did, not only what they said.
See what testers do, not only what they say
A tester writes « it works », but needed three tries to find the button. Another one never scrolled down to your offer. Answers tell you what people think; their behaviour tells you what really happened. Launch Approved records both, in the same test.
- Heatmaps show where all the testers clicked, how far they scrolled and where their mouse went.
- Videos replay each test as the tester saw it, with a jump to every step.
- Signals point out the frustration: rage clicks, clicks on what does nothing, a first click in the wrong place.
Everything stays on your WordPress, positions only, never what is typed. This page explains what is recorded, where to find it, and how to show it to your client.
What is recorded, and where
| What it shows | Setting | |
|---|---|---|
| Clicks | Where testers click: left or right, rage clicks, clicks on what does nothing, the first click of a step. | Record the clicks and scrolling |
| Scrolling | How far down each tester went, and what showed when the page opened. | Record the clicks and scrolling |
| Mouse | Where the mouse went, a few times a second: the reading path. | Record the mouse’s moves too |
| Video | The whole test, as the tester saw it, with a jump to every step. | Record the test as a video |
Clicks, scrolling and mouse moves are read on the pages of this WordPress, or on the client’s site linked by the connector. On another site without the connector, browsers forbid it: the cockpit says so. The video works on any site.
The Behaviour tab
Each campaign has a Behaviour tab with two parts: the videos of the tests and the heatmaps of the pages. Everything is gathered for all the testers together, at the end of their tests, so you see patterns, not one person’s habits.
Pick a page and a screen family — computer, tablet or phone — since a page does not have the same shape on each. The pages are listed in the order of the visit, with their number of clicks.
Three views, alone or together
- Scrolling — bands from red, seen by all, to blue, seen by almost nobody, the lines reached by 75, 50 and 25 % of the testers, and the dotted fold line: what shows when the page opens.
- Mouse — the attention map, from blue (little) to red (a lot). This is where the reading path appears, often in a Z.
- Clicks — their density, then one dot per click: red for a left click, purple for a right click, grey on what does nothing, a black ring for rage clicks.
Tick one, two or the three views to lay them on top of each other, and set the opacity of each. Under the map, the figures of the page: tests, clicks, right clicks, rage clicks, clicks on what does nothing, and the share of testers who saw the bottom.
The picture of the page
The heatmap is drawn on a picture of the whole page. It is taken by itself, once per page and screen family, a few seconds after the page opens in the cockpit, for a tester or for the team. Form fields are left empty in it: nothing typed ever shows.
The picture is redrawn by the browser, so a picture loaded from another site may be missing. For a perfect one, open the cockpit, go to the expert tools, Clicks tab, and click « Capture the page for its heatmap ». If a picture cannot be taken, the Behaviour tab says why.
Rage clicks, dead clicks, first click
| Signal | What it means |
|---|---|
| Rage click | Three quick clicks in the same place within a second: the tester is frustrated, something does not answer. |
| Click on what does nothing | A click on an element that is not a link, a button or a field: it looks clickable, but it is not. |
| First click | On a step with an expected element, the first click lands on it or not, and how fast: the clearest sign that a page is understood. |
Videos of the tests
When the campaign records videos, the tester is asked in the start window, and can refuse unless you make it required. For your own test, a small window asks « Record this test as a video? ». The browser then asks to share the screen:
- Chrome and Edge — the tab of the test is offered first: only the page is recorded.
- Firefox — the whole window is shared, and the browser’s bars (tabs, address, bookmarks) are cut off the video.
- Phones — browsers cannot record the screen: the test goes on without video.
In the Behaviour tab, each video shows its tester, date, length and weight. Watch it, jump to the start of each step, download it (WebM, opens with Chrome, Firefox, Edge or VLC) or delete it. A finding sent during the test opens the video at its exact moment. When a test has no video, the reason is written: phone, box not ticked, or sharing refused.
Light by design
Videos are recorded at a low rate, enough to read the text, the emojis and the mouse: about 2 MB a minute. You set the longest video per test (30 minutes by default). Clicks and moves weigh almost nothing: a grid of positions, not a recording of the screen.
Heatmaps in the client’s report
In the Report tab, tick the pages whose heatmaps speak to the client — none by default — and choose the views: the three side by side, or one only. Each view becomes one light picture, side by side in the PDF too. All the heatmaps stay in the Behaviour tab.
Private by default
Only positions are recorded, never what is typed. The tester is told what is measured in the start window. Videos are kept for the time you set in Settings > Data kept, then erased, except for a signed report still within its proof time. Every recording can be switched off, campaign by campaign.
More questions are answered in the FAQ, and each setting is described on the Settings Reference page.