Heatmaps (Premium Feature)
Heatmaps allow you to record clicks, mouse movements, and scrolling activities of your visitors on your website. site. Heatmaps help you find out where users think something is clickable but isn't, whether there are parts of the page that are rarely viewed or interacted with, what your visitors are actually looking for, how much of the page is visible when users users view your page and much more. Heatmaps allow you to optimize your website and maximize its success.
What does the Heat Map do?
It tracks visitor interactions on the website such as clicks, mouse movements, scrolls, form interactions, and page changes. These interactions can later be played back in a video or viewed in a heatmap so you can find out what your visitors are actually looking for, where they think something is clickable but isn't, how far down the page they've looked, and more.
It's an important tool for you to see visitors' movements on your website.
Create and Manage Heat Maps
Before your users' mouse movements are recorded and your page heatmaps are generated, you need to create a heatmap.
To access the Manage heatmapsr screen, click on the report or on the Administration >> Sites >> Heatmaps menu. No developer knowledge is required to configure any of the heatmaps and you don't need to tweak the code on your website. When you manage your heatmaps, the user interface always explains in detail what each step is about and literally It will only take a few seconds to track your users' interactions and generate heatmaps.
To create a heatmap, click Create New Heatmap in the bottom left corner. To edit a heatmap, simply click the edit icon next to the name of a previously created heatmap.
When creating or editing a heatmap, all you need to do is define a name for the heatmap and choose which landing page to heatmap on. must be generated. To do this, you can choose between attributes and comparisons “URL”, “URL path”, “URL parameter” such as “equals”, “starts with”, “contains”, “matches regular expression” and more. The validator next to the landing page allows you to easily test whether the page you want matches actually matches the pages you want to generate heatmaps for.
Advanced options
When configuring a heatmap, you can optionally set advanced options such as:
- Choose a screenshot URL;
- Hide heatmap elements;
- Choose a different sampling rate;
- Set breakpoint width for mobile and tablets (useful if your site is responsive).
As always, the meaning of each option is clearly explained in the user interface.
Masking content on your website
When you record a session or generate a heatmap, {{ no such element: mkdocs.config.defaults.MkDocsConfig object['mocule_name'] }} may record sensitive user data that is displayed on your website. To mask the content of an element you can use the
You can mask an individual element this way:
<span data-mvm-mask>Person's name</span>
Alternatively, you can mask a set of elements on your site page by specifying the data-mvm-mask attribute on an element higher in the hierarchy:
<div data-mvm-mask>
<p>
<span>Name</span>
<span>Last name</span>
</p>
</div>
Unmasking keystrokes in form fields
When you record a session, MVMCloud Analytics can record keystrokes made by a visitor in a form field, depending on your session recording setup. By default, no keystrokes are captured. If the resource to record keystrokes is enabled, MVMCloud Analytics will record any text entered into form fields and play it back later in the video recording session, but any text entered will be "masked". This means that any text entered into a masked field will be replaced with asterisks, for example it can be tracked as **.
If you want to record keystrokes for some form fields in plain text, you need to enable keystroke capture. key in the session recording and specifically list in the HTML of your website or application which form fields can be recorded specifying a data-mvm-unmask attribute. There is also a data-mvm-mask attribute to prevent logging of sensitive information.
Please note that some fields, such as passwords, common credit card fields, and some other fields, will always be masked to prevent recording of possible personal or confidential information in plain text.
You can unmask an individual form field like this:
<input type="text" name="example_of_text_that_will_be_recorded" data-mvm-unmask>
Alternatively, you can mask a set of form fields on the site page by specifying the data-mvm-unmask attribute and mask individual elements using the data-mvm-mask attribute like this:
<form data-mvm-unmask>
<div>
<input type="text" name="example_of_text_that_will_be_recorded">
<input type="text" name="example_of_text_that_will_not_be_recorded" data-mvm-mask>
<input type="text" name="example_of_text_that_will_not_be_recorded" data-mvm-mask>
</div>
</form>
To force no keystrokes to be registered even when enabled in the UI,
call _paq.push(['HeatmapSessionRecording::disableCaptureKeystrokes']); in the tracking code embedded in your website.
If disabled, no text entered into any form field will be sent to MVMCloud Analytics, not even masked form fields.
Can I track activities for only a portion of my visitors?
Yes, when you configure a heatmap or session recording, you can set a so-called “sample rate”. You can choose a rate between 0.1% and 100%. If you choose, for example, 10%, only every 10th page view will be recorded.