|
Enregistre un identifiant unique qui est utilisé pour générer des données statistiques sur la façon dont le visiteur utilise le site web.
|
2
ans
|
HTML
| |
|
Un cookie de google analytics pour suivre et optimiser le parcours des utilisateurs
|
1
minutes
|
HTML
| |
|
Un cookie de Google Analytics pour distinguer anonymement les utilisateurs d'un site web
|
1
jour
|
HTML
| |
|
Hotjar cookie that is set once a user interacts with an External Link Survey invitation modal. It is used to ensure that the same invite does not reappear if it has already been shown.
|
365
jours
|
HTML
| |
|
Hotjar cookie that is set once a user 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
jours
|
HTML
| |
|
Hotjar cookie that is set once a user minimizes an On-site Survey widget. It is used to ensure that the widget stays minimized when the user navigates through your site.
|
365
jours
|
HTML
| |
|
Hotjar cookie that is set when a user minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if the user navigates to another page where it is set to show.
|
365
jours
|
HTML
| |
|
Causes Hotjar to stop collecting data if a session becomes too large. This is determined automatically by a signal from the WebSocket server if the session size exceeds the limit.
|
session
|
HTML
| |
|
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
jours
|
HTML
| |
|
This should be found in Session storage (as opposed to cookies). This gets updated when a user recording starts and when data is sent through the WebSocket (the user performs an action that Hotjar records).
|
session
|
HTML
| |
|
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
|
HTML
| |
|
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
|
HTML
| |
|
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
|
HTML
| |
|
This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's pageview limit.
|
30
minutes
|
HTML
| |
|
This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's daily session limit.
|
30
minutes
|
HTML
| |
|
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
|
HTML
| |
|
This is set to identify a new user's first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions.
|
session
|
HTML
| |
|
This stores information about the user viewport such as size and dimensions.
|
session
|
HTML
| |
|
This is added when a Recording starts and is read when the recording module is initialized to see if the user is already in a recording in a particular session.
|
session
|
HTML
| |
