What is reduced interactivity mode?
What can cause this?
There are a few main reasons this message might appear. Both of which have solutions that will improve your heatmap experience.
Loading a historical view of your website
Altering your segmentation to include a custom date range while the "load a historical view of this page" option is checked will cause the heatmap tool to load a version of your website from a past recording and you will be placed in this mode.
X-Frame-Options set to DENY
Some websites make use of the
X-Frame-Options header and have it set to
DENY, which prevents the website from ever being loaded with an iframe. Our heatmap tool relies on loading websites within an iframe. However, since the heatmap tool is loaded directly on your website, the X-Frame-Options header can safely be set to
SAMEORIGIN to allow the heatmap to load, but still maintain the same level of security desired by using the X-Frame-Options header.
Will setting SAMEORIGIN invalidate our PCI compliance?
PCI compliance simply requires that the X-Frame-Options header bet set, but does not require it be set to
DENY. You can safely set it to
SAMEORIGIN and maintain your PCI compliance.
Navigating to a page across domains
If you are interacting with your heatmap and navigate to a page on a different domain than your current page, you will experience reduced interactivity. For example, if you are on
mywebsite.com and navigate to your cart which is on
cart.mywebsite.com, the domains no longer match and you be placed in reduced interactivity mode.
You can get around this by returning to your dashboard and loading a heatmap for