Cookies : Disclaimer
** Cookies enable us to identify your device, or you when you have logged in. We use cookies that are strictly necessary to enable you to move around the site or to provide certain basic features. We use cookies to enhance the functionality of the website by storing your preferences, for example. We also use cookies to help us to improve the performance of our website to provide you with a better user experience. The cookies we use are “analytical” cookies. They allow us to recognise and count the number of visitors and to see how visitors move around the site 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.
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.
Most web browsers allow some control of most cookies through the browser settings. To find out more about cookies, including how to see what cookies have been set and how to manage and delete them, visit www.allaboutcookies.org.
[By using our website, you consent to our use of cookies as described above.]
** The information contained in this website is for general information purposes only. The information is provided by wikiwirral and while we endeavour to keep the information up to date and correct, we make no representations or warranties of any kind, express or implied, about the completeness, accuracy, reliability, suitability or availability with respect to the website or the information, products, services, or related graphics contained on the website for any purpose. Any reliance you place on such information is therefore strictly at your own risk.
Stored cookies
| Cookie Name | Expires | Source |
|---|---|---|
| __utma | +2yrs | Google Analytics |
| __utmb | +2yrs | Google Analytics |
| __utmc | Session | Google Analytics |
| __utmz | +1yr | Google Analytics |
| PHPSESSID | Session | wikiwirral |
| ubbt_myid | Session | wikiwirral |
| ubbt_key | Session | wikiwirral |
| ubbt_mysess | Session | wikiwirral |
Sessions
When you close your browser or log out, that is the end of a session.
Google Analytics
Google Analytics will collect cookie inforamtion from you if you are registered or not. If you do not wish google Analitics to track your visit then you should clear your cookies via your browser upon exit. Registered users may use the clear cookies function via there Profile page (My Stuff >> Cookies). By clearing your cookies you will also log yourself out from the forums.
The Very Basics – The Google Analytics Cookies
When someone visits a website that is properly coded with Google Analytics Tracking Code, that website sets four first-party cookies on the visitor’s computer automatically.
…Wait a Minute, What’s a “First-Party Cookie”?
A “first-party cookie” is a cookie that is set by that same website. This term exists because there are also “third-party cookies”, which are cookies that are set by other third party websites (you don’t even need to visit that third party website to have a cookie set – don’t worry, Google Analytics ONLY uses first-party cookies).
So, What Are These Four Cookies?
Well, there can be up to five different cookies that a website with Google Analytics tracking code sets on your computer. However, four of them are automatically set, while the fifth one is an optional cookie. Let’s take a look at each one.
The __utma Cookie
This cookie is what’s called a “persistent” cookie, as in, it never expires (technically, it does expire…in the year 2038…but for the sake of explanation, let’s pretend that it never expires, ever). This cookie keeps track of the number of times a visitor has been to the site pertaining to the cookie, when their first visit was, and when their last visit occurred. Google Analytics uses the information from this cookie to calculate things like Days and Visits to purchase.
The __utmb and __utmc Cookies
The B and C 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.
The __utmz Cookie
Mr. __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 15,768,000 seconds – or, 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.
The __utmv Cookie
If you are making use of the user-defined report in Google Analytics, and have coded something on your site for some custom segmentation, the __utmv cookie gets set on the person’s computer, so that Google Analytics knows how to classify that visitor. The __utmv cookie is also a persistent, lifetime cookie.
That’s all Great, but What if Someone Deletes These Cookies from their Computers?
Unfortunately, you cannot do anything about someone deleting their cookies from their computers. The __utmb and __utmc cookies are gone before you know it, but the __utma, __utmz, and __utmv cookie (when applicable) will remain for a long period of time. Whenever someone deletes the __utma cookie, they are in essence deleting their history with your website. When they visit your website again, they are considered a brand new visitor, just as they were the first time they came around.
How Concerned Should I Be about This?
Concerned isn’t the word I would use. I would be “aware” of this, but there should be no cause for concern on your part. Over time, you will have collected enough data, and you will have been able to make some pretty good guesses on what’s going on and what to do, by analyzing trends and observing patterns, rather than having to rely on whole numbers. Remember, Google Analytics is a trending and analysis tool, not an accounting software program or a report of your server logs. It relies on data collection via javascript and cookie placements, and not every single person in the world has either enabled on their browser of choice.
Source Click Me