The BAM PPP website at www.bamppp.com utilises Google Analytics for purpose of gathering website statistics. Google Analytics is an online tool which enables website owners and developers to establish where visitors to the site are located, identify the route taken to get the website and determine how they used the site.
Google Analytics is an extremely useful tool which enables website developers to identify the most popular pages within the website, ensure users of the site are able to find relevant content and that users find the site easy to navigate.
The list below provides details of the cookies that have been developed by Google Analytics and currently utilised by BAM PPP.
Cookies Used by BAM PPP
|__utma||This cookie is typically written to the browser upon the first visit to our site from that web browser. If the cookie has been deleted by the browser operator, and the browser subsequently visits our site, a new __utma cookie is written with a different unique ID. This cookie is used to determine unique visitors to our 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 our site. When a user views a page on our 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 our 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 our site for longer than 30 minutes. We 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 tracking code, this cookie will continue to be written and will expire when the user exits the browser. However, if you are debugging our 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 our 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 our own site. The cookie is updated with each page view to our 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 we 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 we have added the _setVar() method for the tracking code on our 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 our 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 our site. See the Website Optimizer Help Center for more information.||2 years from set/update.|
The table below provides further details of the cookies that form part of the Google Analytics application and the purpose of each of the cookies.
Functionality of Cookies used by BAM PPP
|Functionality||Description of Cookie||Cookie Used|
|Setting the Scope of our Site Content||Because any cookie read/write access is restricted by a combination of the cookie name and its domain, default visitor tracking via Google Analytics is confined to the domain of the page on which the tracking code is installed. For the most common scenario where the tracking code is installed on a single domain (and no other sub-domains), the generic setup is correct. In other situations where we wish to track content across domains or sub-domains, or restrict tracking to a smaller section of a single domain, we use additional methods in the ga.js tracking code to define content scope. See Domains & Directories in the Collection API document for details.||All Cookies|
|Determining Visitor Session||The Google Analytics tracking for ga.js uses two cookies to establish a session. If either of these two cookies are absent, further activity by the user initiates the start of a new session. See the Session article in the Help Center for a detailed definition and a list of scenarios that end a session. We can customize the length of the default session time using the _setSessionCookieTimeout() method. This description is specific to the ga.js tracking code for web pages.||
|Identifying Unique Visitors||Each unique browser that visits a page on our site is provided with a unique ID via the __utma cookie. In this way, subsequent visits to our website via the same browser are recorded as belonging to the same (unique) visitor. Thus, if a person interacted with our website using both Firefox and Internet Explorer, the Analytics reports would track this activity under two unique visitors. Similarly if the same browser were used by two different visitors, but with a separate computer account for each, the activity would be recorded under two unique visitor IDs. On the other hand, if the browser happens to be used by two different people sharing the same computer account, one unique visitor ID is recorded, even though two unique individuals accessed the site.||__utma|
|Tracking Traffic Sources & Navigation||When visitors reach our site via a search engine result, a direct link, or an ad that links to our page, Google Analytics stores the type of referral information in a cookie. The parameters in the cookie value string are parsed and sent in the GIF Request (in the utmcc variable). The expiration date for the cookie is set as 6 months into the future. This cookie gets updated with each subsequent page view to our site; thus it is used to determine visitor navigation within our site.||__utmz|
|Custom Variables||We can define our own segments for reporting on our particular data. When we use the _setCustomVar() method in our tracking code to define custom variables, Google Analytics uses this cookie to track and report on that information. In a typical use case, we might use this method to segment our website visitors by a custom demographic that they select on our website (income, age range, product preferences).||___utmv|
|Website Optimizer||We can use Google Analytics with Google Website Optimizer (GWO), which is a tool that helps determine the most effective design for our site. When a website optimizer script executes on our page, a _utmx cookie is written to the browser and its value is sent to Google Analytics. See the Website Optimizer Help Center for more information.||___utmx|
Once the cookies are set/updated on the web browser, the data they contain that is required for reporting purposes is sent to the Analytics servers in the GIF Request URL via the utmcc parameter.
Source : Google Analytics (https://developers.google.com/analytics/resources/concepts/gaConceptsCookies)