Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
The cookie is set by Google Analytics and is deleted when the user closes the browser. It is used to enable interoperability with urchin.js, which is an older version of Google Analytics and is used in conjunction with the __utmb cookie to determine new sessions/visits.
Google Analytics sets this cookie to inhibit request rate.
Google Analytics sets this cookie to store the traffic source or campaign by which the visitor reached the site.
This cookie is installed by Google Universal Analytics to restrain request rate and thus limit the collection of data on high traffic sites.
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.
Set by Google to distinguish users.
Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously.
Hotjar sets this cookie to detect the first pageview session of a user. This is a True/False flag set by the cookie.
Hotjar sets this cookie to identify a new user’s first session. It stores a true/false value, indicating whether it was the first time Hotjar saw this user.
Hotjar sets this cookie to know whether a user is included in the data sampling defined by the site's pageview limit.
Hotjar sets this cookie to know whether a user is included in the data sampling defined by the site's daily session limit.
Hotjar sets this cookie when a user minimizes or completes Incoming Feedback so that the Incoming Feedback loads as soon as it is minimized if the user navigates to another page where it is set to show.
To determine the most generic cookie path that has to be used instead of the page hostname, Hotjar sets the _hjTLDTest cookie to store different URL substring alternatives until it fails.
YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data.