<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Insight Buzz &#187; Public Relations</title>
	<atom:link href="http://www.insightbuzz.com/category/public-relations/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.insightbuzz.com</link>
	<description>Paul M. Banas on Consumer Insights, Marketing Research, and the Digital Media Landscape</description>
	<lastBuildDate>Fri, 05 Feb 2010 18:03:08 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>Facebook&#8217;s Beacon Flashes On and Off</title>
		<link>http://www.insightbuzz.com/2007/12/07/facebooks-beacon-flashes-on-and-off/</link>
		<comments>http://www.insightbuzz.com/2007/12/07/facebooks-beacon-flashes-on-and-off/#comments</comments>
		<pubDate>Fri, 07 Dec 2007 12:50:00 +0000</pubDate>
		<dc:creator>Paul M. Banas</dc:creator>
				<category><![CDATA[Advertising]]></category>
		<category><![CDATA[Public Relations]]></category>

		<guid isPermaLink="false">http://www.insightbuzz.com/2007/12/07/facebooks-beacon-flashes-on-and-off/</guid>
		<description><![CDATA[Lost in all the blog coverage of Facebook&#8217;s Beacon saga, was how the whole series of events emphasized the speed at which a company in the digital space can make a mistake and then adjust course in the face of a blizzard of bad press. If this had happened in traditional media, the timeline between [...]]]></description>
			<content:encoded><![CDATA[<p>Lost in all the blog coverage of <a href="http://www.nytimes.com/2007/11/30/technology/30face.html?_r=1&amp;oref=slogin" target="_blank">Facebook&#8217;s Beacon saga</a>, was how the whole series of events emphasized the speed at which a company in the digital space can make a mistake and then adjust course in the face of a blizzard of bad press.</p>
<p>If this had happened in traditional media, the timeline between the announcement, the groundswell of bad PR, Facebook&#8217;s realizing they had a problem, and action on their part to fix it, would have probably covered months.  In this case, Beacon was announced and gone in less than 30 days.</p>
<ul>
<li>On November 6th, Facebook <a href="http://www.readwriteweb.com/archives/facebook_unveils_ad_strategy.php" target="_blank">announces the Beacon system</a> to the broader world.</li>
<li>Within two weeks, <a href="http://www.moveon.org/" target="_blank">Moveon.org</a> launches a campaign against the new system, citing privacy concerns.  Within another two weeks, over 50,000 people had joined the anti-Beacon Facebook group.</li>
<li>On December 5th, Facebook CEO Mark Zuckerberg <a href="http://www.techcrunch.com/2007/12/05/zuckerberg-saves-face-apologies-for-beacon/" target="_blank">apologizes and announces</a> substantial changes to the Beacon program, moving it from an opt out program to an opt in one, effectively killing it.</li>
</ul>
<p>Flash on, Flash off.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.insightbuzz.com/2007/12/07/facebooks-beacon-flashes-on-and-off/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

