Help & Information
What is a Cookie?
A cookie is a small text file of letters and numbers that is used to distinguish you from another user and enables swift passage from one page to the next on our website.
Cookies help us to provide you with a better customer experience when you browse to our website and allow us to improve and tailor the site for you. For example, we keep track of the domains from which people visit and we also measure visitor activity on the site, but we do so in ways that keep the information anonymous. We use the information that we collect to measure the number of visitors to the different areas of our website, and to help us make the site more useful to you.
Our website uses four types of cookies. They are as follows:
These enable us to keep track of your movement from one page to another so that you do not get asked for the same information twice. Our shopping basket uses system cookies to remember your selections so that when you proceed to the checkout we know what you have selected rather than your shopping basket being empty.
WebSphere Commerce supports two types of session management: cookie-based and URL rewriting. For a full explanation of what each mean please make reference to the following link Session Management
WebSphere Commerce contains the following session cookies:
|Cookie Name||Cookie Description|
|WC_SESSION_ESTABLISHED||This cookie is created on the first request processed by WebSphere Commerce runtime. For example, a non-cache request. See Dynamic caching considerations for persistent session for more information.|
|WC_ACTIVEPOINTER||This cookie contains the value of the store ID of the session. This value is used to select the store to execute the command, if one is not specified on the URL.|
|This is a user session cookie that flows between the browser and server over both SSL or non-SSL connection. It is used for user identification over non-SSL connections. It contains user session values such as login timeout, session identifier, etc.|
|WC_GENERIC_ACTIVITYDATA||This cookie only exists if it is a generic user (-1002) session. This cookie stores the session values such as storeid, langid, contracts, etc.|
|WebSphere Commerce uses a secure authentication cookie to manage authentication data. An authentication cookie flows only over SSL, and has a time stamped signature for increased security. This cookie is used to authenticate the user over SSL-connections.|
These enable us to recognize and count the number of visitors to the website, and to see how you navigate the site. These cookies help us to improve the way our website works, for example by making sure that users can find what they want quickly and easily.
Google Analytics sets the following cookies as described in the table below. A default configuration and use of Google Analytics sets only the first 4 cookies in the table.
|__utma||This cookie is typically written to the browser upon the first visit to your site from that web browser. If the cookie has been deleted by the browser operator, and the browser subsequently visits your site, a new __utma cookie is written with a different unique ID. This cookie is used to determine unique visitors to your site and it is updated with each page view. Additionally, this cookie is provided with a unique ID that Google Analytics uses to ensure both the validity and accessibility of the cookie as an extra security measure.||2 years from set/update.|
|__utmb||This cookie is used to establish and continue a user session with your site. When a user views a page on your site, the Google Analytics code attempts to update this cookie. If it does not find the cookie, a new one is written and a new session is established. Each time a user visits a different page on your site, this cookie is updated to expire in 30 minutes, thus continuing a single session for as long as user activity continues within 30-minute intervals. This cookie expires when a user pauses on a page on your site for longer than 30 minutes. You can modify the default length of a user session with the _setSessionCookieTimeout() method.||30 minutes from set/update.|
|__utmc||This cookie is no longer used by the ga.js tracking code to determine session status.
Historically, this cookie operated in conjunction with the __utmb cookie to determine whether or not to establish a new session for the user. For backwards compatibility purposes with sites still using the urchin.js tracking code, this cookie will continue to be written and will expire when the user exits the browser. However, if you are debugging your site tracking and you use the ga.js tracking code, you should not interpret the existence of this cookie in relation to a new or expired session.
|__utmz||This cookie stores the type of referral used by the visitor to reach your site, whether via a direct method, a referring link, a website search, or a campaign such as an ad or an email link. It is used to calculate search engine traffic, ad campaigns and page navigation within your own site. The cookie is updated with each page view to your site.||6 months from set/update.|
|__utmv||This cookie is not normally present in a default configuration of the tracking code. The __utmv cookie passes the information provided via the _setVar() method, which you use to create a custom user segment. This string is then passed to the Analytics servers in the GIF request URL via the utmcc parameter. This cookie is only written if you have added the _setVar() method for the tracking code on your website page.||2 years from set/update.|
|__utmx||This cookie is used by Website Optimizer and only set when the Website Optimizer tracking code is installed and correctly configured for your pages. When the optimizer script executes, this cookie stores the variation this visitor is assigned to for each experiment, so the visitor has a consistent experience on your site. See the Website Optimizer Help Center for more information.||2 years from set/update.|
These cookies allow us to track web browsing habits and to tailor advertisements and promotional campaigns to you, for example targeted ads.
Hurra UK & Hurra Ireland
Reference to Hurra Communication Cookies document
Hurra Communications sets different types of Cookies depending on their purpose. In basic setup two types of Cookies are being used:
is set each time a User clicks on a Customer ad in order to measure conversion rate. Its lifetime is specified in the contract, usually it is 30 days. It stores the
source of click, timestamp and internal ID of the clicked advertisement
. The name of the Cookie corresponds to an internal customer-specific ID.
Example: 45=cKcEcH8AAAEAAAZZWDYAAABk: C45G3: 1326233206
|ts lifetime is specified in the contract, usually it is 30 days.|
|Global Hurra Cookie||
Global Hurra Cookie
is set each time a User clicks on an ad or visits a Website that has OWATag installed. It stores a Unique User ID. The lifetime of Global Hurra Cookie is 365 days and its name always starts with __uu.
|The lifetime of Global Hurra Cookie is 365 days|
|Flash Cookie (Localn shared objects)||Flash Cookies (Local Shared Objects) , unlike previously described (Text-/HTML-Cookies) Flash cookies are not managed by the web browser, but an Adobe Flash Player plugin. They offer advanced capabilities, such as storing and reading information independent from the browser. Flash Cookie stores both the Customer Cookie and the Global Hurra Cookie.||Not available|
|Additional Cookie for Flash Tracking||Additional Cookie for Flash Tracking, these Cookies support the work of Flash Cookie.
|6 months from set/update.|
To disable cookies your website browser settings needs to be set to reject cookies; this depends on the browser being used. We have provided guidance on how to do this for popular browsers:-
- Choose the menu "tools" then "Internet Options"
- Click on the "privacy" tab
- Select the setting the appropriate setting
For Mozilla firefox:
- Choose the menu "tools" then "Options"
- Click on the icon "privacy"
- Find the menu "cookie" and select the relevant options
For Opera 6.0 and further:
- Choose the menu Files?> "Preferences"
For further assistance please refer to help pages within your browser.
Visit our corporate website at www.jdplc.com Copyright © 2017 .