Third party cookie used to track user engagement by giving visitors a random unique identifier. Used to calculate visitor, session and campaign data for reports and to monitor website performance. For more information, please see the Google Analytics website.
Stores the name of the campaign assigned to the visitor.
Used to track conversions for the test and maintain consistent page content for the visitor. Stores the name of the page variant assigned to the visitor, the list of performed conversions and information on whether visitor is included in A/B testing specified by an A/B test for 2 months.
Indicates that the landing page has already been visited so the landing page activity is not logged again for the current visitor. Expires after 20 minutes but renewed on each visit.
Stores the combination of variants assigned to the visitor by a variant test. Used to track conversions for the test and maintain consistent page content for the visitor. Data is kept for 1 month.
Stores the visitor's preferred content culture for 1 year.
Stores a reference to the user's active shopping cart for 1 year.
Stores the global unique identifier of the contact related to the current site visitor. Used to track activities on the website.
Hotjar cookie that is set when the customer first lands on a page with the HotJarscript. It is used to persist the HotJar user IS, unique to this site on the browser. Data is kept for 365 days.
Hotjar cookie that records a visitor’s last action on the website. Data is kept for the browsing session.
Hotjar cookie. When the Hotjar script executes Hotjar 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 trie to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed. Data is kept for the browsing session.
Hotjar cookie that stores user attributes sent through the Hotjar Identify API and are cached for the duration of the session in order to know when an attribute has changed and needs to be updated. Cookie is stored for the browsing session.
Hotjar cookie that 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. Cookie is stored for the browsing session.
Hotjar cookie 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.
Hotjar cookie set to let Hotjar know whether that visitor is included in the data sampling defined by the site's pageview limit. Cookie is stored for 30 minutes.
Hotjar cookie that is set to let Hotjar know whether that visitor is included in the data sampling defined by the site's daily session limit. Cookie is stored for 30 minutes.
Hotjar cookie used to detect the first pageview session of a user. This is a True/False flag set by the cookie. Cookie is stored for 30 Minutes.
LinkedIn cookies (lang; lidc; li_gc; bcookie; AnalyticsSyncHistory; UserMatchHistory)
The LinkedIn Insight Tag enables the collection of metadata such as IP address information, timestamp, and events such as page views. All data is encrypted. The LinkedIn browser cookie is stored in a visitor's browser until they delete the cookie or the cookie expires (there’s a rolling six-month expiration from the last time the visitor’s browser loaded the Insight Tag).
The LinkedIn insight cookies are stored from a per-session basis - a maximum of 2 years.
Meta Pixel cookies
The meta pixel will collect metadata such as HTTP headers, a standard web protocol sent between any browser request and any server on the internet. This information may include data like IP addresses, information about the web browser, page location, document, referrer and person using the website; Pixel-specific Data such as Pixel ID and the Facebook Cookie; Button Click Data – Includes any buttons clicked by site visitors, the labels of those buttons and any pages visited as a result of the button clicks; Custom data events such as conversion value and page type.
Stores the channel from which the user arrived at the site (eg email, Facebook, Twitter, etc.).
Stores the URL referrer from which the user arrives on the website for 1 day.
Indicates if the visitor is new or returning. Used for tracking visitor statistics in Web analytics.