Genetic.codes
All solutions
Website interaction heatmaps

Where visitors actually go on your site

A heatmap over your own pages showing where people move, what they click, and how far down they get before they stop.

Who it is forFor anyone guessing why a page does not convert.
The problem

Analytics tells you how many left, not why.

A page has visitors and no inquiries. The numbers say people arrived and went away again. They do not say that everybody stopped just above the section you consider the point of the page.

Redesigns then get argued from opinion, because nobody in the room has actually seen what visitors do on the page.

Traffic without inquiries and no explanation
Design decisions settled by whoever argues hardest
No idea what phone visitors ever see

A script on the page, a view on top of it.

Embed01

One script on the pages you want to watch. No change to how the site is built.

One script
Collect02

Pointer movement, clicks, taps and scroll depth are recorded as aggregate positions, not as recordings of people.

Aggregate only
View03

The heat is drawn over a live render of the page, per device width, for the period you choose.

Per device widthImage export

What you get

Movement and click maps

Where attention goes and where it turns into a click, on the actual layout of the page.

Scroll depth

How far down the page people get, and which section is the one they stop above.

Split by device width

Phone and desktop behave differently. They are shown separately rather than averaged into one misleading picture.

Clicks on things that are not links

People clicking something that does nothing is a design finding worth having.

Compare periods

Look at the same page before and after a change and see whether the change did anything.

No visitor identification

Aggregate positions only. Nothing that identifies an individual visitor is collected.

What it fits with
Any HTML site or web appSingle-page applicationsStaging and production side by sideSelf-hosted on your own infrastructureExport as image for reportsConsent tooling you already use

It can run on your own servers, which keeps the data on your side.