Hotjar Mobile Integration: Heatmaps & Session Recording

We frequently encounter teams wanting to transfer Hotjar from web to mobile. Hotjar is historically a web analytics tool, and mobile support came later. It works differently: no DOM, no cursor, tap coordinates must be normalized to each device's screen resolution. Before starting integration, it's important to understand what you need: Hotjar for mobile provides heatmaps and session recordings, but for deep mobile analytics (Screen Flows, Gesture Heatmaps, Rage Taps), UXCam or Smartlook are more mature solutions. However, if your team already uses Hotjar on the web and wants a single tool for web + mobile, integration makes sense. Our team has 5+ years of mobile development experience and has successfully integrated Hotjar in over 20 projects. Below is our approach.

Current State of Hotjar Mobile

Hotjar Mobile SDK (currently beta / limited access) supports:

• Session recording (screenshot-based)
• Per-screen heatmaps
• Rage tap detection (repeated taps on non-interactive areas)
• NPS and survey widgets

React Native and Flutter integrations use JavaScript bridge or community SDKs. Native iOS and Android use official SDKs.

Native SDK vs WebView Comparison

According to Hotjar documentation, the native SDK is recommended for the most accurate heatmaps. Hotjar integrates 2-3 times faster than alternatives like UXCam, though it lacks gesture-level detail.

How to Integrate Hotjar in React Native

If you use React Native, the unofficial package @hotjar/react-native-sdk provides ready hooks and components.

// React Native — @hotjar/react-native-sdk (unofficial)
import { Hotjar } from '@hotjar/react-native-sdk';

// Initialization
Hotjar.init('YOUR_SITE_ID', 6);

// Tag screen for heatmaps
Hotjar.stateChange('ProductDetail');

// Custom user attributes
Hotjar.identify('user_123', {
    plan: 'premium',
    country: 'RU'
});

Hotjar.stateChange() is key for mobile heatmaps: without it, all taps would aggregate into a single "whole app" heatmap. This is a common beginner mistake we always fix upfront.

What Are Rage Taps and Why They Matter

Rage taps — a series of fast taps in one spot. Usually indicate a non-responsive element or a button that doesn't respond quickly enough. Hotjar highlights them in red. According to Hotjar statistics, up to 30% of all sessions contain at least one rage tap. Dead zones — screen areas with no taps. If a CTA button lies in a dead zone, it's either not seen or not recognized as interactive. In a typical app, 20% of the screen gets ignored. Scroll depth shows how far users scroll. If 80% leave before scrolling, content "below the fold" isn't working.

How to Configure Data Masking in Hotjar

Hotjar records keyboard input in session recordings by default. You must explicitly enable suppress mode for sensitive fields:

// Suppress keyboard input recording globally
Hotjar.init('YOUR_SITE_ID', 6, {
    debug: false,
    suppress: true  // don't record keyboard input
});

// Or for a single session
Hotjar.suppress(true);

To mask individual components, use HotjarMask:

// React Native — mask a component
import { HotjarMask } from '@hotjar/react-native-sdk';

<HotjarMask>
    <TextInput
        placeholder="Card number"
        value={cardNumber}
        onChangeText={setCardNumber}
    />
</HotjarMask>

Scope of Work

Includes: integration documentation, analytics access, heatmap interpretation consultation.

Timelines and Cost

Basic integration takes 4–8 hours. Full setup with masking and NPS takes 1–2 days. Cost depends on app complexity and number of screens. Contact us for a free project estimate. With over 20 integrations completed, we ensure accurate configuration without data loss. Order Hotjar integration and get precise analytics in as little as two days.

Mobile App Analytics: Firebase, Amplitude, AppsFlyer and Attribution

Our team regularly encounters projects where analytics is already "set up" but yields no real insights. A typical example is a startup with 50k DAU: tracking dozens of events without a single answer to the question "why don't users reach payment?". In two weeks we built a basic funnel and found that 70% of users drop off at the phone number verification screen. After fixing the bug, retention increased by 12%. The takeaway: analytics should start with specific questions, not tracking everything indiscriminately.

Why Event Taxonomy is the Foundation of Mobile App Analytics?

Firebase Analytics, Amplitude, Mixpanel — technically similar. The difference lies in what you put into them. A common mistake: events like screen_view, button_tap_1, button_tap_2 without context. A month later, no one remembers what button_tap_2 means.

