NetDirector® Cookies

 

What are cookies?

Cookies are text files containing small amounts of information which are downloaded to your device when you visit a website. Software on your device, for example a web browser, stores the cookies and sends them back to a website next time you visit. Cookies allow websites to recognise your device and preferences and provide information to the owners of sites which can be used to improve your online experience. A number of websites provide details on cookies, including cookiedatabase.org and cookiepedia.co.uk.

The rules on cookies are covered by the Privacy and Electronic Communications Regulations 2003 (PECR). PECR also covers the use of similar technologies for storing or accessing information, such as ‘Flash cookies’ and device fingerprinting.

In the UK, the Information Commissioners Office (ICO) is responsible for enforcing these rules.

How do the cookie regulations affect consumers?

Consumers may come across information about cookies and similar technologies on websites and be given choices about how some cookies are used. This might include, for example, being asked to agree to a cookie being used for a particular service, such as remembering your preferences on a site.

Organisations have to provide clear and comprehensive information about the way they use cookies, and ensure that for any cookie not strictly necessary for their website, they give you an appropriate means of consenting to that cookie being set on your device.

What is a First-Party cookie?

First-party cookies are directly stored by the website (or domain) you visit. These cookies allow website owners to collect analytics data, remember language settings, and perform other useful functions that provide a good user experience. The domain host can see the data that the cookie retrieves. First-party cookies can’t usually be used to track a user’s activity on another site other than the original website it was placed on. These types of cookies include things such as your sign-on credentials, items you put in the shopping cart, or your preferred language.

First-party cookies are set by the publisher’s web server or any JavaScript loaded in the website.

What is a Third-Party cookie?

Third-party cookies are created by domains that are not the website (or domain) that you are visiting. These are usually used for online-advertising purposes and placed on a website through adding scripts or tags. A third-party cookie is accessible on any website that loads the third-party server’s code.

Cookies generated by NetDirector® and other technologies

The below tables detail the cookies generated by GForces NetDirector® suite of technologies so that you can share the information with consumers via your websites Cookie Policy. From time to time, this list will be updated when new cookies are added to GForces NetDirector® software platforms. Additionally, we have provided the lists of cookies generated by other common technologies added to GForces product suites.

NetDirector® Auto V10 cookies

Cookie Name Categorisation Description Duration 1st/3rd Party
dataLayer.visitor.isReturning Analytics Cookie to provide page view details to a GTM data layer where added. By default the cookie is set to 'True'. Persistent First Party
gf-session-id Required When users are navigating throughout the site this is used to determine a consistent session. E.g a user creates a transaction without being logged in and then the user logs in we can use the consistent session id to link the user to the transaction. This is set in local storage Session First Party
isSessionUsed Functional To determine if a session is used on the frontend. For example, a website page that requires a login screen because it's for internal use only. Session First Party
lastViewedVehicles_* Required Allows the breadcrumbs to work within the details pages Session First Party
PHPSESSID Required Preserves user session state across page requests. Session First Party
postcode Functional Saves the postcode used within vehicle search and dealer locator search so that it is populated for example do a postcode search on dealer locator page, go to used cars and postcode is populated. Session First Party
recentLocationHash Functional Allows the enquiry form where multiple locations may be present to populate the most recently used location for example on site enquiry forms. Session First Party
recentVehicles_* Required Stores the reference of the most recent vehicle viewed. Session First Party
searchPath_* Functional Welcome back module - Shows the continue search button within Welcome back by storing the search parameters Persistent First Party
searchQuery_* Required Enables site breadcrumbs to work with New Car Offers, vehicle search listings and details pages, and ensures that the lazy load search feature works correctly Session First Party
searchTags_* Required Enables the search pills to be displayed from the search selection Session First Party
sessionStorageTest Required Determines if sessionStorage is available Session First Party
storageSettings Required Determine which category of cookies can be stored locally Persistent First Party
trackingIpFilter Required Stores the user IP address when visiting the website for cyber security purposes in the event a user uses the website maliciously. 2 Years First Party
vehicleId Required Is used by the AJAX used vehicles listing to hold the last clicked vehicle, so that it can be scrolled to once the user revisits the listing Session First Party
vehicleIndex Required Works with vehicleQuery cookie to store the vehicle index of the vehicle in relation to the previous/next vehicle Session First Party
vehicleQuery Required Previous and next vehicle buttons - run search and go to vehicle details - buttons that allow you to go to previous and next within search results Session First Party
wasCtwPopupSeen Required To determine if the cookie banner has been engaged with and consent obtained 6 months First Party
wbClosed_* Required Determines if Welcome Back module has been closed Session First Party
XSRF-TOKEN Required Security cookie to prevent Cross site Forgery Session First Party
CONSENT Analytics YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. 2 Years youtube.com
VISITOR_INFO1_LIVE Functional Tries to estimate the users' bandwidth on pages with integrated YouTube videos. 6 months youtube.com
YSC Functional Registers a unique ID to keep statistics of what videos from YouTube the user has seen. Session youtube.com
yt-player-bandwidth Functional For YouTube to provide bandwidth estimations. Session youtube.com
yt-player-headers-readable Functional Used to determine the optimal YouTube video quality based on the visitor's device and network settings. Session youtube.com
yt.innertube::nextId Analytics This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. Session youtube.com
yt.innertube::requests Analytics This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. Session youtube.com

