Interruption is a way of life here in America. I remember reading somewhere that in Japan if a person is working by themselves they are not as likely to be interrupted because it is assumed that they are in thought whereas in America if you are working by yourself it means you are available because it is assumed you are not busy. Not sure if that is true or not, but I know that if I see someone at their desk I will talk to them if I need them. I always ask if they have time, but I still ask because – in famous final words fashion – it will only take a second.
How does this relate to web analytics? It relates because of the definition of a visit. If you are new to web analytics, you may wonder “What is a visit?”. Web Trends Live has an excellent glossary of terms which is where I pulled this definition from:
Visit: A visit is an interaction a unique visitor has with a website over a specified period of time or activity. In most cases, if a visitor has left a site or has not executed a click within 30 minutes, the visit session will terminate.
My question is, is this the correct length of time? Should it be longer than 30 min because of how many distractions/interruptions we have in a day? I read a great interview at FastCompany.com about how often people get interrupted at work. The average time between switching tasks was 3 minutes and 5 seconds. That is a lot of moving around. It took an average of 23 minutes and 15 seconds to get back to something they switched from.
This would give credence to the 30 minute rule that is laid out for us, but I still have to wonder if it is correct. I think that with tab browsing people are more likely to have a longer lag time between looking at one page and looking at another. I think that since the onset of ‘restore session’ – when you open up a browser that you previously exited with multiple tabs active – lag times between activity have increased. ‘Fires’ come up at work and need to be handled, e-mails come in, the phones ring, etc. The reality is that while a person may be idle for 30 min they would say that it was one visit. This begs the question of who defines a visit, the web site or the viewer?
My main concern is that this time frame may skew some data that looks at visits by a visitor for a given period of time. Perhaps you will get data that says people visit your site multiple times in one day – probably considered a good thing – when really you just can’t keep a visitors attention and they keep having a 30 min or more delay in between their activity. This would actually then be a bad thing because you are not keeping the viewer involved which may discourage them from coming back.
Clearly an industry needs standards and, honestly, web analysts are lucky to have any standards at all in a field that changes so quickly while being so young. That said, hanging on to old standards just for the sake of standards isn’t such a great policy either. It doesn’t need to change today, but it is something to keep thinking about as browsing habits evolve.