Cookies on data.jisc.ac.uk
To help improve this site we place small files, known as cookies, onto your computer. Some are essential for the site to work properly, others are to improve the experience you have.You can stop this site using non-essential cookies by updating your settings above.
Please note, if you have used the site in the past these cookies may still be on your computer - but by disabling them in your settings we will no longer access them.
How we use cookies
We use cookies for several purposes on this website – we’ve listed each of them below with more details about why we use them and how long they’ll last.
Cookies to improve your experience
Understanding our users' needs
We use Hotjar to better understand our users’ needs and optimise the experience of this website. It helps us understand users’ experiences (eg how much time they spend on which pages, which links they choose to click, what users do and don’t like, etc), which enables us to build and maintain our service with user feedback.
Hotjar uses cookies and other technologies to collect data on our users’ behaviour and their devices. This includes:
- A device's IP address (processed during your session and stored in a de-identified form)
- Device screen size
- Device type (unique device identifiers)
- Browser information
- Geographic location (country only)
- Preferred language used to display our website
Hotjar stores this information on our behalf in a pseudonymised user profile and are contractually forbidden to sell any data collected on our behalf.
The following cookies are set by Hotjar:
hjActiveViewportIds - This cookie stores user active viewports IDs. It stores an expirationTimestamp that is used to validate active viewports on script initialization. It expires when you close the browser.
_hjClosedSurveyInvites - This sets when a user interacts with a Link Survey invitation modal. It ensures the same invite does not reappear if it has already been shown. It expires after 1 year.
_hjCookieTest - This checks to see if the Hotjar tracking code can use cookies. If it can, a value of 1 is set. It is deleted almost immediately after it is created. It expires immediately after the test completes, typically under 100ms.
_hjDonePolls - This is used to make sure the same survey does not reappear if you've already filled it in. It expires after 1 year.
_hjMinimizedPolls - This is used when you minimise a survey widget - it makes sure that this stays minimised as you navigate through the website. It expires after 1 year.
_hjSession_<session id> - This holds current session data and ensures subsequent requests in the session window are attributed to the same session. It expires 30 minutes after the last user activity.
_hjSessionStorageTest - This checks if the Hotjar tracking code can use session storage. If it can, a value of 1 is set. The data stored in _hjSessionStorageTest has no expiration time, but it is deleted almost immediately after it is created. It expires immediately after the test completes, typically under 100ms.
_hjSessionUser_<user id> - This sets when a user first lands on a page. It ensures data from subsequent visits to the same site are attributed to the same user ID. It expires after 1 year.
_hjTLDTest - When the Hotjar script executes, it tries to determine the most generic cookie path to use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, Hotjar tries to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed. It expires when the browser session ends.
_hjHasCachedUserAttributes - This stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. Collected attributes will only be saved to Hotjar servers if the user interacts with a Hotjar Feedback tool, but the cookie will be used regardless of whether a Feedback tool is present. It expires when the browser session ends.
_hjLocalStorageTest - This is used to check if the Hotjar Tracking Script can use local storage. If it can, a value of 1 is set in this cookie and is deleted almost immediately after it is created. It expires immediately after the test completes, typically under 100ms.
_hjViewportId - This stores information about the user viewport such as size and dimensions. It expires when the browser session ends.
_hjUserAttributes - This stores user attributes sent through the Hotjar Identify API. It does not expire.
_hjUserAttributesHash - Lets us know when any user attribute has changed and needs to be updated. It lasts for 2 minutes, extended by user activity.