Back to Learning Hub
Comparison8 min readJuly 21, 2026

Arktis vs Hotjar: Session Recordings Alone Aren't Attribution

Hotjar is a strong heatmap and session recording tool, but it stops at showing you what happened on a page. This comparison looks at where Hotjar excels, where it falls short for e-commerce attribution, and how Arktis combines recordings with multi-touch attribution and AI agents.

S

Sara

Co-founder & CTO


If you've used Hotjar, you probably know it for one thing: watching real visitors move through a page via heatmaps and session recordings. It's a genuinely well-built tool for that job. But e-commerce teams trying to answer "which campaign actually paid for this order" run into a wall fast, because Hotjar was built to show what happened on a page, not to connect that behavior to ad spend, revenue, or customer lifetime value. This Hotjar comparison looks at where session recording tools like Hotjar earn their reputation, where they stop short for e-commerce attribution, and what a purpose-built alternative looks like.


The Quick Verdict


Hotjar remains one of the more polished tools for watching how visitors interact with a specific page, particularly for UX research and conversion rate optimization on landing pages. It would be unfair to call it a bad product, its heatmaps and click tracking are genuinely useful for design and product teams doing qualitative research. But Hotjar was never built for multi-touch attribution, CAC and ROAS calculation, or connecting session behavior to actual Shopify or Stripe revenue, and its 2025 acquisition by Contentsquare has left pricing and product structure in flux through 2026. Arktis starts from a different premise: session recordings and heatmap-style insight are one part of a platform anchored in attribution tracking, revenue data, and AI agents, built specifically for e-commerce.


Feature Comparison


Session Recordings and Heatmaps


Hotjar's heatmaps, especially its Engagement Zone view, are among the more developed options on the market for visualizing where users click, move, and scroll on a single page. Session recordings capture clicks, scrolls, mouse movement, and form interaction so a UX researcher can watch a real visitor struggle with a checkout form. The catch is volume: Observe plans cap recordings at 100, 500, or 1,500 sessions per day depending on tier, and once you hit the daily cap, recording simply stops until the next day. Reviewers also note that heatmaps can misread pages with dynamic elements like modals, sticky navigation, and pop-ups, and that recording sampling leaves gaps for high-traffic sites.


Arktis includes session recordings as part of the core platform rather than a bolt-on product, using rrweb to capture full DOM playback with click, scroll, and keystroke counts stored alongside the same visitor and session data used for attribution. Recording capacity scales with the plan's monthly tracked users rather than a hard daily cap, and because recordings live in the same database as pageviews, conversions, and ad click data, a recording of a visitor who abandoned checkout can be pulled up next to the exact campaign and touchpoint that brought them in.


Attribution Tracking


Hotjar has no multi-touch attribution model. It doesn't track fbclid or gclid, doesn't calculate customer acquisition cost, and doesn't connect ad spend to revenue. Its own product framing is explicit about this: Hotjar is built for user experience analytics, not attribution modeling, so teams pair it with Google Analytics or an ads platform's own dashboard to answer "where did this customer come from" and use Hotjar separately to answer "what did they do once they arrived."


Arktis was built around the opposite question first. The tracker captures fbclid and gclid on landing, builds a full multi-touch journey across sessions, and calculates CAC and ROAS per campaign automatically. When a Shopify order comes in, Arktis connects it back through the visitor's touchpoints to the specific ad campaign that introduced them versus the one that converted them, something no combination of Hotjar plus a generic analytics tool does out of the box.


Privacy and Compliance


Hotjar is not GDPR-compliant by default. Documentation and independent privacy reviews note that Hotjar begins recording as soon as its script loads unless a site operator explicitly gates it behind a consent management platform, and that IP addresses, browser identifiers, and device data are collected regardless. Text fields are masked by default, but if masking isn't configured correctly, form inputs including names, emails, and sensitive data can end up visible in a recording. Compliance is achievable, but it depends entirely on the website operator configuring consent gating, retention limits, and IP anonymization correctly.


Arktis gates session recording behind explicit visitor consent at the database level: a visitor's consent_given flag has to be true before any recording chunk is accepted, and the tracker requests consent before rrweb ever loads. There's no separate consent management platform to wire up correctly, the behavior is built into how the tracker and backend communicate by default.


AI and Automation


Hotjar has no AI agents. Its Ask product (surveys and feedback) includes some AI-assisted summarization of open-text responses, but nothing in the platform monitors conversion trends, flags anomalies, or takes action on its own. Interpreting heatmaps and recordings is manual work.


Arktis includes AI agents that watch conversion rates and funnel drop-off in the background, surface anomalies (a sudden spike in checkout abandonment, a campaign whose CAC just doubled) without a human digging through dashboards, and can escalate specific sessions worth reviewing. This is a category Hotjar's product doesn't touch at all.


Pricing at Scale


Hotjar splits its platform into separate products, Observe for heatmaps and recordings, Ask for surveys, and Engage for interviews, each billed on its own. A team wanting both recordings and survey feedback pays for two subscriptions. Following the July 2025 Contentsquare acquisition, Hotjar is migrating existing customers onto Contentsquare's unified tiers (Growth at $49/month, with Pro and Enterprise at custom pricing) through 2026, and billing now comes from a Contentsquare entity rather than Hotjar itself.


Arktis uses one plan that includes attribution, session recordings, and AI agents together rather than as separate purchases, so a growing e-commerce team isn't stacking subscriptions to get a complete picture. See the full pricing breakdown for exact tier limits.


Ease of Setup


