Heatmaps & recordings

When you record a session or sample a heatmap Extellio may record user-sensitive data with is displayed on your website. To avoid recording personal data you can mask elements from being recorded by adding the data-matomo-mask attribute around the element in the website’s code. You can mask individual elements like this:  <span data-matomo-mask>Firstname lastname</span> or you can mask a set of elements <div data-matomo-mask><p> <span>Firstname</span><span>Lastname</span> </p

If the web page has elements set to a 100% of the browser height or uses parallax scrolling, the heatmap might display incorrectly. The header may appear stretched across the entire heatmap, obscuring other parts of the web page. To fix it,  you can set a maximum height on the element using CSS or JavaScript. For instance: .hero{ max-height: 1000px; } If you want to set this style only for heatmaps, you can prefix the selector with "html.matomoHeatmap":  html.matomoHeatmap

Sometimes you might want to force the screenshot on a heatmap to make sure it's correct, or you might want to check the configuration on your session recording. If your sample rate isn't 100% there is a risk your activities won't be recorded.To ensure your activities are included in the sample group you can append a URL parameter?pk_hsr_forcesample=1 to the page you're visiting. The page still needs to follow the target rules you configured in your heatmap or session recordi

After you have created a new heatmap, it will automatically start to collect samples, but in order to view it, you also need to take a screenshot. Note that the samples are not dependent on the screenshot, and all samples collected before the screenshot was taken will still be usable.  If your heatmap is missing a screenshot, you will be asked to add one when you click to view the heatmap. To take the screenshot, enter the URL for the heatmap and click on "Open page". The URL

When a heatmap or session sample is recorded, Extellio saves the webpage's CSS to display the page correctly, even if the CSS or URLs to the CSS change.  If Extellio can't read the CSS from the DOM, it tries to fetch the content via an HTTP request. While this works most of the time, in certain situations, like when you load your CSS from a CDN, you need to take extra steps to ensure it works.  Recommended: To avoid Extellio having to make an additonal HTTP request to fetch

Does your target rules match a URL?  Check there isn't any spelling mistakes in the target page rules. Is the target rules logic? Make sure that the target page rules are logical and correctly configured to track the intended page.  When using URL and equals exactly or equals simple make sure you're using the full URL with https:// .  This will not collect any samples because there is no URL equaling exactly www.example.com/ Meanwhile, this will collect samples from https://w