Is Hotjar still Hotjar, or is it Contentsquare now?
Hotjar is now sold as Contentsquare. As of November 2026, Contentsquare’s Hotjar page says it is no longer possible to create a Hotjar account, new users sign up for Contentsquare’s Free plan, and hotjar.com’s pricing page shows Contentsquare’s plans. This comparison uses those plans, since they are what you can buy.
Existing Hotjar accounts are being moved in phases that began on August 26, 2026. Per Contentsquare’s migration FAQ, an account gets 30 days with both products, then switches to the Contentsquare Growth plan unless the owner opts out. The price may change. Hotjar’s heatmaps, recordings, funnels and dashboards do not move across: they stay read-only in Hotjar for 12 months and are then deleted. Surveys and feedback do move.
Contentsquare is an experience analytics suite: session replays, heatmaps, funnels, surveys, error and performance monitoring, and AI summaries. invisit is cookieless web analytics with heatmaps and a feedback widget. It has no session recordings, which were Hotjar’s main product, so invisit replaces only the heatmap, feedback and analytics half of Hotjar.
How much does Hotjar cost now?
Contentsquare is free up to 200,000 sessions a month, with one project, one month of data and replays for 5% of sessions. Its Growth plan runs from $49 a month for 7,000 sessions to $739 for 200,000 on monthly billing, and beyond that it is quoted, as of November 2026 (pricing). invisit charges by events, from $14 for 100K to $199 for 10M.
The two meter different things. Contentsquare counts sessions, which end after 30 minutes without activity. invisit counts page views, custom events, conversions and short-link clicks, so one visit costs at least one event and usually several. The tables on this page count one session as one event, which favours Contentsquare.
| Contentsquare Growth, monthly | Sessions a month | Replays recorded |
|---|---|---|
| $49 | 7,000 | 7,000 |
| $119 | 20,000 | 20,000 |
| $279 | 60,000 | 20,000 |
| $409 | 100,000 | 20,000 |
| $739 | 200,000 | 30,000 |
A worked example: a site with 60,000 sessions a month that average three page views sends invisit 180,000 page views, which the 250K plan covers for $24. Contentsquare Growth at that volume costs $279 and records 20,000 of those sessions. Contentsquare Free covers the same traffic for $0, with replays of 3,000 sessions and one month of history.
That last line is the honest catch: up to 200,000 sessions, Contentsquare Free is cheaper than any paid invisit plan. What it gives up is history (one month, against invisit’s forever), sampled replays, and Growth’s journey analysis and AI features.
When a Free or Growth month runs out of sessions, Contentsquare stops collecting new sessions until the next month (plan limits). invisit warns at 80%, records the first month over in full, and pauses new events only after a second month over in a row (billing). Contentsquare’s yearly billing saves 20%; an invisit year costs nine months’ price.
Does Hotjar need a cookie banner?
Usually, yes. Both the Hotjar tracking code and the Contentsquare tag store visitor IDs on the device, and both leave the consent question to you. invisit sets no cookies and stores nothing on the device by default, so its analytics and heatmaps need no banner.
- Hotjar sets
_hjSessionUser_{site_id}, a user ID kept for 365 days, plus a session cookie, on the top-level domain and every subdomain. It does not track visitors with cookies disabled, and its cookie docs point you to a consent tool and your own lawyer. - Contentsquare sets
_cs_idfor 13 months and_cs_sfor the session. Its cookieless mode writes the same items to localStorage and sessionStorage instead (cookies), which is still storage on the device. - Contentsquare’s privacy FAQ says it collects IP addresses (deleted after 3 days by default) and an online unique ID through cookies.
invisit tells visitors apart with a hash that rotates every day, never stores raw IP addresses, and can honour Global Privacy Control and Do Not Track. If your policy wants consent anyway, requireConsent holds every event until the visitor agrees (privacy guide).
Where does Hotjar store data, and for how long?
Hotjar stores data in Ireland on AWS eu-west-1, per its security page. Contentsquare hosts EU customers in its EU region by default and US customers in the US. Its security page lists EU pipelines on AWS and Azure in Ireland. invisit stores every site’s data in Falkenstein, Germany, on Hetzner, with Cloudflare, a US company, in front for DNS and CDN.
How long data stays is the bigger difference. On Contentsquare’s Free plan, analytics and replays are available for one month. Growth keeps analytics 13 months and replays 2 months. invisit keeps every plan’s data forever, so a heatmap or a visit from two years ago is still there.
Contentsquare’s privacy FAQ also says it may process personal data as a controller for internal development, alongside its processor role under the DPA. invisit’s DPA is at /legal/dpa.
How big is the Hotjar script?
The Hotjar tracking code loads about 78 KB gzipped, and the Contentsquare tag about 251 KB. invisit’s core script is about 9.8 KB, and its heatmap and feedback modules load only when those features are on.
| Script, measured 16 November 2026 with gzip -9 | Gzipped |
|---|---|
Hotjar loader hotjar-<site id>.js, with the site’s settings |
6.7 KB |
Hotjar modules.js, which the loader always fetches |
71.2 KB |
Contentsquare loader uxa/<tag id>.js (contentsquare.com’s own) |
7.5 KB |
| Contentsquare tag runtime (15.284.4), shared by projects on it | 244.0 KB |
invisit invisit.js |
About 9.8 KB |
Both vendors load asynchronously, and Contentsquare’s tag delivery docs note the runtime is cached long-term between releases. Size still matters on the first visit and on slow phones. The script size test puts the other analytics trackers on the same scale.
Hotjar heatmaps and feedback compared with invisit
Both draw heatmaps over your live pages and both collect feedback from visitors. Contentsquare does more of each; invisit does them without cookies and keeps them forever.
| Feature | Contentsquare (Hotjar) | invisit |
|---|---|---|
| Clicks and scroll depth | Yes | Yes |
| Rage and dead clicks | Yes; frustration score and filters from Growth | Yes |
| Attention maps | Yes | No |
| Zone-based heatmaps | From Growth | No |
| Session replays | 5% of sessions free, all up to 20K on Growth | No |
| Surveys and NPS | Yes; 3 surveys or widgets and 100 responses a month free | No |
| Feedback widget | Yes | A message and an optional email, linked to the visit |
| History | 1 month free, 13 on Growth | Forever |
| Billing | Sessions | Heatmap clicks, scroll depth and feedback never billed |
invisit stores each click as the element it landed on, so heat stays on the right button when the layout shifts, and it marks rage and dead clicks on every plan (heatmaps). Feedback sent through the widget links to the visit it came from, and invisit’s visit timelines show every page and event of that visit step by step: the closest invisit gets to a recording, and it is a list, not a video.
When Hotjar is the better choice
Contentsquare, Hotjar’s successor, is the better pick over invisit when you need to see what visitors did rather than count it. In particular:
- Session recordings. Watching a visitor struggle with a form is Hotjar’s core, and invisit has nothing like it.
- Surveys and research. NPS, multi-question surveys, embedded surveys and AI survey analysis, up to 100,000 responses a month on Growth.
- Richer heatmaps. Attention maps, zone-based metrics and side-by-side comparisons.
- AI on top. Replay and heatmap summaries, a chat over your data, and an MCP server on every plan.
- Mobile apps. Contentsquare analyses native iOS and Android apps.
- Free volume. 200,000 sessions a month on the Free plan, if one month of history is enough.
- Enterprise depth. Revenue attribution, AI agent analysis, alerts and APIs on the quoted Pro and Enterprise plans.
For a full comparison of recording tools, see the Microsoft Clarity alternatives guide.
Switching from Hotjar to invisit
Moving from Hotjar to invisit is a short code change, as long as you can live without recordings. invisit cannot import Hotjar data, so export what you want first.
- Export your history. Hotjar exports recording lists and their metadata as CSV or XLSX, heatmaps as JPG or CSV, and survey responses as CSV or XLSX. Recordings cannot be downloaded as video. If your account has moved to Contentsquare, Hotjar stays read-only for 12 months and is then deleted.
- Install invisit next to the Hotjar code, then turn on heatmaps and the feedback widget for the site in the dashboard. Clicks are recorded from then on.
- Map the calls. invisit event names use letters, digits and
_ . : -and can carry up to 32 properties (events guide), which Hotjar’s events cannot.
| Hotjar | invisit |
|---|---|
hj('event', 'signed_up') |
track('signed_up'), with properties if you want them |
hj('identify', userId, attributes) |
identify(userId), stored hashed; attributes have no equivalent (identify) |
hj('stateChange', url) for SPAs |
Nothing: the tracker follows client-side navigation |
| Feedback widget and surveys | The feedback widget, or sendFeedback() from your own form |
| Recordings | No equivalent; visit timelines list each visit’s pages and events |
// Before: Hotjar
hj('identify', user.id, { plan: 'pro' })
hj('event', 'signed_up')
// After: invisit
import { identify, init, track } from '@invisitdev/web'
init({ site: '<site id>' })
identify(user.id)
track('signed_up', { plan: 'pro' })- Run both for two to four weeks and compare page views. Visitor counts will differ: Hotjar remembers a visitor for up to a year with a cookie, while invisit’s hash rotates daily.
- Remove the Hotjar code. If your consent banner existed only for Hotjar, review whether your site still needs it.