Cookies

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.

Why do we use Cookies?

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.

Cookie Types

Our website uses four types of cookies. They are as follows:

System Cookies

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.

System cookies we use »

IBM

Cookie Types

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.
WC_USERACTIVITY_ID

For example: WC_USERACTIVITY_-1000

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.
WC_AUTHENTICATION_ID

For example: WC_AUTHENTICATION_-1000

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.

Analytic Cookies

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.

Analytic cookies we use »

Google Analytics

Cookie Types

Reference to http://code.google.com/apis/analytics/docs/concepts/gaConceptsCookies.html

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.

Name Description Expire
__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.

Not set.

__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.

Coremetrics

Cookie Types

Reference to two (2) documents Coremetrics Implementation Guide-1.pdf and Understanding_Coremetrics_Reports.pdf

In order to facilitate tracking of session and visitor activities, Coremetrics makes use of cookies.

Session Cookie:
The 'Session' cookie exists only for the lifetime of the current browser session. The Session cookie will exist from the point at which the first tag is received from the website until 1) the visitor closes all browser windows for the browser in question or 2) more than 30 minutes pass without receiving a data collection tag from the browser session. One or more 'sessions' may be associated with a 'visitor'.
Visitor Cookie:
The 'Visitor' cookie persists after the visitor closes all browser windows. The 'Visitor' cookie contains a cookie ID referenced by Coremetrics to identify a visitor returning to the site across multiple 'sessions'.

Maxymiser

Cookie Types

The cookies that Maxymiser uses are known as "first party cookies" and are classified as "analytical cookies" which allow to recognize and count the number of visitors to see how visitors browse around the site. The website owners can then understand the areas that are not working well and find better ways to serve the customer.

Maxymiser never shares data or observations with anyone outside of the website owner and the data is used at an aggregated level so it does not and is never used to identify the customer. They don't work in the online advertising industry who use 'third party cookies'. They only work on web sites - so for instance they do not generate pop-up adverts or adverts (re) targeting the customer on third party websites.

Further information to support queries can be found:
http://www.maxymiser.com/cookies
http://www.maxymiser.com/company/privacy

Name Description

mmid

This cookie does the same job as mmcore.pd. It is set for backwards compatability with previous mmcore versions.

mmcore.tst

This cookie is used to test if browser accepts cookies or not

mmcore.srv & mmcore.pd

These 2 cookies are used to store anonymous identifiers for the visitor to ensure visitors are served the same content variations each time they return to the site.

mmcore.mmact

This cookie is used for handling delayed actions between two pages

Marketing Cookies

These cookies allow us to track web browsing habits and to tailor advertisements and promotional campaigns to you, for example targeted ads.

Marketing cookies we use »

Hurra UK & Hurra Ireland

Reference to Hurra Communication Cookies document

Cookie Types

Hurra Communications sets different types of Cookies depending on their purpose. In basic setup two types of Cookies are being used:

Name Description Expire

Customer Cookie

Customer Cookie 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

Its 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.

Example: __uu=cKcEcH8AAAEAAAZZWDYAAABk

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.

Example: fr=1014

Example: r=1014_1329918297

Not available

Responsys

Cookie Types

No cookies are implemented on any of the websites.

However a cookie is added to the end-user's machine if they click on an email which links up to an image tracking pixel that the merchandising team would have added to the confirmation page of each website

Shopzilla

Name Website on which Cookie is Active

Shopzilla Merchant ID (var MID)

All

Order value (var order _value)

All

Order ID (var ordere_id)

All

Customer Type (var cust_type)

All

Units Ordered (var units_ordered)

All

Cookie Types

Name Description

Shopzilla Merchant ID (var MID)

Purpose: Allows Shopzilla to correctly identify the order activity with Buyagift.co.uk.

Value to Enter: Your MID is 82754 and has been added to the code. DO NOT ALTER the "var mid" value in the code above.

Benefits: Your Merchant ID allows Shopzilla to correctly identify the order activity with Buyagift.co.uk.

Order value (var order _value)

Purpose:Specifies dollar value of an order.

Value to Enter: The total amount of the order without formatting. If the order value is £ 1,200.38, then populate the "var order_value" with '1200.38'. Do not include dollar signs or commas.

