How a visit becomes something you can watch

It takes four places and one line that matters: the edge of the visitor’s browser, where masking has already happened.

You add a script to your site
Two script tags, with your environment’s public key. The script is under 40 KB gzipped and loads asynchronously, so it doesn’t hold up your page.
Install
```
<script>…heatlytics.init({ key, host })…</script>
<script async src="…/heatlytics-<version>.min.js"></script>
```
It records the visit in the browser
Heatlytics records the page’s structure and changes rather than video, along with clicks, scrolling and page changes. It also spots rage clicks, dead clicks and U-turns as they happen.
Sensitive data is masked before it leaves
Password, email and phone fields, and recognised card and bank fields, become asterisks in the browser, and long numbers do in any text field. You can mask or block anything else, and hold recording until the visitor consents.
Security and privacy
- Email******************
- Card number**** **** **** ****
- Password***************
Batches are sent and processed
The script sends compressed batches. Country and city come from Cloudflare’s location headers, and the IP address isn’t stored. Heatlytics then works out page views, entries and exits, quick exits and friction tags.
- Page views
- Entries and exits
- Quick exits
- Friction tags
- Country and city
- IP address: not stored
You find the story
Start from a number on a dashboard or funnel, or from a page’s heatmap, and open the recordings behind it. Every screen can be filtered the same way.
See all features

Or watch one visit go through it

A short film, without sound: someone gets stuck, Heatlytics marks the moment, you watch it, and you know what to fix.

40 seconds, no sound. A visitor gets stuck at checkout, Heatlytics records the visit and marks the moment, you watch it, and you fix it.

Tell us about your website, and we’ll walk through these steps with it in mind.