List of cookies at elmia.se

Google Analytics
 _ga:
This cookie is used to distinguish unique users by assigning a randomly generated number as a client identifier. It is included in each page request in a site and used to calculate visitor, session and campaign data for the sites analytics reports.

_gid:
This cookie is used to distinguish users. This cookie is responsible for tracking user behavior. It expires after 24 hours of inactivity. The contents of this cookie are also very similar to _ga cookie, and it contains 4 types of information: “GA1”, stands for the cookie version. 

__utma:
This cookie keeps track of the number of times a visitor has been to the site pertaining to the cookie, when their first visit was, and when their last visit occurred. Google Analytics uses the information from this cookie to calculate things like Days and Visits to purchase.

__utmc:
This is one of the four main cookies set by the Google Analytics service which enables website owners to track visitor behaviour and measure site performance. It is not used in most sites but is set to enable interoperability with the older version of Google Analytics code known as Urchin. In this older versions this was used in combination with the __utmb cookie to identify new sessions/visits for returning visitors. When used by Google Analytics this is always a Session cookie which is destroyed when the user closes their browser. Where it is seen as a Persistent cookie it is therefore likely to be a different technology setting the cookie. 

__utmz:
This is one of the four main cookies set by the Google Analytics service which enables website owners to track visitor behaviour measure of site performance. This cookie identifies the source of traffic to the site - so Google Analytics can tell site owners where visitors came from when arriving on the site. The cookie has a life span of 6 months and is updated every time data is sent to Google Analytics.

Google AdSense
_gcl_au:
Used by Google AdSense for experimenting with advertisement efficiency across websites using their services.

Hotjar
_hjIncludedInSample:
This cookie identifies users during a unique session and determines that it participates in the target audience.

_hjid:
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.

_hjAbsoluteSessionInProgress:
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.

Upsales
__upsales_v_45ef11554e6f417ba75c4a2659f04c7d_tracker
This cookie is used to gather information about website statistics, customize the website when a visitor returns, and for marketing purposes.

Facebook
_fbp:
Used by Facebook to deliver a series of advertisement products such as real time bidding from third party advertisers.

EPiServer CMS

.EPiServerLogin, EPiDPCKEY, .ASPXRoles:
These cookies are used to allow login and manage access and permissions when using EPiServer CMS.

.EPiForm_BID:
Used when visitors fill out a form to allow Episerver to keep track of what is being filled in. The cookie is automatically deleted after 90 days.

ASP.NET_SessionId:
This cookie is required to identify requests from the same browser during a limited session time window when browsing the website. This cookie is deleted when you close your browser.

EPiForm_{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx}:{xxxxx}:
This cookie is used when a visitor submits data via an EPiServer form. This cookie stores any partial form submissions so a user can continue with the submission later. The xxxxx refers to a unique identifier.

.EPiForm_VisitorIdentifier:
This cookie is used when a visitor submits data via an EPiServer form. This cookie stores any partial form submissions so a user can continue with the submission later. The xxxxx refers to a unique identifier.

__epiXSRF:
This cookie is used to protect the user against cross-site request forgery (XSRF). It is only used by EPiServer CMS.

__RequestVerificationToken:
This is an anti-forgery cookie set by web applications built using ASP.NET MVC technologies. It is designed to stop unauthorised posting of content to a website, known as Cross-Site Request Forgery.

ImageEditorFileSize:
Used by Episerver's built-in image processing feature.

Other
elmia.acceptedCookies:
Indicates consent for cookies. Indicates whether the visitor has approved cookie info (so that the banner is not displayed every time).

elmia.warningMessage:
Indicates consent not to display Warning Message / Modal window more times. Indicates whether the visitor has accepted the warning message (so that the banner is not displayed every time).

origin_site:

picked_site: