<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Time on Site &amp; Time on Page &#8211; Google Analytics metric mystery</title>
	<atom:link href="http://www.conceptcurry.com/web-analytics/time-spent-on-site-and-page-google-analytics/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.conceptcurry.com/web-analytics/time-spent-on-site-and-page-google-analytics/</link>
	<description>Startups, Web 2.0, Search Marketing, Social Media, Web Analytics, Online Travel, Mobile, Technology &#38; the Internet</description>
	<lastBuildDate>Thu, 18 Feb 2010 19:05:55 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Carl</title>
		<link>http://www.conceptcurry.com/web-analytics/time-spent-on-site-and-page-google-analytics/comment-page-1/#comment-184</link>
		<dc:creator>Carl</dc:creator>
		<pubDate>Sat, 13 Feb 2010 09:16:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.conceptcurry.com/?p=176#comment-184</guid>
		<description>Regarding the proposed adjustment of screening out bounces, that will help, but it still does not provide an accurate estimate because a visitor could land on your page, click off to a second page after 5 seconds, and then stay on that second page for 20 minutes, but the time on site would still display as 5 seconds.

One of my sites has a curious variant of this problem because it loads an iframe containing help pages on the main page using Javascript a few seconds after it comes up, and so the report has numerous visits that are a few seconds long, and no bounces at all.

My main page has interactive Javascript content, and that content is the main reason a visitor would come to the site, so it is entirely possible for a visitor to spend the entire visit there without loading another page.

