I've just installed GA on my news aggregator.
Now, apparently a "visit" is a group of interactions that last up to 30 minutes at which point the analytics tracking cookie gets reset. So if the cookie sits idle for half an hour cos the user has gone for a dump or whatever and he then comes back and starts moving around the site again, this counts as a new visit. Should I take it that any user who stays on my site for 30 minutes is a good thing and that he a) didn't die or b) isn't sitting in another tab fapping over WF bewbs threads?
The real problem for me is that my site includes a LOT of reading and my users ARE likely to stay in a page longer than 30 minutes. At first glance this is gonna screw my tracking completely.
Is there a way to allow for / filter out this behaviour in GA? Or is there a way in code to bugger about with the __UTMB cookie? If I'm asking a tard question or I'm in the wrong place, please feel free to shat on me / stab my kittens / set fire to my house.
Now, apparently a "visit" is a group of interactions that last up to 30 minutes at which point the analytics tracking cookie gets reset. So if the cookie sits idle for half an hour cos the user has gone for a dump or whatever and he then comes back and starts moving around the site again, this counts as a new visit. Should I take it that any user who stays on my site for 30 minutes is a good thing and that he a) didn't die or b) isn't sitting in another tab fapping over WF bewbs threads?
The real problem for me is that my site includes a LOT of reading and my users ARE likely to stay in a page longer than 30 minutes. At first glance this is gonna screw my tracking completely.
Is there a way to allow for / filter out this behaviour in GA? Or is there a way in code to bugger about with the __UTMB cookie? If I'm asking a tard question or I'm in the wrong place, please feel free to shat on me / stab my kittens / set fire to my house.