Conversion Signals — how it works

Watch what real visitors do on your live page. Rage clicks, dead clicks, and scroll drop-off are overlaid on a screenshot of the page so you can see exactly where people get stuck and which fix moves the needle first.

Category: Get Started
Reading time: 7 min

Quick fix

In a hurry? Try this first.

Add your site, paste the one-line script into your site's <head>, and your first report lands a minute after the first visitor.

What you are looking at

Conversion Signals is a behaviour overlay on a screenshot of your real page. Each coloured region is a place real visitors did something the page did not expect, and that almost always points to a clarity, friction, or hierarchy problem you can fix.

You will see three kinds of signal: rage clicks (red), dead clicks (amber), and a scroll-depth overlay along the page. They each answer a different question.

Setting it up the first time

Conversion Signals needs a one-line tracking script on your site. Once it is installed, every visitor's behaviour starts streaming in automatically. No tagging individual elements, no event configuration.

Add your site
Click Add site on the Signals index page. Enter your domain. Levri generates a unique site key for you.
Install the script
Copy the snippet shown in the install step and paste it into your site's <head>. It is one async script tag with your site key inline. Works on any platform that lets you add a script (Webflow, Framer, Shopify, Wordpress, custom builds).
Wait for the first events
As soon as a visitor lands on the page, events start flowing. The site status flips from Not installed to Collecting within seconds of the first event.
First report
About one minute after the first event, Levri auto-builds your first report. Building takes 10 to 30 seconds. After that the site is Ready and you can click into the detail view.

Site statuses on the index

Each site on the Signals index shows a coloured dot and a status label that tells you exactly where it is in the pipeline.

Not installed (gray). The script has not fired yet. Continue setup is the primary action.
Collecting (sky, pulsing). Script is firing and events are streaming, but Levri does not have enough signal yet to build a report.
Building report (violet, pulsing). Levri is processing the first batch of events. Usually 10 to 30 seconds.
Ready (emerald). A report exists and you can view signals.
Needs attention (amber). The script has been quiet for a while. Either traffic dropped, or the script was removed from the page.

Rage clicks

Rage clicks are bursts of repeated clicking on the same spot in a short window. A visitor expected something to happen, nothing did, and they hammered the same area trying to make it respond.

Dead clicks

Dead clicks are single clicks on a non-interactive element. The visitor saw something they thought would respond (an image, a piece of text, an icon) and tapped it. Nothing happened. They moved on, often off the page entirely.

Dead-click clusters on hero images, logos, or product photos are the most common. Visitors expect them to enlarge, scroll, or open a detail view. The fix is either making them interactive or making them clearly static.

Scroll depth

Scroll depth shows the percentage of visitors who reached each vertical section of the page. A steep drop between two sections is the loudest signal there is. Whatever sits above the cliff is the section visitors are bailing on.

Controls on the detail page

Once a site is Ready, clicking into it opens the detail view. The toolbar gives you everything you need to slice the signal:

Path + Device picker. Pick which page (homepage, pricing, checkout) and which device size (desktop, mobile, tablet) you want to look at. Each combination has its own report.
Sessions counter. How many sessions are behind the current report. Bigger is more confidence.
Refresh capture. Re-runs the screenshot and recomputes the zones for the active path and device. Use this after you ship a change to the page.
Signal type tabs. Switch between Clicks, Rage, Dead, and Scroll. Each tab filters the overlay so you can read one signal at a time.
Intensity slider. Adjusts how strong the heatmap looks. Useful when the page is dark or busy.
Scroll overlay toggle. On by default for Scroll tab, off elsewhere.

Inspecting a zone

Numbered badges on the screenshot mark each detected zone. Click a number on the canvas or a row in the problem list on the left to open the detail panel on the right.

The detail panel shows the zone type, a cropped close-up of the element visitors clicked, and the CSS selector that matched it. That tells you exactly which element on your page is the source of the signal.

How to read the screenshot

Scan from top-left, the same way visitors do. For each red or amber zone, ask three questions:

What element is the visitor clicking?
What did they probably expect to happen?
What does the page actually do (or not do)?

The gap between expectation and reality is the fix. Most of the time it is a label change, an interaction added, or removing a misleading visual cue. Not a redesign.

How to prioritise

Start above the fold
Issues in the first viewport affect every visitor. Issues deeper down only affect visitors who already scrolled past the earlier ones.
Pick rage over dead
Rage clicks signal active frustration, not just confusion. Fixing them recovers visitors who are already engaged enough to click hard.
Then chase the scroll cliffs
Once the loud above-the-fold zones are addressed, scroll-depth cliffs tell you which mid-page section is bleeding the remaining audience.

Common new-user questions

Do I need to install something? Yes. Conversion Signals needs the one-line tracking script on your site. Without it, no events flow in. The setup step on the Signals index walks you through it.
How long until I see my first report? About one minute after the first visitor lands on the page. Levri waits for a small batch of events, then builds. Building itself takes 10 to 30 seconds.
Why does my site say Needs attention? The script has been quiet. Either real traffic genuinely dropped, or the script tag was removed from the page during a deploy. Re-paste it and traffic resumes immediately.
Can I track multiple pages? Yes. The script tracks every page on your domain automatically. Pick which page to view from the Path picker in the detail view.
Does the screenshot match what visitors see? Yes. Levri captures the screenshot at the same viewport size visitors are using (separate captures per device).
Can I get heatmaps for staging or auth-walled pages? No. The tracking script needs to be live on the public page for visitors to fire events.

Feedback

Was this helpful?

We read every answer — it shapes the next article.

Still stuck?

Talk to a human. Today.

Our team can unblock a specific site, walk you through a screenshot, or diagnose a tricky failure. We reply to most messages within one business day.

Unblock WAF / Cloudflare issues
Diagnose failed analyses
Help with your report + next steps