A real solution might be for GA to hook the browser events in Javascript to detect user activity and then when a browser close was finally detected to report the time between the first page load and the most recent user action (not including the close).  This could also solve the problem of users leaving the browser open and running off to do something else.  Maybe GA does not want to do something that invasive and potentially disruptive, though, so it is what it is.</description>
		<content:encoded><![CDATA[<p>Regarding the proposed adjustment of screening out bounces, that will help, but it still does not provide an accurate estimate because a visitor could land on your page, click off to a second page after 5 seconds, and then stay on that second page for 20 minutes, but the time on site would still display as 5 seconds.</p>
<p>One of my sites has a curious variant of this problem because it loads an iframe containing help pages on the main page using Javascript a few seconds after it comes up, and so the report has numerous visits that are a few seconds long, and no bounces at all.</p>
<p>My main page has interactive Javascript content, and that content is the main reason a visitor would come to the site, so it is entirely possible for a visitor to spend the entire visit there without loading another page.</p>
<p>A real solution might be for GA to hook the browser events in Javascript to detect user activity and then when a browser close was finally detected to report the time between the first page load and the most recent user action (not including the close).  This could also solve the problem of users leaving the browser open and running off to do something else.  Maybe GA does not want to do something that invasive and potentially disruptive, though, so it is what it is.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nicole saunders</title>
		<link>http://www.conceptcurry.com/web-analytics/time-spent-on-site-and-page-google-analytics/comment-page-1/#comment-182</link>
		<dc:creator>nicole saunders</dc:creator>
		<pubDate>Wed, 06 Jan 2010 20:59:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.conceptcurry.com/?p=176#comment-182</guid>
		<description>That was a highly informative article...Thanks for a lot for posting it...keep up the gr8 work...</description>
		<content:encoded><![CDATA[<p>That was a highly informative article&#8230;Thanks for a lot for posting it&#8230;keep up the gr8 work&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Measuring Website Usage With Google Analytics, Part I &#171; JISCPress</title>
		<link>http://www.conceptcurry.com/web-analytics/time-spent-on-site-and-page-google-analytics/comment-page-1/#comment-181</link>
		<dc:creator>Measuring Website Usage With Google Analytics, Part I &#171; JISCPress</dc:creator>
		<pubDate>Thu, 17 Dec 2009 13:42:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.conceptcurry.com/?p=176#comment-181</guid>
		<description>[...] Which is why the emphasis on collecting stats from at last two pages: given the current crop of analytics tools that struggle to do anything meaningful with single page visits, specifying a two page visit means that not only visits to the site that are likely to be meaningful are reported, but also that the reports are more likely to contain meaningful data too. (There is an obvious problem here: if visitors visit two pages, and quickly click to the second from the first before exiting the site from the second page, the time spent on the second page won&#8217;t be captured? See for example Time on Site &amp; Time on Page – Google Analytics metric mystery) [...]</description>
		<content:encoded><![CDATA[<p>[...] Which is why the emphasis on collecting stats from at last two pages: given the current crop of analytics tools that struggle to do anything meaningful with single page visits, specifying a two page visit means that not only visits to the site that are likely to be meaningful are reported, but also that the reports are more likely to contain meaningful data too. (There is an obvious problem here: if visitors visit two pages, and quickly click to the second from the first before exiting the site from the second page, the time spent on the second page won&#8217;t be captured? See for example Time on Site &amp; Time on Page – Google Analytics metric mystery) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Measuring Website Usage With Google Analytics, Part I at Actually&#8230;</title>
		<link>http://www.conceptcurry.com/web-analytics/time-spent-on-site-and-page-google-analytics/comment-page-1/#comment-180</link>
		<dc:creator>Measuring Website Usage With Google Analytics, Part I at Actually&#8230;</dc:creator>
		<pubDate>Sun, 22 Nov 2009 19:22:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.conceptcurry.com/?p=176#comment-180</guid>
		<description>[...] Which is why the emphasis on collecting stats from at last two pages: given the current crop of analytics tools that struggle to do anything meaningful with single page visits, specifying a two page visit means that not only visits to the site that are likely to be meaningful are reported, but also that the reports are more likely to contain meaningful data too. (There is an obvious problem here: if visitors visit two pages, and quickly click to the second from the first before exiting the site from the second page, the time spent on the second page won&#8217;t be captured? See for example Time on Site &amp; Time on Page – Google Analytics metric mystery) [...]</description>
		<content:encoded><![CDATA[<p>[...] Which is why the emphasis on collecting stats from at last two pages: given the current crop of analytics tools that struggle to do anything meaningful with single page visits, specifying a two page visit means that not only visits to the site that are likely to be meaningful are reported, but also that the reports are more likely to contain meaningful data too. (There is an obvious problem here: if visitors visit two pages, and quickly click to the second from the first before exiting the site from the second page, the time spent on the second page won&#8217;t be captured? See for example Time on Site &amp; Time on Page – Google Analytics metric mystery) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: usability testing</title>
		<link>http://www.conceptcurry.com/web-analytics/time-spent-on-site-and-page-google-analytics/comment-page-1/#comment-177</link>
		<dc:creator>usability testing</dc:creator>
		<pubDate>Sun, 05 Jul 2009 04:56:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.conceptcurry.com/?p=176#comment-177</guid>
		<description>this post is incredible helpful! i could not figure out what all those 0:00 visits meant and your site has the clearest explanation.

so another question - is there an easy way to remove or filter these &quot;bounce&quot; visits from our site analytics? it seems like these visits from bots or other sources are skewing our site metrics - is that correct? is there a standard practice around this that you would suggest?

thanks</description>
		<content:encoded><![CDATA[<p>this post is incredible helpful! i could not figure out what all those 0:00 visits meant and your site has the clearest explanation.</p>
<p>so another question &#8211; is there an easy way to remove or filter these &#8220;bounce&#8221; visits from our site analytics? it seems like these visits from bots or other sources are skewing our site metrics &#8211; is that correct? is there a standard practice around this that you would suggest?</p>
<p>thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: iprogrammer</title>
		<link>http://www.conceptcurry.com/web-analytics/time-spent-on-site-and-page-google-analytics/comment-page-1/#comment-163</link>
		<dc:creator>iprogrammer</dc:creator>
		<pubDate>Mon, 02 Mar 2009 12:55:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.conceptcurry.com/?p=176#comment-163</guid>
		<description>Hi Abhi this is great article, but can you elaborate on Time on Page &amp; Time on Site, I mean according to your article are these 2 totals should be equal? If No then can you please explain why?</description>
		<content:encoded><![CDATA[<p>Hi Abhi this is great article, but can you elaborate on Time on Page &amp; Time on Site, I mean according to your article are these 2 totals should be equal? If No then can you please explain why?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Abhishek Bhardwaj</title>
		<link>http://www.conceptcurry.com/web-analytics/time-spent-on-site-and-page-google-analytics/comment-page-1/#comment-129</link>
		<dc:creator>Abhishek Bhardwaj</dc:creator>
		<pubDate>Sat, 03 Jan 2009 04:19:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.conceptcurry.com/?p=176#comment-129</guid>
		<description>Re: eye tracking research 

Yes the formula you applied gave you the actual time spent on your site i.e. the time spent by actual visitors who stayed on your website. This formula excludes the visitors who bounced without navigating further into your site.</description>
		<content:encoded><![CDATA[<p>Re: eye tracking research </p>
<p>Yes the formula you applied gave you the actual time spent on your site i.e. the time spent by actual visitors who stayed on your website. This formula excludes the visitors who bounced without navigating further into your site.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: eye tracking research</title>
		<link>http://www.conceptcurry.com/web-analytics/time-spent-on-site-and-page-google-analytics/comment-page-1/#comment-128</link>
		<dc:creator>eye tracking research</dc:creator>
		<pubDate>Sat, 03 Jan 2009 02:59:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.conceptcurry.com/?p=176#comment-128</guid>
		<description>Ah, this is a GREAT article. All of the 0:00 page views in google analytics were confusing the heck out of me! I thought they might be from automated bots? (is there any way to estimate that?)

I took your formula and applied it - very helpful.

personally i find it a little easier to compute this more quickly by multiplying the reported site time by 100/bounce rate.

example:
*reported site time = 65 seconds. *bounce rate of 50%

**actual time: then 100/50% = 2 and 2*65 =130seconds.</description>
		<content:encoded><![CDATA[<p>Ah, this is a GREAT article. All of the 0:00 page views in google analytics were confusing the heck out of me! I thought they might be from automated bots? (is there any way to estimate that?)</p>
<p>I took your formula and applied it &#8211; very helpful.</p>
<p>personally i find it a little easier to compute this more quickly by multiplying the reported site time by 100/bounce rate.</p>
<p>example:<br />
*reported site time = 65 seconds. *bounce rate of 50%</p>
<p>**actual time: then 100/50% = 2 and 2*65 =130seconds.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pagealizer</title>
		<link>http://www.conceptcurry.com/web-analytics/time-spent-on-site-and-page-google-analytics/comment-page-1/#comment-113</link>
		<dc:creator>Pagealizer</dc:creator>
		<pubDate>Wed, 10 Dec 2008 13:12:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.conceptcurry.com/?p=176#comment-113</guid>
		<description>All site analytics show you some stats on how long people visit your page. Most site analytic services guess how long a visitor has been on a page by noting when a visitor arrives and that visitor views another page in the site. This calculation is a good estimate in general but has its weakness when calculating first page visit length - sometimes there isn&#039;t a second page view. &lt;a href=&quot;http://www.pagealizer.com&quot; rel=&quot;nofollow&quot;&gt;Pagealizer&lt;/a&gt; does actual counting. Our tracking code pings the tracking server as long as the visitor has the page open. 
This metric is very important for landing/sales pages which a lot of times do not trigger another page view and help you understand if people read your page. If for example you have long copy and most people visit your page for 10 seconds you might need to add more call to action links on the top of your page or reduce the amount of text. Check us out :)</description>
		<content:encoded><![CDATA[<p>All site analytics show you some stats on how long people visit your page. Most site analytic services guess how long a visitor has been on a page by noting when a visitor arrives and that visitor views another page in the site. This calculation is a good estimate in general but has its weakness when calculating first page visit length &#8211; sometimes there isn&#8217;t a second page view. <a rel="nofollow" target="_blank" href="http://www.pagealizer.com" rel="nofollow">Pagealizer</a> does actual counting. Our tracking code pings the tracking server as long as the visitor has the page open.<br />
This metric is very important for landing/sales pages which a lot of times do not trigger another page view and help you understand if people read your page. If for example you have long copy and most people visit your page for 10 seconds you might need to add more call to action links on the top of your page or reduce the amount of text. Check us out <img src='http://www.conceptcurry.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