Benefits: Passing Order Value allows you to view Sales Revenue, Average Order Value, and Cost of Sale for Shopzilla-generated sales. This information is necessary to determine which products are driving sales at your store.

Order ID (var order_id)

Purpose:Specifies merchant order identification number associated with an order.

Value to Enter: The unique tracking number associated with an order. It can be numbers, letters, or both.

Benefits: The Order ID will help should any troubleshooting needs arise but will not be visible in your Shopzilla Performance Report.

Customer Type (var cust_type)

Purpose: Specifies whether the order is from a New or Repeat customer.

Value to Enter: For a new customer, populate the var cust_type with '1'. For a repeat customer, populate the var cust_type with '0'.

Only a 1 or a 0 is accepted in this field!

For an easy way to tell if a customer is new or repeat, check to see if the customer's email address already exists in your database.

Benefits: Passing Customer Type will allow you to see how many new customers were generated from your Shopzilla campaign and to determine the cost per new customer acquisition.

Units Ordered (var units_ordered)

Purpose:Specifies the number of units of merchandise associated with an order.

Value to Enter: Enter the number of units of merchandise that make up the order. For example, if someone orders a sweater, a shirt and a hat, the units ordered would be 3.

Benefits: This value assists you when performing order value analysis.

Kelkoo

Cookie Types

Refer to the following link for a full explanation http://www.kelkoo.co.uk/co_16734-privacy-policy-kelkoo-uk.html

Criteo

Criteo does not identify the visitor and do not gather any user information from the retail that may be stored such as name, address etc.. The advertisements do not combine information about the visitor from multiple sources. Criteo do not share any data with any site that displayed the Criteo advertising.

More information about Criteo may be gathered from http://www.criteo.com/en/privacy-policy.

These are set to expire 13 Months after being dropped, with the exception of the uid cookie (currently, uid cookie is kept for longer). This is due to be reduced to 13 Months expire date shortly; the uid cookie does not contain any browsing data.

Name Website on which Cookie is Active

ASP.NET_SessionID

jdsports.widget.criteo.com

X-Mapping-hmeipdnj

jdsports.widget.criteo.com

uid

.criteo.com

uic

.criteo.com

dis

.criteo.com

udc

.criteo.com

udi

.criteo.com

Cookie Types

Name Description Expire

ASP.NET_SessionID

Domain: jdsports.widget.criteo.com

Path: /

Send For: Any type of connection

At end of session

X-Mapping-hmeipdnj

Domain: jdsports.widget.criteo.com

Path: /

Send For: Any type of connection

At end of session

uid

Domain: .criteo.com

Path: /

Send For: Any type of connection

DD Month YYYY HH:MM:SS

uic

Domain: .criteo.com

Path: /

Send For: Any type of connection

DD Month YYYY HH:MM:SS

dis

Domain: .criteo.com

Path: /

Send For: Any type of connection

DD Month YYYY HH:MM:SS

udc

Domain: .criteo.com

Path: /

Send For: Any type of connection

DD Month YYYY HH:MM:SS

udi

Domain: .criteo.com

Path: /

Send For: Any type of connection

DD Month YYYY HH:MM:SS

Affiliate Window

Cookie Types

Reference to http://blog.affiliatewindow.com/wp-content/uploads/2012/03/The-ePrivacy-Directive-FAQs.pdf

Title Documentation Reference / Section Link

Affiliate Window

The ePrivacy Directive FAQs.pdf

http://blog.affiliatewindow.com/wp-content/uploads/2012/03/The-ePrivacy-Directive-FAQs.pdf

Opt-out Information

By using and browsing the JDSPORTS website, you are approving the use of cookies by JD in accordance with our cookies policy. If you have an objection to our use of cookies you must or disable the cookies or stop using the site.

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

For Microsoft Internet Explorer:
1. Choose the menu "tools" then "Internet Options"
2. Click on the "privacy" tab
3. Select the setting the appropriate setting
For Mozilla firefox:
1. Choose the menu "tools" then "Options"
2. Click on the icon "privacy"
3. Find the menu "cookie" and select the relevant options
For Opera 6.0 and further:
1. Choose the menu Files”> "Preferences"
2. Privacy
For further assistance please refer to help pages within your browser.
About Us
Customer Service

We accept the following payment methods

cards