The Cookie Monster Goes to Washington
Friday, October 31st, 2008
“Me want cookies!” This is what I hear many of my Government clients say – more specifically they want to understand cookies in relation to their web analytics. I have come to call this the “Cookie Monster” issue since there is so much confusion. So for my post here (and with many thanks to DJ) I thought Let’s start with dessert first!
Below I have listed from most accurate to less accurate the ways visitors are identified on-line:
- Authenticated: The technique by which access to Internet or intranet resources requires the user to enter a username and password as identification. This is the only way to count visitors “across machines”, as no matter where they log in they are identified correctly. Cookies are really just tracking unique computers!
- Persistent Cookies : A text file containing a random identification string that “lives” on the visitors computer. Using the value stored in this cookie, WebTrends can identify if you’ve been to the site before and identify you as a “new” or “returning” visitor (but can’t tell anything else about you… it’s a random number after all!). This is also used to provide “unique visitor” counts in WebTrends.
- Session Cookies : A text file containing a random identification string that only remains in the computer’s memory for the length of the visit, or “session”. It does not live on the machine after you navigate away from the site that set it, so there is no way to identify visitors that have been to the site before.
- IP Address : Internet Protocol Address is used to identify a computer connect to the internet. Since there are only so many IP addresses to go around, more often than not individual machines end up sharing the same IP address due to the use of proxy servers (used by large organizations like companies and universities), internet service providers or even home wireless routers.


If you haven’t used the new
Content groups are probably the most common dynamic parameters I see people setting up when tagging their site. By dynamic parameters I mean something the logging script doesn’t grab automatically and you have to actually put some effort into. Yes WT.cg_n and WT.cg_s are standard parameters not like DCSext, and Content Group reporting is in the standard report package. But defining and then implementing content groups is a very non-standard process.
The recommended practice for defining Content Groups, Sub Groups and how they will be organized is to use your site map or navigation tree. Your average to medium-sized web site will have at least a two tier navigation represented by drop down, fold out, or sub menus. So if you’re lucky enough to have a typical web site you can pretty much just replicate this structure. If you’re really lucky (or rather if the site developers are lucky) you can even leach the values you are assigning to WT.cg_n and WT.cg_s from the little Java Script function that builds your navigational menu or bread crumb navigation.
Someone never asked me this week “What do you think is best Parameter in WebTrends Analytics?” Without hesitating for even a moment (I didn’t even blink) I was able to answer straight from (my man sized but well toned and shaped) gut with 100% conviction and certainty that WT.Seg_X was definitely THE all time best ever WebTrends parameter.
Follow us on Twitter