Note: Cookies used for YouTube will only be presented if there is YouTube videos added to the website.

NetDirector® Online Payments Cookies

Cookie Name Categorisation Description Duration 1st/3rd Party
auth-token Required Required by ecommerce module for session security Session First Party
currentTransaction Required A session storage variable that allows us to scope our API requests in a browser tab (so you can have two different concurrent transactions in different tabs). Functionally, we use this variable when the user logs in to allow us to transition an anonymous transaction onto a users account. Session First Party
ovs_criteria_* Functional Stores the budget search parameters so that they can be re-used when a user comes back and performs another search. Session First Party
ovs-entry-point Required Stores the entry page from the website into the ecommerce journey in the event of a network failure Session First Party
ovs-previous-step Required Stores the website previous page OR ecommerce previous step in the event of network failure Session First Party
gf-auth0-access-token Required Used to get user detail from auth0 and to generate an Auth token. This is set in session storage. Session First Party
gf-auth0-id-token Required Used to generate an Auth token. This is set in session storage. Session First Party
gf-jwt-token Required The internal auth token. This is stored in local storage so the user does not have to log in / get auth status from Auth0 on each page load which improves performance of the site. Session First Party
touchPayment Required Required by the Online Payment technology Session First Party

NetDirector® BI Cookies

Cookie Name Categorisation Description Duration 1st/3rd Party
_sp_id.* Analytics It is used to persist information about a user's activity on the domain between sessions to provide Business Intelligence for the software provider. It contains the following information: - An ID for the user based on a hash of various browser attributes - How many times the user has visited the domain - The timestamp of the user's first visit - The timestamp of the current visit - The timestamp of the last visit - The ID of the current session Persistent First Party
_sp_ses.* Analytics The purpose of this cookie is to differentiate between different visits to provide Business Intelligence for the website provider. Persistent First Party
enquiriesSent_* Analytics Captures the type of enquiries sent in a session. No PII is collected, only the enquiry type Session First Party
nd Analytics SnowPlow tracking - Events and Contexts Session First Party
session_counter_* Analytics Determines if ReturningUsers context should be sent (ie. if counter > 1 then send ReturningUsers context) Persistent First Party
session_was_counted_* Analytics Ensures current session is counted only once Session First Party
snowplowOutQueue_ndanalytics_nd_post2 Analytics Snowplow Analytics Used to store a cache of unsent events. This is used to reduce the chance of events to be lost due to page navigation and events not being set to the collector before the navigation event occurs. Where GET requests are used, this key will end in _get rather than _post2. Session First Party
snowplowOutQueue_ndanalytics_nd_post2.expires Analytics Snowplow Analytics Used to match the concept of cookie expiry within Local Storage. This ensures a consistent behaviour between cookie and local storage. Where GET requests are used, this key will end in _get rather than _post2. Session First Party
sp_landing_page Analytics Stores the landing page URL 1 day First Party
sp_referer Analytics Stores the host/referrer Session First Party
sp_referer_category Analytics Stores the referer/channel category Session First Party
sp_referrer_url Analytics Stores the referrer URL Session First Party

 

 

