Integrate Hotjar for Heatmaps & Session Recordings
Your online store is live, but conversion is lower than expected. According to Baymard Institute, 70% of users abandon carts due to poor interface. Without behavior analytics, you’re left guessing why they leave. Hotjar solves this by recording sessions and building heatmaps—visualizations of clicks, scrolls, and mouse movements. We, a team with 7+ years in web analytics, integrate Hotjar into your project within a day. A heatmap is key for UX understanding. Our clients save up to 40% analysis time, and post-optimization conversion grows 20–30% based on Hotjar data. Request a free consultation to assess your site.
Why Hotjar Outperforms Log Analyzers
Log analyzers show what users clicked, but not why. Hotjar records the full session: cursor movement, gaze dwell. Research indicates that UX issues are discovered twice as fast with Hotjar. Click heatmaps reveal up to 30% of clicks on non-clickable elements—actionable data for targeted fixes.
How Hotjar Unveils UX Issues
Hotjar generates three heatmap types: click maps, move maps, and scroll maps. Click maps show exactly where users click—often on non-clickable elements. Move maps track cursor movement, correlating with attention. Scroll maps indicate how far users scroll. Combined, they provide a complete picture. For instance, on one project we detected 70% of clicks landing on an empty area right of a form—solved by widening the input field.
Data from Session Recordings
Session recordings are videos of each visitor’s actions. You see how users fill forms, where they hesitate, which validation errors appear. Funnels show drop-off at each step. Surveys allow on-site polling. All this data drives pinpoint UX improvements.
Installing Hotjar in 30 Minutes
We install Hotjar via Google Tag Manager or direct code in <head>. Below is the GTM snippet:
<!-- Hotjar Tracking Code -->
<script>
(function(h,o,t,j,a,r){
h.hj=h.hj||function(){(h.hj.q=h.hj.q||[]).push(arguments)};
h._hjSettings={hjid:YOUR_SITE_ID,hjsv:6};
a=o.getElementsByTagName('head')[0];
r=o.createElement('script');r.async=1;
r.src=t+h._hjSettings.hjid+j+h._hjSettings.hjsv;
a.appendChild(r);
})(window,document,'https://static.hotjar.com/c/hotjar-','.js?sv=');
</script>
Trigger: "All Pages". Publish the container.
Next, configure user identification and events:
// User identification
window.hj('identify', userId, {
plan: 'pro',
email: userEmail,
country: 'US',
});
// Events
window.hj('event', 'form_opened');
window.hj('event', 'add_to_cart');
window.hj('event', 'form_validation_error');
window.hj('event', 'form_submitted');
In the Hotjar interface → "Recordings", filter sessions by attributes or events.
Data Privacy
Hotjar blurs password inputs by default. For other personal fields, explicitly add classes:
<input type="text" name="card_number" class="data-hj-suppress">
<div class="data-hj-suppress">
<p>SSN: 123-45-6789</p>
</div>
<input data-hj-suppress type="text" name="passport">
You can also set global CSS selectors in the site settings—no code changes needed.
Configuring Hotjar for SPAs
In SPAs, the router changes URL without full reload. Hotjar by default creates heatmaps based on URL—if URL doesn't change, all events merge into one map. The solution: manually notify Hotjar of page changes:
// React Router v6
import { useEffect } from 'react';
import { useLocation } from 'react-router-dom';
export function HotjarPageTracker() {
const location = useLocation();
useEffect(() => {
window.hj?.('stateChange', location.pathname + location.search);
}, [location.pathname]);
return null;
}
For Next.js, use the routeChangeComplete event.
Common Integration Mistakes
Frequent issues: wrong Site ID (counter not verified), empty heatmaps due to missing data (wait 1-2 hours), non-recording sessions (enable Recordings), and events not firing due to typos. All errors are easily diagnosed via browser console and Hotjar dashboard.
What Our Integration Service Includes
| Step |
What We Do |
Timeline |
| Counter installation |
Place code on all pages via GTM or directly |
30 minutes |
| User identification |
Pass user attributes (email, plan, registration date) |
2-3 hours |
| Event setup |
Tag key actions (form, cart, error) |
1-2 hours |
| Data masking |
Configure hiding of sensitive fields |
1 hour |
| Testing |
Verify recordings and heatmaps |
1 hour |
| Documentation |
Provide setup description and instructions |
included |
Timelines and Cost
Counter installation: 30 minutes. Full cycle (identification, events, masking, tests): 2 to 5 days. Cost is determined individually. Request a free estimate—we’ll analyze your site and propose an optimal plan.
Optimize your site based on Hotjar data. Our engineers help you get the most from heatmaps and session recordings; contact us for a consultation on Hotjar integration.
Feature information sourced from official documentation: Hotjar Help Center
Setup Web Analytics: GA4, GTM, Yandex.Metrica, and Amplitude
We often see: conversion rate 1.2%, traffic grows, but conversion stays flat. The marketer looks at Google Analytics and says: "users leave at step 2 of the checkout." The developer opens the same step — no errors, Sentry is silent. So it's not a JS bug, but a UX issue or skewed data from analytics. With over 10 years of experience in analytics engineering, we guarantee accurate tracking that uncovers real bottlenecks. Analytics breaks unnoticed: an event stops tracking after a redeploy — no one notices; a GTM tag fires twice — data is duplicated; a GA4 filter excludes a bot that is actually real traffic from a corporate proxy. An audit of your current tags will find the cause within a week.
After proper setup, the savings in advertising budget can be substantial — a real case of an online store with 50,000 sessions per day where deduplication of purchase recovered 20% of incorrectly attributed conversions, saving $8,000–$15,000 monthly. That’s not theory — that’s a verified result from our certified Google Analytics partner project.
Why do GA4 events duplicate and how to fix it?
Universal Analytics is gone, replaced by GA4's event-based model. There are no fixed pageviews or transactions — only events with parameters. This is more flexible but requires proper event design. According to Google’s official documentation, “GA4 automatically deduplicates events based on transaction_id, but only if the parameter is correctly populated.” Many implementations miss this.
Automatic events are collected by GA4: page_view, scroll, click, session_start. Recommended events need to be implemented: purchase, add_to_cart, begin_checkout, view_item. Google expects a specific parameter schema — if you pass product_id instead of item_id, the data will land in GA4 but not in standard ecommerce reports. Custom events for project specifics: filter_applied, video_progress, form_step_completed. Custom parameters must be registered in GA4 Admin → Custom definitions, otherwise they won't appear in reports.
A common mistake is the purchase event being duplicated. Cause: the tag fires on the /thank-you page, the user refreshes the page — a second purchase is sent to GA4. Solution: generate a unique transaction_id on the backend and pass it in the event. In our experience, 80% of e-commerce stores have this issue. GA4 deduplicates based on it (in theory — verify with DebugView). Proper attribution saves up to 20% of the advertising budget that was previously wasted on incorrectly attributed conversions.
How to set up the data layer to avoid data loss?
GTM is a tool for managing tags without code deployment. But "no code" doesn't mean "no architecture." The data layer is the foundation. We pass data from the application to GTM via dataLayer.push(). Structure: event + contextual data. For e-commerce: before opening a product page — push with product data. GTM tag reads from the data layer, not from the DOM.
window.dataLayer = window.dataLayer || [];
dataLayer.push({
event: 'view_item',
ecommerce: {
items: [{
item_id: 'SKU-12345',
item_name: 'Product name',
price: 1990.00,
currency: 'USD'
}]
}
});
Bad practice: GTM tag parses the DOM — looks for the price in span.price, the name in h1. This breaks with any layout change. Good practice: always use the data layer. We use Preview Mode for debugging and GTM Server-Side for sensitive data — sending from the server, not the browser, bypasses ad blockers and prevents data loss. A properly implemented data layer reduces tracking errors by 95%.
How does Yandex.Metrica complement web analytics?
For a Russian audience, Metrica is a must — especially Webvisor. Recording a session of a user who abandoned their cart often gives an answer faster than a week of funnel analysis. Goals in Metrica: event-based (via ym(COUNTER_ID, 'reachGoal', 'GOAL_NAME')) or automatic (button click, page visit). Integration with CRM via Metrica Plus — passing offline conversions. Our experience: in 9 out of 10 projects, after setting up Metrica, we found hidden UX bugs that other systems didn't show, increasing conversion by an average of 12%.
What does product analytics give in Amplitude?
Amplitude is a product tool, unlike marketing-oriented GA4 and Metrica. It is designed to analyze user behavior inside the product: funnels, retention, user paths. Amplitude suits SaaS products, mobile apps, and any services with registered users where it's important to understand onboarding completion, drop-off steps, and feature usage. Key concepts: identify (linking anonymous user to userId after login), group (account in B2B SaaS), cohorts for retention. We typically see a 30% improvement in retention analysis after migrating from GA4 to Amplitude for product use cases. Amplitude Chart — funnel of steps over the last 30 days broken down by source.
Monitoring Data Quality
Analytics without monitoring is a black box. We set up:
- GA4 Realtime — check after every deploy that key events are coming in
- Alerting in GA4 — anomaly in the number of
purchase events (sharp drop = something broke)
- GTM Preview in staging before production
- Manual funnel tests once a week — simply go through the buyer journey and verify everything is tracked
What we check after each deploy
- All recommended events present in DebugView
- No duplicates (count
purchase per 100 sessions)
- Data layer structure unchanged after frontend update
What the work includes
| Component |
Description |
| Audit of existing tags |
Check current GTM tags, data layer, duplicates, and errors |
| Event schema design |
Documentation: event list, parameters, triggers |
| GA4 + GTM setup |
Create configuration, tags, custom definitions |
| Yandex.Metrica |
Install counter, create goals, set up Webvisor |
| Amplitude (optional) |
Set up client and server SDK, cohorts |
| QA and monitoring |
Testing in Preview Mode, alerting |
| Training and handover |
Access, instructions for adding new events, console |
Process and timeline
- Audit of existing tags and data (2 days)
- Event schema design (2 days)
- Data layer development and tag setup (3–5 days)
- QA in Preview Mode and staging (2 days)
- Deploy and dashboard setup (1 day)
| Scenario |
Timeline |
| Basic GA4 + GTM setup |
1 week |
| Full e-commerce tracking + Metrica |
2–3 weeks |
| Server-side GTM + Amplitude |
3–5 weeks |
Cost is calculated individually. Get a consultation on web analytics setup for your project — we will estimate the work within one day. Contact us to get started with a free audit of your current tracking.
