Last updated on 13/03/2015
The following list of cookies are those used on our site which we have identified as being for performance:
1st Party cookies
A "first party" cookie is either set by Just Eat itself or by a tool using the Just Eat domain. For example, Just Eat uses Google Analytics first party cookies on your machine
|Tool/Company||Cookie name||What does it do?|
|Just Eat website||Conversation ID||Only for app users. Just Eat uses the conversation ID, to trace the activities of a user of our apps (including but not limited to iOS, Android & Windows Phone apps) through all of our servers. This allows Just Eat to more effectively debug and trace issues that may arise. No events are logged that contain personal information, and the data collected is never shared outside of Just Eat. conversation ID is deleted if you delete the app.|
|je-logging||Just Eat uses this cookie to track a user's session for reporting purposes.|
|je-order||This cookie is used by Just Eat to track customer usage of the 'Re-order' feature, which allows customers to quickly order a meal they've had previously.|
|je-session||This is used for tracking a user throughout their session|
|searchApi||This cookie is used by Just Eat to track customer usage of the new search results page, to ensure that the algorithm we use to rank restaurants is working as well as it can.|
Just Eat uses ClickTale to identify usability problems with the website.
The __CT_Data cookie is used to count the number of pageviews or visits of the anonymous visitor for the purpose of enabling the ClickTale software to track the number of pageviews or visits a visitor made on Just Eat's website.
The WRIgnore cookie is created if the domain is not selected or if the account has run out of recording credits. It provides information that the specific visitor should not be recorded or tracked by the ClickTale software.
The WRUID cookie is used to anonymously identify a visitor of Just Eat's Website for the purpose of enabling the ClickTale software to track such visitor's actions across the Just Eat website.
If a visitor to Just Eat's website does not wish to be tracked by the software he may opt-out through the following link: http://www.clicktale.net/disable.html. Clicking this link shall place the WRBlock cookie on the visitor's machine for the purpose of blocking any recording by the ClickTale software of this visitor's session.
Just Eat uses Google Analytics to monitor usage of the website
The __utmb and __utmc cookies are brothers, working together to calculate how long a visit takes. __utmb takes a timestamp of the exact moment in time when a visitor enters a site, while __utmc takes a timestamp of the exact moment in time when a visitor leaves a site. __utmb expires at the end of the session. __utmc waits 30 minutes, and then it expires. You see, __utmc has no way of knowing when a user closes their browser or leaves a website, so it waits 30 minutes for another pageview to happen, and if it doesn't, it expires.
__utmz keeps track of where the visitor came from, what search engine you used, what link you clicked on, what keyword you used, and where they were in the world when you accessed a website. It expires in 6 months. This cookie is how Google Analytics knows to whom and to what source / medium / keyword to assign the credit for a Goal Conversion or an Ecommerce Transaction. __utmz also lets you edit its length with a simple customization to the Google Analytics Tracking code.
__utmt_UA- is used to track Events.
_ga stores the unique ID of the user for analytical purposes.
_gat is used to throttle the request rate.
_gali is used to monitor performance of the website and improve it.
Just Eat uses OpinionLab to gather customer feedback about the website to help us improve it. There are a number of cookies used to help us do so.
3rd Party cookies
Third party cookies are cookies that have been written on to your browser or device by a website that is different from the website you are actually visiting (i.e. by a site other than Just Eat, in this case).
|Tool/Company||Cookie name||What does it do?|
|Ad-X (and Criteo 5888)||ADX_com.justeat.JUSTEAT||
Only for app users. The ADX_com.justeat.JUSTEAT cookie allows us to identify which source an app was installed from and additional user actions after that, such as whether an order was placed.
AD-X sends information relating to your use of our apps and third party apps and websites to Just Eat's partner Criteo for the purpose of targeted marketing to you (see Targeting and Sharing Cookies).
AD-X shares data with other third party networks when instructed to do so by Just Eat from time to time. A list of these third parties (as may be updated from time to time) is available here: http://wiki.adxtracking.com/en/index.php?title=Integrated_Networks
Just Eat uses Optimizely to test variations of a web page. These cookies are used to track which variation a customer sees and to track their usage
More info: https://www.optimizely.com/privacy
|optimizelyEndUserId||Just Eat uses Optimizely to test variations of a web page. These cookies are used to track which variation a customer sees and to track their usage|
|optimizelyPendingLogEvents||Just Eat uses Optimizely to test variations of a web page. These cookies are used to track which variation a customer sees and to track their usage|
|Piwik (TV Squared)||_pk_uid||
Just Eat uses TV Squared for targeting adverts to customers based on interest. TV Squared use Piwik - an analytics tool - to measure the success of targeted adverts.
More info: http://piwik.org/privacy-policy/
Opt out: http://piwik.org/privacy/
|_pk_id||This contains a 64-byte int UUID that is generated when the cookie is created. It contains a timestamp of the cookie creation date in UTC, which is used to process the days it took for goal conversion. It contains a visits count that is updated when a _pk_ses cookie is created and this is used to calculate Visits to conversion. It contains a timestamp of the last page view of the last visit before this visit, which is used to process Days since last visit and Days to purchase.|
|_pk_ref||This contains the referrer URL, which is truncated at 1024 bytes. It also contains the time the referrer URL was set.|
|_pk_ses||This contains no data. Every time a new _pk_ses is created, 1 is added to the visits counter in the _pk_id cookie.|