Google Analytics cookies

__utm.gif Analytics Google Analytics Tracking Pixel that logs details about the visitor's browser and computer. Session google-analytics.com
__utma Analytics Collects data on the number of times a user has visited the website as well as dates for the first and most recent visit. Used by Google Analytics. Persistent First Part
__utmb Analytics Registers a timestamp with the exact time of when the user accessed the website. Used by Google Analytic s to calculate the duration of a website visit. Session First Part
__utmc Analytics Registers a timestamp with the exact time of when the user leaves the website. Used by Google Analytics to calculate the duration of a website visit. 30 mins First Part
__utmt Analytics Stores the number of requests to the server. Used by Google Analytics. 10 mins First Part
__utmv Analytics Google Analytics __utmv Cookie lasts "forever". It is a persistant cookie. It is used for segmentation, data experimentation and the __utmv works hand in hand with the __utmz cookie to improve cookie targeting capabilities. Persistent First Part
__utmz Analytics Collects data on where the user came from, what search engine was used, what link was clicked and what search term was used. Used by Google Analytics. 6 months First Part
_ga Analytics The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. 2 years First Part
_gat_* Analytics Used to throttle the speed of requests to the server. Used by Google Analytics. 1 min First Part
_gid Analytics Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. 1 day First Part
collect Analytics Used to send data to Google Analytics about the visitors device and behaviour. Tracks the visitor across devices and marketing channels Session google-analytics.com
uid Analytics This cookie provides a uniquely assigned, machine-generated user ID and gathers data about activity on the website. This data is used by Google Analytics for analysis and reporting. Session First Party

Digital Retailing v2 cookies

Cookie Name Categorisation Description Duration 1st/3rd Party
ndfe-payment-state Required Stores the status of an online payment incase the users refreshes their browser so they don’t get charged twice. This cookie is only applicable if using checkout.com payment gateway. Session First Party

Gubagoo Chat cookies

Cookie Name Categorisation Description Duration 1st/3rd Party
__ggtrses functional Gubagoo - Stores data relating to chat feature. It uses a cookie to decide when to display the chat feature. 24 hours First Party
__ggtruid functional Gubagoo - Stores data relating to chat feature. It uses a cookie to identify and differentiate between user sessions. 2 years First Party
*:cache_expiry functional Gubagoo - to know when the items in LocalStorage should expire Persistant First Party
gg_chat_popup_closed functional Gubagoo - to know that the chat popup has been closed Persistant First Party
gg_chat_welcome_msg functional Gubagoo - to know if the welcome message has been displayed Persistant First Party
gg_emulation_welcome_msg functional Gubagoo - Stores data relating to chat feature. Welcome message to be displayed when chat is opened Persistant First Party
gg_firestamps functional Gubagoo - Stores data relating to engagement. Logs when a user engages with a portion of Gubagoo Persistant First Party
gg_firestamps:cache_expiry functional Gubagoo - to know when the firestamp data should expire 40 days First Party
gg_repeat functional Gubagoo - Stores data relating to chat feature. Determines if a chat element that was hidden should reshow Persistant First Party
gg_repeat:cache_expiry functional Gubagoo - to know when the repeat data should expire Persistant First Party
gg_tabs-opened functional Gubagoo - tracks the number of tabs Gubagoo is open on Persistant First Party
gg_view-*_time functional Gubagoo - Stores data relating to chat feature. Records time when a view was generated Persistant First Party
gg_*_1_ccpa_accept functional Gubagoo - Tracks whether or not a Cookie toolbar has been accepted. Moves the chat feature up or down if on the page. Persistant First Party
prox_id functional Gubagoo - Responsible for determining chat socket to Glive / Chat Console 24 hours First Party
*_cbo_in_transit_vins functional Gubagoo - Stores vehicle VINs that are in transit to dealership but still sold in VR Persistant First Party