This website uses Google Analytics and to collect anonymous information such as the number of visitors to the site, and the most popular pages. We use HotJar to collect surveys and user behaviour. We also use Clarity to provide insights into user behaviour through anonymous session recordings and heatmaps.
Keeping these cookies enabled helps us to improve our website.
Please enable Strictly Necessary Cookies first so that we can save your preferences!
Show details
| Name |
Provider |
Why do we use this? |
Expiry |
|
_ga
|
Google Analytics
|
These help us count how many people visit digitalculturenetwork.org.uk by tracking if you’ve visited before
|
2 years
|
|
_gid
|
Google Analytics
|
These help us count how many people visit digitalculturenetwork.org.uk by tracking if you’ve visited before
|
24 hours
|
|
_hjid
|
HotJar
|
Hotjar cookie that is set when the customer first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.
|
365 days
|
|
_hjDonePolls
|
HotJar
|
Hotjar cookie that is set once a visitor completes a survey using the On-site Survey widget. It is used to ensure that the same survey does not reappear if it has already been filled in.
|
365 days
|
|
_hjMinimizedPolls
|
HotJar
|
Hotjar cookie that is set once a visitor minimizes an On-site Survey widget. It is used to ensure that the widget stays minimized when the visitor navigates through your site.
|
365 days
|
|
_hjRecordingLastActivity
|
HotJar
|
This should be found in Session storage (as opposed to cookies). This gets updated when a visitor recording starts and when data is sent through the WebSocket (the visitor performs an action that Hotjar records).
|
Session
|
|
_hjTLDTest
|
HotJar
|
When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed.
|
Session
|
|
_hjUserAttributesHash
|
HotJar
|
User Attributes sent through the Hotjar Identify API are cached for the duration of the session in order to know when an attribute has changed and needs to be updated.
|
Session
|
|
_hjCachedUserAttributes
|
HotJar
|
This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. These attributes will only be saved if the user interacts with a Hotjar Feedback tool.
|
Session
|
|
_hjLocalStorageTest
|
HotJar
|
This cookie 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. The data stored in_hjLocalStorageTest has no expiration time, but it is deleted almost immediately after it is created.
|
Under 100 ms
|
|
_hjIncludedInPageviewSample
|
HotJar
|
This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's pageview limit.
|
30 minutes
|
|
_hjIncludedInSessionSample
|
HotJar
|
This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's daily session limit.
|
30 minutes
|
|
_hjAbsoluteSessionInProgress
|
HotJar
|
This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie.
|
30 minutes
|
|
_clck
|
Clarity
|
|
1 year
|
