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.
Interested in other ways to filter your Continuous Heatmaps?
To explore additional filters that can be applied, after you've generated a Continuous Heatmap, check out What are Continuous Heatmaps filters?
You can view Continuous Heatmap data for a single page or a group of pages. When viewing a Heatmap for a group of pages, you’ll only see one screenshot, but the data that appears over the screenshot will be aggregated from all matching pages.
There are five URL filtering options that you can choose from:
- Single page: This is the default match type and is used to target a specific page on your site, ignoring any query strings and fragments that might get added, as well as ignoring the protocol, HTTP vs HTTPS, and the presence or not of 'www'.
- Exact match: Displays data from users who visited a specific URL, including the protocol and any query strings and fragments.
- All pages containing: Displays data for all URLs which contain the entered text. This rule is case sensitive.
- All pages starting with: Displays “Exact match” results for all URLs that begin with the entered text, including the protocol.
- All pages ending with: Displays “Exact match” results for all URLs that end with the entered text, including strings and fragments.
Regular expressions (Regex) are not currently supported as a URL filtering option.
It is not currently possible to use regex as one of the URL filtering options.
Single page
This is the default match type that allows you to view a Continuous Heatmap for a specific page on your site. The match will be correct if the URL path that users land on matches the URL path you specify.
If query strings or fragments are added to the URL when the page loads, the Single page match type will still be tracked. Any added query strings or fragments will be ignored.
Single page - http://www.x.com/pages/
| Result | Example URL | Why? |
| MATCH | http://www.x.com/pages/ | The domain (x.com) and page path (/pages) is a match |
| NO MATCH | http://www.x.com/pages/subpage | /subpage is not part of the page path criteria |
| MATCH | http://www.x.com/pages/?x=1 | The query string (?x=1) is ignored |
| MATCH | http://www.x.com/pages/?x=1&y=1 | The query string (?x=1&y=1) is ignored |
| MATCH | http://www.x.com/PAGES | The single page method is NOT case sensitive |
| MATCH | https://www.x.com/pages/ | The HTTPS protocol is ignored |
| MATCH | http://x.com/pages | The www. prefix to the domain is ignored |
| MATCH | https://x.com/pages/ | The HTTPS and www. prefix to the domain are ignored |
Single page - exact match
The match will be correct if the URL path, query-string, and fragment that users land on match EXACTLY the ones you specify.
Example:
Exact match - http://www.x.com/pages/?x=1
| Result | Example URL | Why? |
| ✔️MATCH | http://www.x.com/pages/?x=1 | All URL components are an exact match |
| ❌NO MATCH | http://www.x.com/pages/subpage | The required query string (?x=1) is missing and the page path should not include /subpage |
| ❌NO MATCH | http://www.x.com/pages/ | The required query string (?x=1) is missing |
| ❌NO MATCH | http://www.x.com/pages/?x=1&y=1 | The URL has a non-matching query string (&y=1) at the end of it |
| ❌NO MATCH | http://www.x.com/pages/?x=1#2 | The URL has a non-matching URL fragment (#2) at the end of it |
| ❌NO MATCH | https://www.x.com/pages/?x=1 | The URL protocol (HTTPS) needs to be changed to HTTP to become an exact match. |
All pages containing
The match will be correct if the URL that users land on includes the text you specified.
All pages containing - ?x=1
| Result | Example URL |
| ✔️MATCH | http://www.x.com/pages/?x=1#2 |
| ✔️MATCH | http://www.x.com/pages/?x=1&y=1 |
| ✔️MATCH | http://www.x.com/pages/?x=1 |
| ❌NO MATCH | http://www.x.com/pages/subpage |
| ❌NO MATCH | http://www.x.com/pages/ |
All pages starting with
The match will be correct if the URL that users land on starts exactly as you specify it, including the protocol.
All pages starting with - http://www.x.com/pages/
| Result | Example URL |
| ✔️MATCH | http://www.x.com/pages/ |
| ✔️MATCH | http://www.x.com/pages/subpage |
| ✔️MATCH | http://www.x.com/pages/?x=1 |
| ✔️MATCH | http://www.x.com/pages/?x=1&y=1 |
| ✔️MATCH | http://www.x.com/pages/?x=1#2 |
| ❌NO MATCH | https://www.x.com/pages/ |
All pages ending with
The match will be correct if the URL that users land on ends exactly as you specify it.
All pages ending with - pages/
| Result | Example URL |
| ✔️MATCH | http://www.x.com/pages/ |
| ❌NO MATCH | http://www.x.com/pages/subpage |
| ❌NO MATCH | http://www.x.com/pages/?x=1 |
| ❌NO MATCH | http://www.x.com/pages/?x=1&y=1 |
| ❌NO MATCH | http://www.x.com/pages/?x=1#2 |
Hotjar can only support the following characters
a-z, A-Z,0-9, -, ., _, /, and ~. Any other characters need to be percent-encoded.