A cookie is a small file of letters and numbers that we store on your browser or the hard drive of your computer if you agree. Cookies contain information that is transferred to your computer’s hard drive.
We use the following cookies:
- Strictly necessary cookies. These are cookies that are required for the operation of our website. They include, for example, cookies that enable you to log into secure areas of our website, use a shopping cart or make use of e-billing services.
- Analytical/performance cookies. They allow us to recognise and count the number of visitors and to see how visitors move around our website when they are using it. This helps us to improve the way our website works, for example, by ensuring that users are finding what they are looking for easily.
- Functionality cookies. These are used to recognise you when you return to our website. This enables us to personalise our content for you, greet you by name and remember your preferences (for example, your choice of language or region).
- Targeting cookies. These cookies record your visit to our website, the pages you have visited and the links you have followed. We will use this information to make our website and the advertising displayed on it more relevant to your interests. We may also share this information with third parties for this purpose.You can find more information about the individual cookies we use and the purposes for which we use them in the table below:
|_jsuid||This is a random number that is generated by the Code the first time someone visits a web site with the Code installed. Its sole purpose is to better identify new and unique visitors to a web site. This cookie is sent to the Service for every event logged. The value of this cookie will also be set as a third party cookie with the name of “cluid”, if such a cookie does not exist. The purpose of the third party cookie is for web sites with multiple domains and who want to track visitor sessions across multiple domains, which is not possible with first party cookies. These “uid” cookies are set to more or less never expire.|
|_eventqueue||This cookie stores an array of mouse events that can’t be guaranteed to be logged to our servers before the current page is unloaded. The purpose is to store these events in a queue so on the subsequent page view, these events can be processed and logged. This is a session cookie so it will expire when the visitor leaves our web site.|
|_referrer_og||This cookie stores the external referrer for a visitor, so that on future visits the same referrer will be attached to their sessions. This cookie expires after 90 days but will be set again or updated on future visits if they arrive at our site from a link on another site, whether or not it’s the same referrer. When this cookie is updated, the expiration date is reset to 90 days from the time of the new visit. This cookie can be disabled by setting the sticky_data_disable tracking option.|
|_utm_og||This cookie stores dynamic (UTM) campaign variables, so that on future visits the same campaign data will be attached to their sessions. This cookie expires after 90 days but will be set again or updated on future visits if they arrive at our site with campaign data in the URL. When this cookie is updated, the expiration date is reset to 90 days from the time of the new visit. This cookie can be disabled by setting the sticky_data_disable tracking option.|
|_first_pageview||This cookie is set on the first page view of a session. It is used to make our tracking code more efficient, so certain processes are only run on a visitor’s initial page view. It expires after 10 minutes.|
|heatmaps_g2g_[site_id]||This cookie tells our tracking code whether or not to log data about where a visitor is clicking on a site to send back to our servers and use that data to generate a heatmap report of clicks on that page. If you disable cookies, heatmap data cannot be logged. This is a session cookie so it will expire when the visitor leaves our web site.|
|unpoco_[site_id]||The Code sends “pings” when a visitor sits on a single page. This allows the Service to more accurately track “time on site” values. Because this feature uses a lot of extra bandwidth, it requires a paid account. For non-paid accounts, this cookie is set to tell the Code not to send these pings. This cookie expires after 1 hour but will be set again upon future visits by the same visitor.|
|no_tracky_[site_id]||When a site stops using the Service, it is quite common for the web master to leave the code installed, which is against the Terms of service. For high traffic sites, this can use a lot of extra bandwidth and CPU resources on our servers. This cookie is set whenever data is sent in for a site that is disabled. It tells our tracking code to stop sending data to us. This cookie expires after 1 hour but will be set again upon future visits by the same visitor, until the Code is removed from the offending web site.|
You block cookies by activating the setting on your browser that allows you to refuse the setting of all or some cookies. However, if you use your browser settings to block all cookies (including essential cookies) you may not be able to access all or parts of our site.