Name	fe_typo_user
Provider	TYPO3
Period of validity	7 days
Purpose	This cookie is a standard session cookie of TYPO3. It stores the session ID in case of a user login. This allows the logged-in user to be recognized, and access to protected areas is granted.

Name	cookie_optin
Provider	TYPO3
Period of validity	1 year
Purpose	Contains your selected tracking settings of the Cookie-Content tool used.

Name	_gat
Provider	Google Analytics
Period of validity	1 minute
Purpose	This is a pattern type cookie specified by Google Analytics, where the pattern element on the name contains the unique identity number of the account or website to which it refers. This is a variant of the _gat cookie, which limits the amount of data recorded by Google on websites with high traffic volumes.

Name	_ga
Provider	Google Analytics
Period of validity	2 years
Purpose	This cookie is installed by Google Analytics and is used to calculate visitor, session, and campaign data and to track website usage for the website analysis report. It stores information anonymously and assigns a randomly generated number to identify unique visitors.

Name	_gid
Provider	Google Analytics
Period of validity	1 day
Purpose	This cookie is installed by Google Analytics. It is used to store information about how visitors use a website and helps to produce an analytical report about how the website is doing. The data collected includes the number of visitors, the source from which they came and the pages in anonymized form.

Name	_hjid
Provider	Hotjar
Period of validity	1 year
Purpose	Hotjar cookie. This cookie 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.

Name	_hjIncludedInSample
Provider	Hotjar
Period of validity	1 year
Purpose	Hotjar cookie. This session cookie is set to let Hotjar know whether that visitor is included in the sample which is used to generate funnels.

Name	_hjAbsoluteSessionInProgress
Provider	Hotjar
Period of validity	30 minutes
Purpose	The cookie is set so Hotjar can track the beginning of the user's journey for a total session count. It does not contain any identifiable information.

Name	_hjClosedSurveyInvites
Provider	Hotjar
Period of validity	1 year
Purpose	Hotjar cookie. This cookie is set once a visitor interacts with a survey invitation modal popup. It is used to ensure that the same invite does not re-appear if it has already been shown.

Name	_hjDonePolls
Provider	Hotjar
Period of validity	1 year
Purpose	Hotjar cookie. This cookie is set once a visitor completes a poll using the Feedback Poll widget. It is used to ensure that the same poll does not re-appear if it has already been filled in.

Name	_hjMinimizedPolls
Provider	Hotjar
Period of validity	1 year
Purpose	Hotjar cookie. This cookie is set once a visitor minimizes a Feedback Poll widget. It is used to ensure that the widget stays minimized while the visitor navigates through the site.

Name	_hjDoneTestersWidgets
Provider	Hotjar
Period of validity	1 year
Purpose	Hotjar cookie. This cookie is set once a visitor submits their information in the Recruit User Testers widget. It is used to ensure that the same form does not re-appear if it has already been filled in.

Name	_hjShownFeedbackMessage
Provider	Hotjar
Period of validity	1 year
Purpose	This cookie is set when a visitor minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if they navigate to another page where it is set to show.

Name	_hjRecordingLastActivity
Provider	Hotjar
Period of validity	End of the session
Purpose	This should be found in sessionStorage (as opposed to cookies). It is updated when a visitor recording starts and when data is sent through the WebSocket (the visitor performs an action that Hotjar records).

Name	hjTLDTest
Provider	Hotjar
Period of validity	End of the session
Purpose	When the Hotjar script is executed, we try 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, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed.

Name	_hjUserAttributesHash
Provider	Hotjar
Period of validity	End of the session
Purpose	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.

Name	_hjCachedUserAttributes
Provider	Hotjar
Period of validity	End of the session
Purpose	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.

Name	_hjLocalStorageTest
Provider	Hotjar
Period of validity	N/A
Purpose	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 immediately after creating it so the expected storage time is under 100 ms.

Name	_hjptid
Provider	Hotjar
Period of validity	End of the session
Purpose	This cookie is set for logged in users of Hotjar, who have Admin Team Member permissions. It is used during pricing experiments to show the Admin consistent pricing across the site.

External content
We use external content on our website to offer you additional information. You need to allow the cookie category "External content" to be displayed.

Publication

Last searches

Using Multi-Factor Authentication (MFA) to Sign In to the Server

Dialog: Automation Server – Sign In

Committing a Project and Boot Application to the CODESYS Automation Server and to a PLC