<?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: Back button breaks Internet advertising</title>
	<atom:link href="http://www.robmanuel.com/2007/03/23/back-button-breaks-internet-advertising/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.robmanuel.com/2007/03/23/back-button-breaks-internet-advertising/</link>
	<description>follow me on http://twitter.com/robmanuel</description>
	<lastBuildDate>Mon, 23 Jan 2012 18:18:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Jobbys</title>
		<link>http://www.robmanuel.com/2007/03/23/back-button-breaks-internet-advertising/comment-page-1/#comment-6084</link>
		<dc:creator>Jobbys</dc:creator>
		<pubDate>Sat, 24 Mar 2007 08:47:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.robmanuel.com/2007/03/23/back-button-breaks-internet-advertising/#comment-6084</guid>
		<description>As you know it&#039;ll most likely be a cache busting ad tag that causes the behaviour.

On the advertisers side your almost always going to want to get another ad impression counted rather than have the same ad displayed from user&#039;s cache. Typical stats suggest something like 20% of page impressions are from people using the back button.  That&#039;s a lot of potential impressions to lose, compared to the very rare occasion that a user actually wants to look at the exact same ad they saw before.

Of course if your not rotating ads on the page in question, they&#039;ll see the same ad creative, the cache busting will just ensures the publisher gets another ad impression counted.

I suppose the user&#039;s browser could be configured to use only cached content when using the back button, if that&#039;s the behaviour wanted. Though in a lot of cases they&#039;ll want/expect page content to be updated, particularly on more dynamic pages such as News sites.</description>
		<content:encoded><![CDATA[<p>As you know it&#8217;ll most likely be a cache busting ad tag that causes the behaviour.</p>
<p>On the advertisers side your almost always going to want to get another ad impression counted rather than have the same ad displayed from user&#8217;s cache. Typical stats suggest something like 20% of page impressions are from people using the back button.  That&#8217;s a lot of potential impressions to lose, compared to the very rare occasion that a user actually wants to look at the exact same ad they saw before.</p>
<p>Of course if your not rotating ads on the page in question, they&#8217;ll see the same ad creative, the cache busting will just ensures the publisher gets another ad impression counted.</p>
<p>I suppose the user&#8217;s browser could be configured to use only cached content when using the back button, if that&#8217;s the behaviour wanted. Though in a lot of cases they&#8217;ll want/expect page content to be updated, particularly on more dynamic pages such as News sites.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

