<?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>refresherate.com &#187; Social Media</title>
	<atom:link href="http://www.refresherate.com/category/social-media/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.refresherate.com</link>
	<description>An invigorating splash of web geek goodness.</description>
	<lastBuildDate>Fri, 06 Aug 2010 19:13:01 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Holding a Twitter Contest: Lessons Learned</title>
		<link>http://www.refresherate.com/2010/01/11/holding-a-twitter-contest-lessons-learned/</link>
		<comments>http://www.refresherate.com/2010/01/11/holding-a-twitter-contest-lessons-learned/#comments</comments>
		<pubDate>Tue, 12 Jan 2010 04:30:23 +0000</pubDate>
		<dc:creator>Sheldon Finlay</dc:creator>
				<category><![CDATA[Social Media]]></category>

		<guid isPermaLink="false">http://www.refresherate.com/?p=211</guid>
		<description><![CDATA[I recently held a Twitter contest for a popular how to knit web site and while the contest was good, I did learn some things along the way which I would like to share. Make your contest short &#8211; Twitter buzz is pretty short-lived. Attention spans wane. One week is the maximum I&#8217;d recommend running [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignright size-full wp-image-212" title="twitter_logo_header" src="http://www.refresherate.com/wp-content/uploads/2010/01/twitter_logo_header.png" alt="twitter_logo_header" width="155" height="36" />I recently held a Twitter contest for a popular <a href="http://www.knittinghelp.com">how to knit</a> web site and while the contest was good, I did learn some things along the way which I would like to share.</p>
<ol>
<li><strong>Make your contest short</strong> &#8211; Twitter buzz is pretty short-lived. Attention spans wane. One week is the maximum I&#8217;d recommend running a contest, unless you think your contest is so exciting it will sustain a longer level of excitement. Your contest will most likely peak after a day or two. If you are giving away a MacBook or Canon 5D, you contest might be an exception. If you are giving away T-Shirts and bumper stickers, stick to a few days.</li>
<li><strong>Have multiple prizes</strong> &#8211; They don&#8217;t all have to be grand prizes. Maybe a handful of consolation prizes, free accounts, t-shirts, whatever. The multiple prizes will appeal to folks and make them more likely to jump into your contest since they have a greater chance to win something cool.</li>
<li><strong>Have people tweet a  message </strong>- Create a concise message which advertises your Twitter contest and make it a requirement that folks tweet it. Include a link (shortened of course) to the contest so others will be able to find your contest and join in.</li>
<li><strong>Have people follow you</strong> &#8211; You want to get followers don&#8217;t you? This should be a no-brainer.</li>
<li><strong>Don&#8217;t post about your contest like a manic squirrel</strong> &#8211; People will get tired of you if you are promoting your contest every hour. Find creative ways to give updates on your contest which also double as promotion. For example &#8220;Wow, we have had 1,200 people sign up for our contest. If you haven&#8217;t signed up there is still time *link*&#8221;. Done re-use the same line either, people will catch on.</li>
<li><strong>Use a hashtag</strong> &#8211; Add a hashtag to your contest message. You want to choose something fairly unique, so go off to <a href="http://search.twitter.com">search.twitter.com</a> and search to make sure it&#8217;s not already being used.</li>
<li><strong>Harvest your contest entrants </strong>- You will want to collect your contest entrants and not rely on search.twitter.com to store them for you. Search.twitter.com only goes back about a week and isn&#8217;t always reliable. If you are not saving your entrants in some way, you will likely lose some of them. Disenfranchising your contestants isn&#8217;t cool man.</li>
<li><strong>Create a script to query Search.twitter.com</strong> &#8211; I created a small <a href="http://ruby-lang.org">Ruby</a> script to regularly query the search.twitter.com and stick the entrants usernames a database. This way I always ensure I had a list of all contest entries. The script I created took advantage of the <a href="http://github.com/jnunemaker/twitter">Twitter gem </a>and would search for the hashtag and then look to make sure the tweet matched the contest message. The more you automate, the better.</li>
<li><strong>Don&#8217;t encourage re-Tweets</strong> &#8211; This is against Twitter&#8217;s <a href="http://help.twitter.com/forums/26810/entries/68877">contest guidelines</a> and will make Twitter mad and possible show the fail whale. For our contest we just did one entry per twitter user. Some people retweeted and that&#8217;s fine. But don&#8217;t make it a &#8220;whomever tweets this the most wins&#8221; contest.</li>
<li><strong>Follow up quickly with winners</strong> &#8211; Announce and congratulate them on Twitter, post them on your site, and contact them by DM as soon as the contest has ended. Don&#8217;t leave your contestants in the dark.</li>
<li><strong>Be prepared for a follower bounce back</strong> &#8211; Some of your followers who joined for the contest will abandon you as soon as they find out they didn&#8217;t win. It&#8217;s ok, they were not really into you, they just wanted to win free schwag. You are better off. Get over it already.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.refresherate.com/2010/01/11/holding-a-twitter-contest-lessons-learned/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