Proper taxonomy: object + action + context. product_viewed, checkout_started, payment_completed with parameters product_id, category, price, source. This allows building funnels, cohort analysis, and retention without additional tracking.

We document the naming convention in a tracking plan — a document (Google Sheet or Amplitude Data Catalog) describing every event, its parameters, and triggering conditions. The tracking plan is synced with the analytics team before development begins, not after. This approach ensures that data remains interpretable months later and doesn't become a dump. Experience from 50+ projects confirms: without a tracking plan, analytics maintenance costs increase 2-3 times due to rework.

What Should You Choose for Mobile App Analytics: Firebase, Amplitude, or Mixpanel?

The table below highlights key differences between the three popular platforms. Choice depends on budget, traffic, and tasks.

Firebase Analytics — free, deep integration with Google Ads, BigQuery export for raw data. Limitations: data latency up to 24 hours, limited funnels. For startups with Google Ads traffic, it's the first choice.

Amplitude — product analytics focused on cohorts and user journeys. Journeys (formerly Pathfinder) shows actual paths between events — not assumed funnels but real routes. Session Replay records sessions for UX analysis. The free tier up to 10M events/month is enough for most products at launch.

Mixpanel — close to Amplitude, stronger in real-time segmentation. Insights, Funnels, Retention cover 90% of product analysts' tasks.

How to Solve Multi-Channel Attribution with AppsFlyer?

Knowing where a user came from is a separate task. Firebase Attribution works only within the Google ecosystem. For multi-channel attribution (Facebook Ads, TikTok, Apple Search Ads, programmatic), an MMP (Mobile Measurement Partner) is needed.

AppsFlyer is the market leader. OneLink — universal deep link working on iOS and Android, correctly attributing installs from any channel. Protect360 — built-in fraud protection (fake installs, click injection on Android). Adjust and Branch are competitors with similar features. Branch excels in deep linking; Adjust is popular in gaming.

According to Apple, with iOS 14.5, apps must obtain user permission via ATT before collecting IDFA for tracking. AppsFlyer uses probabilistic matching (IP + user agent + timing) for these users — accuracy is lower but better than nothing. SKAdNetwork and Privacy Preserving Attribution provide aggregated data from Apple with a 24-72 hour delay.

How to Set Up Crash Analytics to Not Miss Bugs?

Firebase Crashlytics is the standard for crash reporting. It automatically groups crashes by stack trace, shows affected users %, and sends velocity alerts when crash rate increases by more than 10% per hour.

Important: symbolication. On iOS, .dSYM files must be automatically uploaded with each build — via Fastlane upload_symbols_to_crashlytics or Xcode Cloud built-in. Without symbols, crashes in Crashlytics appear as memory addresses. This happens more often than expected when switching to a new CI — in one project with 500k users, we found that 40% of crashes remained unsymbolicated due to a missing CI/CD step. After automation, bug response time dropped from 3 hours to 15 minutes.

For React Native and Flutter, @sentry/react-native and sentry_flutter provide additional context: breadcrumbs, network requests before the crash, Redux/Provider state.

Below is a comparison of popular crash analytics tools to choose according to your needs.

Environment Setup

Three environments with separate Firebase projects: dev, staging, production. Mixing analytics from test sessions and production is a common mistake that skews all metrics. On iOS via GoogleService-Info.plist per scheme, on Android via google-services.json in each flavor folder.

Timelines: basic analytics with Firebase + Crashlytics — 3-5 days. Full tracking plan + Amplitude/Mixpanel with funnels and cohorts — 2-3 weeks. Attribution via AppsFlyer with deep linking and fraud protection — 1-2 weeks. Cost is calculated individually based on integration complexity.

What Is Included in Our Work

As part of analytics implementation, we provide:

• Development and approval of a tracking plan with product and marketing teams.
• SDK integration (Firebase, Amplitude, Mixpanel, AppsFlyer) considering your stack (Swift/Kotlin/Flutter/React Native).
• Setup of funnels, cohorts, dashboards, and alerts.
• Automation of symbolication and .dSYM upload via Fastlane.
• Documentation of events and parameters.
• Team training on the analytics platform.
• Two weeks of post-release support and tracking adjustments.

Our experience: 7 years of analytics implementation and over 80 successful projects in mobile development. We guarantee data correctness and transparency at every stage.

Contact us for a consultation on setting up analytics for your app. Request an audit of your current analytics — and we will show you which metrics you are losing.