Both tools install with a single script tag and no engineering lift for a standard site. Hotjar's setup is well documented and quick, which is a fair strength given how long it's been the default choice for heatmapping. Arktis's tracker installs the same way but is tuned for e-commerce out of the box, auto-detecting Shopify and Stripe checkout events and UTM parameters without extra configuration, since attribution and revenue tracking are first-class rather than something bolted on afterward.


Pricing Comparison


Hotjar


Hotjar's Observe product (heatmaps and recordings) runs Free for a limited trial tier, Plus at $39/month billed monthly or about $32/month annual with 100 daily sessions, Business at $99/month or about $80/month annual with 500 daily sessions, and Scale at $213/month or about $171/month annual with 1,500 daily sessions. Ask (surveys) is priced separately, running free up to roughly $159/month depending on tier. Teams who want recordings and surveys together are effectively paying for two products. Hotjar's pricing structure is in the middle of a migration to Contentsquare's unified tiers, starting at $49/month for Growth with Pro and Enterprise at custom pricing, through 2026 (see sources below).


Arktis


Arktis has a free tier covering 1,000 sessions per month forever, no credit card required. Iceberg Starter is $49/month for up to 50,000 monthly tracked users. Growth is $149/month for up to 250,000 monthly tracked users and adds session recordings and custom attribution. Scale is $349/month for unlimited users with raw data export and API access. Every tier includes attribution tracking from day one, unlike tools where it's a separate product or missing entirely. Full details on pricing.


When to Choose Hotjar


Hotjar is a reasonable choice if you're a UX researcher or product designer who mainly needs to watch page-level behavior on marketing or landing pages, run quick heatmap studies before a redesign, collect open-text survey feedback through Ask, or you already have a separate analytics and ads attribution stack and just need a bolt-on tool for qualitative research, since Hotjar was built and refined for exactly that use case over more than a decade.


When to Choose Arktis


Arktis makes more sense for e-commerce brands running paid campaigns on Facebook or Google who need to know which campaigns actually generate revenue rather than just clicks, teams that want session recordings and heatmap-style visual insight bundled with multi-touch attribution tracking, CAC, and ROAS in a single dashboard instead of stitching together two or three tools, and teams that want AI agents flagging conversion problems automatically instead of manually reviewing recordings to find them. Check the product page for the full feature list.


Migration is Simple


Switching from Hotjar to Arktis doesn't require ripping anything out first. Install the Arktis tracker script alongside your existing Hotjar tag, run both in parallel for a week or two to compare data, then remove Hotjar once you're confident in the numbers. There's no data migration needed since Arktis starts collecting fresh from install.


The honest takeaway is that Hotjar and Arktis solve different problems that happen to overlap on session recordings. If your bottleneck is understanding whether a specific ad campaign is actually profitable, Hotjar was never built to answer that question, and Arktis was built for little else.


Sources

1. Hotjar Pricing 2026, "Observe + Ask Plans From Free to $372/mo Combined" (2026)

2. Hotjar Documentation, "Hotjar Plans" (2026)

3. Hotjar Documentation, "What Is Included in the Observe Scale Plan" (2026)

4. Hotjar Documentation, "Hotjar is merging into Contentsquare - Billing and Legal changes" (2025)

5. FullSession, "Contentsquare Acquires Hotjar: What It Means" (2025)

6. Lokker, "Hotjar Session Replay Privacy Risk, Consent, and GDPR Compliance" (2026)

7. FullSession, "Hotjar Review 2026: Features, Pricing, and Limits" (2026)

Frequently Asked Questions

Does Hotjar offer multi-touch attribution?

No. Hotjar is built for user experience analytics, heatmaps, session recordings, and surveys, not attribution modeling. It doesn't track fbclid or gclid, doesn't calculate CAC or ROAS, and doesn't connect campaigns to revenue. Teams typically pair Hotjar with a separate analytics or ads platform to get attribution data, then use Hotjar separately for behavioral insight.

How many sessions can Hotjar record per month?

It depends on the Observe plan. Plus includes 100 daily sessions, Business includes 500 daily sessions, and Scale includes 1,500 daily sessions, roughly 3,000, 15,000, and 45,000 sessions per month respectively. Recording stops once the daily cap is hit and resumes the next day.

Is Hotjar GDPR compliant by default?

Not by default. Hotjar begins recording as soon as its script loads unless the site owner explicitly gates it behind a consent management platform, and it collects IP addresses, browser identifiers, and device data regardless of consent status. Compliance is achievable but depends on the website operator correctly configuring consent gating, data retention, and IP anonymization.

What happened to Hotjar after the Contentsquare acquisition?

Contentsquare completed its acquisition of Hotjar in mid-2025. As of 2026, Hotjar customers are being gradually migrated onto Contentsquare's unified pricing tiers (Growth, Pro, Enterprise), billing now comes from a Contentsquare entity rather than Hotjar, and Hotjar's separate Observe, Ask, and Engage products are being folded into the broader Contentsquare platform.

Can I use Arktis and Hotjar at the same time during a switch?

Yes. Both install as a single script tag with no conflict between them, so you can run the Arktis tracker alongside an existing Hotjar tag, compare data for a week or two, and remove Hotjar once you're confident in the new numbers.

Does Arktis include heatmaps like Hotjar?

Arktis focuses on full session recordings with rrweb-based DOM playback rather than static heatmap grids, giving you the actual visitor journey (clicks, scrolls, keystrokes) alongside attribution and conversion data in the same dashboard, rather than heatmaps as an isolated product.

Try Arktis free for 7 days

Attribution tracking, session recordings, and AI automation in one platform. Set up in 2 minutes, no credit card required.

Start 7-day free trial

Written by

S

Sara

Co-founder & CTO

Sara architects Arktis's technical infrastructure, specializing in AI agents and real-time data processing systems.