Heatmaps and session recordings answer a question aggregate stats often miss: what did the visitor actually do on screen? Where did they look for a button, did they scroll to important content, did they get stuck on a form field? These tools do not replace traffic and lead metrics — they are a visual explanation layer on top.
This guide separates the concepts, explains when each helps, and describes how Insytix includes heatmaps in the dashboard and session recordings as a paid add-on — without overstating features the product does not have.
One critical Insytix detail: a session recording does not create an extra page_view, and visitor card statistics count normal tracking events. Watching a recording does not change lead counts — leads come from events such as form_submit and phone_click.
The same rule applies when leaving KPI cards: if forms rose but views did not, replays did not “create” the change — you likely improved the page or traffic quality shifted.
What is a heatmap?
A heatmap is a view that overlays activity points (mainly clicks) on a screenshot or page layout. Heavy click areas show hot colors; quiet areas stay cool. In Insytix, heat data comes from existing tracking: click totals, mobile versus desktop split, and top engaging pages — in the insights area of the dashboard.
A useful heatmap reveals buttons people try to click that are not links, or content below the fold few reach. It is weaker for understanding a full journey sequence — recordings handle that better.
What is session replay?
Session recording stores a log of browser interactions — scrolls, clicks, page changes — and lets you play them like sped-up video. It helps spot frustration: a form never submitted, a menu that fails on mobile, an error after a click.
In Insytix recordings are a paid add-on enabled from site feature settings. Data is stored apart from statistical events. Once on, recordings appear in the dashboard by period and filters — without automatically inflating page view counters.
When to use heatmaps
Heatmaps fit single-page optimization: campaign landing page, service page with contact button, or product page with CTA. After a week or two of enough traffic, open click summary and check whether the CTA gets clicks or visitors click irrelevant elements.
On mobile, desktop versus mobile gaps in heat data often explain conversion drops — button too small, phone below the fold. Fix layout first, measure again — do not wait for a hundred recordings if the visual issue is obvious.
The insights UI also shows numeric summaries — total clicks, device split, top pages — before you dive into a single replay. That saves time when sorting long session lists.
When to use recordings
Recordings pay off when the bug is hard to reproduce: “the client said the form failed” or “leads dropped without traffic falling.” Pick a recording with form_submit that went nowhere or a short session exiting checkout. That beats guessing the drop-off cause.
⚠️ Recordings can hold sensitive data — form fields, sometimes typed text. Do not share view links with parties not bound by confidentiality, and update privacy policy before enabling.
Combining with Insytix statistics
Recommended flow: spot an unusual change in KPI cards or charts (for example formSubmissions drop). Check traffic source — is the shift mobile. Then open heatmap for that page. If still unclear — find a recording from that day and device.
Stats say “there is a problem,” heat points to “where on the page,” recording shows “what the visitor did.” Without the stats layer, watching random recordings wastes time.
Briefly note what you learned after each replay — otherwise the team re-watches the same sessions without changing the site.
Limits and realistic expectations
Heatmaps need click volume — on ten visits per day the picture is not representative. Recordings do not capture outside the browser (not a native app unless it is a WebView). Password fields are often masked industry-wide, but do not treat that as a substitute for care.
Insytix is not a full A/B platform for parallel variants; it helps diagnose a live page. If you run two designs, tag traffic with UTM and compare stats before and after.
On a short campaign, heat alone may suffice; over a year many teams add recordings for recurring UX fixes.
Enablement and privacy
Heatmaps lean on tracking already installed — usually no separate step beyond a live tag. Session recordings need explicit add-on enablement and legal responsibility: updated privacy policy, consent when required, and limits on who may watch.
Insytix owner documentation states that recordings or heatmaps require visitor transparency. Adapt wording with counsel if you handle sensitive data (health, finance, minors).
Common mistakes
- Turning on recordings without updating privacy policy.
- Interpreting heatmaps from pages with tiny traffic.
- Assuming recordings increase visitor counters in the dashboard.
- Sharing recordings widely without access control.
Scroll depth and on-page attention
Besides click heat, advanced analytics sometimes show scroll depth — how far down the average visitor went. In Insytix some insight panels lean on the same tracking events, not on replay. That is enough to ask whether people see pricing or testimonials before leaving.
If scroll is weak on a long page, consider shortening, raising the CTA, or splitting into two landings. If scroll is strong but leads are flat, the offer or form field is suspect — recordings may earn their cost there.
The recording add-on is turned on from site Features; until then no replays are collected and no extra privacy surface exists beyond normal stat tracking.
Summary
Heatmaps and session replay explain behavior; Insytix statistics measure outcomes. Use dashboard heat for click patterns, and the recording add-on when you need a full path or a specific failure. Protect privacy, separate event counts from watching replays, and always tie analysis to one business question.
With no traffic there is no meaningful heat or replay — confirm tracking first, then return to the visual layer.
Frequently Asked Questions
Does heatmap need separate installation?
In Insytix heatmaps rely on tf.js tracking already on the site. Without live tracking there is no heat data.
Are recordings included in every plan?
Session recordings are a paid add-on enabled per site in feature settings. Dashboard heatmaps are not the same product as recordings.
Why do I not see a recording for every visitor?
Recording depends on enablement, sampling, volume, and storage. Not every session is kept for playback; focus on sessions with a known issue or a relevant date filter.