Hotjar Recordings Are Missing Form Interactions: What Can Cause It?
When Hotjar recordings are missing form interactions, the recording plays but typing, clicking or selecting inside a form does not appear. The cause is usually dynamic forms, embedded forms, iframes, consent, privacy masking or page behavior. Do not disable privacy protections to see more data, because the masking exists for a reason.
Table of Contents
- 01.Why form interactions can be missing
- 02.What to check first
- 03.Dynamic and embedded forms
- 04.Privacy masking
- 05.Consent and page behavior
- 06.How to test the fix
- 07.How to validate the final result
Why form interactions can be missing
A recording captures the page and the interactions on it. Form interactions can be missing because the form is dynamic, embedded in an iframe, masked for privacy, blocked by consent or loaded in a way Hotjar does not capture. Each cause has a different fix, and some have no fix because the behavior is intentional privacy protection.
| Cause | What happens | How to check |
|---|---|---|
| Dynamic form | Form loads after the recording starts | Check if the form loads dynamically |
| Iframe embed | Form is in a separate frame | Check if the form is in an iframe |
| Privacy masking | Fields are masked for privacy | Check masking settings |
| Consent | Form interactions not eligible | Check consent state |
| Page behavior | Form replaces content dynamically | Check SPA or dynamic behavior |
What to check first
- Confirm the recording captures the page but not the form interactions.
- Check whether the form loads dynamically after the page loads.
- Check whether the form is embedded in an iframe.
- Review the privacy masking settings for form fields.
- Check the consent state for the session.
Dynamic and embedded forms
A form that loads dynamically after the page loads may not be captured in the recording, because the recording started before the form existed. A form embedded in an iframe is a separate document, and Hotjar may not capture interactions inside the iframe depending on the setup. Confirm how the form loads and whether it is in an iframe. These are technical limitations, not configuration errors.
Privacy masking
Hotjar masks sensitive form fields for privacy. A masked field shows no input in the recording, which looks like a missing interaction but is intentional protection. Do not disable masking to see the input, because that exposes sensitive user data. If you need to understand form behavior without the input values, the recording still shows the interaction timing and field focus. Respecting privacy masking is covered in the privacy rule: do not bypass it.
Consent and page behavior
Consent affects which interactions are captured. A session without full consent may not capture form interactions. Page behavior also matters. A single-page application that replaces form content dynamically can confuse the recording. Confirm the consent state and how the page loads the form. Recording capture problems are covered in the guide on Hotjar recordings not showing.
How to test the fix
- 1.Confirm whether the form is dynamic or in an iframe.
- 2.Review the masking settings without disabling privacy protection.
- 3.Check the consent state for the test session.
- 4.Test a form interaction and confirm whether it appears in the recording.
How to validate the final result
Form interactions are captured when the recording shows field focus and interaction timing for unmasked fields. Masked fields correctly show no input. If the form is dynamic or in an iframe and interactions remain missing, that is a technical limitation of the setup, not a fixable configuration error. For analyzing form drop-off, use the guide on Hotjar form drop off alongside the recordings.
Frequently Asked Questions
Why does my Hotjar recording not show form typing?
The field may be privacy-masked, the form may load dynamically or it may be in an iframe. Masked fields correctly show no input. Do not disable masking to see the values. Confirm how the form loads and review the masking settings without bypassing privacy protection.
Should I disable privacy masking to see form interactions?
No. Masking protects sensitive user data. Disabling it exposes personal information in recordings. The recording still shows interaction timing and field focus for masked fields, which is enough to understand form behavior without the input values.
Need help applying this to your business?
PPC, Conversion Tracking, CRM and Automation Specialist. Helping businesses generate qualified leads with Google Ads, accurate tracking and automated follow-up.
Related Guides
Hotjar Recordings Not Showing: Common Tracking and Session Problems
Recordings can be missing even when tracking is installed, because of consent, sampling, page targeting or browser restrictions. Distinguish a tracking problem from a capture problem first.
Hotjar Users Drop Before Submitting the Form: How to Audit the Page
Form drop-off can come from visibility, field length, required fields, errors, mobile usability, trust or page speed. Use recordings and heatmaps to find where visitors leave.
Hotjar Tracking Not Working: What to Check First
When Hotjar tracking does not work, the cause is the tracking code, page coverage, consent, a website change or browser behavior. Confirm the code is present and loading before debugging anything deeper.