I recently blogged about cookies and the possible approaches we are hoping or looking to adopt here in Devon. Well it has taken me sometime to actually find the time to blog about this but our approach has already started to hit the web on some of our microsites.
My personal preference was to simply adopt an implied consent approach (the far easiest and lowest cost approach), but in conversations with colleagues we agreed that this would fail to raise the awareness of the issues, so we opted in the end for an “in yer face” approach.
I personally feel the more subtle approach (adopted by some) fails to raise awareness and because it isn’t that obvious for people, it will naturally lead to some functions of the site not working or displaying correctly without them knowing why – a big #fail in my eyes. But I certainly recommend that people adopt an approach they feel works for them and their organisation – I am merely passing comment and sharing our approach.
What have we done?
We have created a piece of reusable code which applies our global header and footer as well as a process for managing google analytics code…the technical details of which i can’t start to explain here but Tim in my team has developed this approach from the bottom up. But in short we developed an approach which basically stops the google code from being applied to the pages of the site until after they have accepted the cookie, if they decline we don’t process the google analytics code and we no longer get stats on those users.
The advantage of this approach is that we also get to apply a high level branding to most if not all of our microsites in the same process. Win Win…which was a task we set over a longer period of time, but this approach simply presented itself and allowed us to take advantage.
Check out the following sites which are the first to have the code applied – we have a large number of sites to apply this to and we are working really hard to get this done as soon as possible.