From Friday July 1, 2022 we're moving accounts that were created before April 20, 2022 to our updated pricing model.
Under the updated pricing model, we've grouped Surveys and Feedback into a separate product called Ask that’s priced based on the number of responses you want to collect across Surveys and Feedback. Heatmaps and Recordings will be grouped into a separate product called Observe and will still be priced based on the number of daily sessions.
Both products, Observe and Ask, will have the Basic (free), Plus, Business, and Scale plans available, and the selected plan can be different for each product.
See the Updating our pricing model blog post for all the details on this update.
Heatmaps cannot track user interactions that happen inside iframes within your pages. This is due to potential security problems inherent to how iframes work. If you are unfamiliar with what an iframe is, you can think of it as a web page inside another web page. They are often used to add elements like chatbots, videos, or forms to your pages by third-party service. You can read more about iframes on the Mozilla Developer Network.
This means that any of the following content types embedded as iframes cannot be tracked, and may not show in your Heatmaps:
❌ Chat bots.
❌ Third-party form tools.
❌ Embedded video players.
❌ Third-party payment processors.
❌ Embedded apps or pages you might have created.
Workaround for same-source iframes
If you have the ability to edit the HTML of your iframe element, and your iframe source URL uses the same domain as the page the iframe is being added to, then you can place the Hotjar tracking code inside the iframe source page, instead of the parent page. With this option, you can track the iframe source page but not other aspects of the parent page.
How do iframes appear within a Heatmap?
How an iframe will appear in your Heatmap depends on how the iframe source page is built. If it's a static page, then you can see the iframe appear in your Heatmap (you may need to allow the iframe domain in order to see the static content). You will not see clicks within the iframe elements, but you can see cursor movements, as these can be tracked on the parent page.
What limitations still exist after allowing iframes?
Before allowing an iframe, you should consider some of the limitations that still exist even after allowing the iframe.
We can track:
✔️ a static page delivered through an iframe can be displayed inside a Heatmap.
✔️ mouse over behavior is tracked, relative to the parent page.
We cannot track:
❌ clicks on elements inside an iframe.
❌ scroll events inside an iframe.
❌ if your iframe source domain is different than the parent page domain, Hotjar will not work with your iframe.