Filtering for Feedback and Survey responses works differently
Feedback and Survey filtering currently work slightly differently from session filters discussed in this article. See our How to View Your Feedback Responses guide for details on filtering Feedback responses and our article on How to View Your Survey Responses for filtering Survey responses.
Hotjar's tools enable you to filter collected session data using a set of filters known as session filters. A collection of session filters can also be saved as a Segment for reuse at a later time, and this is currently only available with our Recordings tool. To view a heatmap with pre-determined filters applied, click on the Generate short link button on the bottom right of your heatmap's page. The Generate short link button will copy a short URL for the heatmap that you can revisit in the future with the pre-determined filters applied.
How do session filters work?
Applied filters are combined using "AND" logic and evaluate the filter criteria based on entire user sessions, which is important to keep in mind with Heatmaps. A heatmap will show a single page's screenshot under data from sessions that match the filtered criteria at any point, on any page, during an entire session. For example, applying a rage click filter to a heatmap of your homepage doesn't necessarily mean that the users have rage clicked on the homepage heatmap you're currently viewing. The rage click could have occurred at any moment during their entire session.
What filters are available?
- Path/URL - navigation during a session
- Session - attributes about a session
- Behavior - actions during a session
- User Attributes
- Technology - technology used in a session
- Feedback - response sentiment
- Experiment - Google Optimize experiments
- Date filter
Referrer URL is available on Observe or plans. All other Path/URL filters are available with Observe , or plans.
Path/URL filters focus on where users have or haven't navigated.
For each path/URL filter, you can refine the filter by whether the path "contains", "starts with", "ends with", or "is". You can also filter by sessions where the path "does not contain", "does not start with", "does not end with", or "is not".
- Viewed page
- Referrer URL - not all sessions will have a referrer URL.
- Landing page
- Exit page
Available with Observe , or plans.
Session filters refine your data based on broader details about the session:
- New/Returning - Specifies whether the sessions are filtered by new or returning users.
- Country - The country the session is indicated to originate from.
- Duration - The total session duration in seconds, minutes, or hours. With the options of exactly, less than, greater than, or between.
- Page count - The number of pages visited in a session. With the options of exactly, less than, greater than, or between.
The Event filter is available on Observe , or plans. The Error filter is available on Observe . All other Behavior filters are available with Observe or plans.
These filters include actions performed or experienced by users during their session.
- Clicked element - An element that users have or have not clicked on.
- Event - An action occurred that triggered an event in Hotjar.
- Rage click - Multiple clicks on the same element during a session. Defined as five clicks within 500ms of one another.
- U-turn - Sessions where users directly returned to the previous URL within 7 seconds of leaving that URL.
For all of the above, you can filter by whether the behavior occurred or did not occur.
Available on Observe or plans.
Filtering by User Attributes is only available after setting up the User Attributes feature, and Hotjar has received user attribute data via the Identify API.
- User Attributes - Sessions from specific users based on custom attributes you've passed to Hotjar from your data.
Depending on the attribute data type, you can refine the User Attributes filter by whether the attribute "contains", "starts with", "ends with", or "is". You can also filter by sessions where the attribute "does not contain", "is not", "is unknown", or "has any value".
Available on Observe , or plans.
Refine collected session data based on technology used during a session.
- Hotjar User ID - Sessions relating to a Hotjar User ID, a unique anonymous identifier that Hotjar assigns to all users. Only one ID can be provided, with the options of "is" or "is not" the ID.
- Device - Sessions where the device used was desktop, tablet, and/or mobile. This filter is not shown in the filter dropdown for Heatmaps and instead the device icons available when viewing a heatmap can be used.
- Browser - Sessions using specific browsers, including Chrome, Chromium, Safari, Firefox, Internet Explorer, Edge, Opera.
- Operating system - The operating system in use during a session. This includes Windows, macOS, Linux, Ubuntu, Android, iOS.
Available on Observe or plans.
Filter sessions where a feedback response occurred.
- Feedback - Sessions where a user submitted a Feedback widget response, including Love, Like, Neutral, Dislike, and/or Hate.
- Net Promotor Score® - Sessions where a user submitted an NPS Survey. This is based on their NPS scores and includes Promoters, Passives, and/or Detractors.
Available on Observe or plans.
Filter sessions based on inclusion in an experiment.
- Google Optimize - Sessions where a user was part of a Google Optimize experiment based on the unique ID Google Optimize creates for your experiments.
Available on all plans.
Filter sessions based on relative or custom date ranges.
- Relative date ranges - allow you to see session data from up to 12 months in the past.
- Custom date ranges - useful for comparing session data before and after any changes. View data from a specific period through to 12 months in the past. See our article on How long does Hotjar keep my data for more information about data retention periods.
Net Promoter, Net Promoter System, Net Promoter Score, NPS and the NPS-related emoticons are registered trademarks of Bain & Company, Inc., Fred Reichheld and Satmetrix Systems, Inc.