Filtering for Survey responses works differently
Survey filtering currently works slightly differently from session filters discussed in this article. See our article on Understanding Your Survey Responses and Results for filtering Survey responses.
Hotjar's tools enable you to filter collected session data using a set of filters known as session filters. Some tools let you save session filters in different ways:
- Recordings: A collection of session filters can be saved as a Segment for reuse at a later time.
- Heatmaps: Click the Save button to quickly revisit a heatmap with previously applied filters.
- Trends/Funnels: Click the Add to dashboard button to save the chart with any applied filters to your dashboard.
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.
What filters are available?
Path/URL
Traffic channel available with Observe 
or Observe 
. All other path/URL filters available on Observe 
, Observe , or Observe
Path/URL filters focus on where users have or haven't navigated.
Path/URL filters have additional matching options
You can refine each path/URL filter by whether it "contains/does not contain", "starts with/does not start with", "ends with/does not end with", "is/is not", "is exactly/is not exactly" or "matches regex/does not match regex".
For more detail on filter conditions, visit our How to Use Conditions in URL Filtering article.
- Viewed page
- Landing page
- Exit page
- Traffic channel - You can filter your sessions by Referrer URL and UTMs.
Session
Traffic channel available with Observe or Observe . All other path/URL filters available on Observe , Observe , or Observe
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.
Behavior
Error filter and Entered text filter available with Observe . Event filter available with Observe , Observe , or Observe . All other filters available with Observe , or Observe
These filters include actions performed or experienced by users during their session.
- Clicked element - An element that users have or have not clicked on.
- Entered text - Sessions where users entered or changed the text in an input field (e.g. a registration form).
- Error - A JavaScript console error occurred (not available with the Surveys).
- Event - An action occurred that triggered an event in Hotjar.
- Rage click - Multiple clicks on the same element during a session. Defined as six clicks within 600ms of one another.
- Refreshed page - Sessions where users refreshed a page.
- U-turn - Sessions where users directly returned to the previous URL within 7 seconds of leaving that URL.
Filtering by URL or CSS selector
You can use the following conditions to further refine your behavior filters (Clicked Element, Entered text, Rage click, U-turn):
-
Page URL: filters sessions where the action happened on a given page.
- See our How to Use Conditions in URL Filtering article for help using URLs as the filter condition, including using regex.
-
CSS selector: filters sessions where the action happened within a given selector.
- CSS selectors define which elements on a page will receive a specific set of CSS rules (or styles). For example, the CSS selector .button will match any element on a page that has a class attribute of button.
User attributes
Available on Observe or Observe plan.
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".
Technology
Available with 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 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 focused on the device type (desktop, tablet, and/or mobile).
- Screen resolution - Sessions focused on specific device pixel width or height.
- Browser - Sessions with specific browser parameters. You can filter by Browser name, version, or language.
- Operating system - The operating system in use during a session. You can filter by Operating system name or version.
Surveys
Available on Observe or plans.
Filter sessions where a Survey response occurred.
- Reaction - Sessions where a user submitted a reaction 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.
Experiment
Available on Observe or plans.
Filter sessions based on inclusion in an experiment.
- Unbounce - filter session data by Unbounce page and variant. This doesn't include Surveys.
- AB Tasty - filter sessions by AB Tasty campaigns.
Date filter
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.