Every Wednesday, I sit down and interview different metrics or report sections from Google Analytics. I ask the tough questions – and I expect straight answers! (This, obviously, is a fictional interview. However, if metrics or reports could talk and be interviewed, this is how I imagine their personalities being and how they would answer my questions. Hopefully this will be a fresh, interesting way to learn about the wonderful world of Google Analytics in a unique way).
Joe Teixeira: “Mr. Average Time on Site…how are things?”
Average Time on Site: “…Average…”
JT: “What’s with the sunglasses?”
ATOS: “…It’s bright in here…”
JT: “Well those are just the studio lights…I can have them turned down if you…”
ATOS: “No…it’s cool.”
JT: “Ummm…OK. Well let me ask you my first question. Can you explain to everyone exactly how you are calculated?”
ATOS: [Turns Away in Disgust and Rolls Eyes] “Man…come on, man. Why you gotta play me like that? Everybody knows it’s up to __utmb and __utmc to calculate the difference between the time stamps of each page. I ain’t got nuthin’ to do with any of that.”
JT: “So, two cookies – __utmb and __utmc – they calculate you…”
ATOS: “Yeah, man…”
JT: “…and the difference between each time stamp on each page is the time a user spent on that page…”
ATOS: “Yeah…”
JT: “…and then the Average Time on Site is the sum of all of the time a user – or groups of users – spent on the pages of a site, divided by the number of pages viewed.”
ATOS: “…something like that. If you know all this, how come you’re asking me, man?”
JT: “Because I wanted to hear what you’d have to say about it…”
ATOS: [Becoming more frustrated] “Look, man, this is how it goes down, a’ight? If somebody bounces from a landing page, guess what happens? I become an average of 0:00:00, because there ain’t no second timestamp to go by, so [pointing to the ceiling] the big man upstairs [GA] can’t give me credit for my time. It ain’t my fault, I’m just doing my job around here.”
JT: “So you really have a problem with this. What about people that leave their computers on and go to lunch, or go to a meeting?”
ATOS: “It’s the same thing, except backwards. Let’s say somebody goes to lunch for an hour and they leave they browser on…after 29 minutes of what they like to call “inactivity”, I stop counting. This happens ALL THE TIME, man. It just ain’t right! If they time me out, no second timestamp happens, which again means the average time for that page becomes 0:00:00.”
JT: “What I’m gathering from you is the message you’re trying to convey here is for people who look at you, and use you in their reports and presentations, to take you with a grain of salt…to use your number precariously.”
ATOS: “Well I don’t know what “precariously” means…but yeah, don’t do that.”
JT: “Last week, I talked briefly to Bounce Rate about setVar, and how his change in classification has impacted him. How has the update to setVar affected you?”
ATOS: “Man, it’s about time they did somethin’ about that. setVar ain’t nothing but a greedy metric, man. I’ve been tryin’ to tell people about setVar, and how it was being counted as an interaction hit, but they weren’t listening to me…but finally they took care of some business and straightened things out.”
JT: “Well, thanks a lot for your time…”
ATOS: “Oh, shoot – we done already?”
JT: “Yeah, I’m sorry…”
ATOS: “C’mon, man…I get paid by the second…”
JT: “Sorry, ATOS…maybe some other time.”
ATOS: “…whatever, man. That’s what everyone always says: “Time”. More time, less time, average time…everyone always wants to know about time. People need to just chill for a second and look at everything else, not just me…”
JT: “Well…thanks again [I start getting up].”
Wednesday Interview Series:
February 11, 2009: Bounce Rate