<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>Omniture: Industry Insights » Lily Chiu</title>
	
	<link>http://blogs.omniture.com</link>
	<description>Thought leaders share insights on the direction of web analytics and online marketing.</description>
	<pubDate>Wed, 11 Nov 2009 22:47:49 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/omniture/blogs/author/lchiu" type="application/rss+xml" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><item>
		<title>Day 1: I Just Got a Testing Platform. Now What?</title>
		<link>http://feedproxy.google.com/~r/omniture/blogs/author/lchiu/~3/8u1synYbPCw/</link>
		<comments>http://blogs.omniture.com/2009/03/11/day-1-i-just-got-a-testing-platform-now-what/#comments</comments>
		<pubDate>Thu, 12 Mar 2009 01:25:57 +0000</pubDate>
		<dc:creator>Lily Chiu</dc:creator>
		
		<category><![CDATA[Testing and Targeting]]></category>

		<guid isPermaLink="false">http://blogs.omniture.com/?p=206</guid>
		<description><![CDATA[Take a deep breath. Before you start thinking about the implementation and what you can or cannot do with the platform, begin with your data.  Look for pages with the highest bounce rate, steps in your funnel with the greatest fallout, landing pages with the lowest conversion rate.  These should be red flags [...]]]></description>
			<content:encoded><![CDATA[<p>Take a deep breath. Before you start thinking about the implementation and what you can or cannot do with the platform, begin with your data.  Look for pages with the highest bounce rate, steps in your funnel with the greatest fallout, landing pages with the lowest conversion rate.  These should be red flags helping you prioritize where to start testing first.  For example, in the report below, check out the highlighted conversion rate that&#8217;s significantly lower than the other search terms:</p>
<p><img src="http://assets.omniture.com/en/images/blogs/lily_post_15_image_first.png" alt="" /></p>
<p>Get key stakeholders who are on board with testing in a room together and throw out hypotheses you draw from the data, along with the ideas you&#8217;ve debated in circles forever without ever coming to a decisive answer.  You can never underestimate how political testing can be in an organization, so make sure you don&#8217;t have naysayers in the room on day 1.  They&#8217;ll come into play later on :)</p>
<p>Once you&#8217;ve got all the ideas on the wall, it&#8217;s time to start slicing!  Let&#8217;s say that the list below is what we have to work with.</p>
<p><img src="http://assets.omniture.com/en/images/blogs/lily_post15_image2.jpg" alt="" /></p>
<p>Here are some key questions you want to ask yourself when evaluating the quality of an idea:</p>
<p><strong>1) What is my hypothesis?</strong> - If you don&#8217;t have a hypothesis, it&#8217;s game over.</p>
<p><strong>2) What are my goals?</strong> - Sounds like a no brainer, but I can&#8217;t tell you how many times I&#8217;ve had clients want to try testing colors or layouts just for the heck of it.  You must have a clear goal that you are working towards!  It can be more than one goal, such as locating a dealer or requesting a quote, in the case of an automaker, but just make sure you&#8217;ve got it clear in your mind so your design aligns with it.</p>
<p><img class="alignleft" style="5px;5px;5px;5px;" src="http://assets.omniture.com/en/images/blogs/lily_post15_image4.jpg" alt="" width="240" height="240" align="left" /><strong>3) How much traffic do I get?</strong> - This one&#8217;s important.  If you only get 50 conversions a day, you will never be able to run a test with 100 different variations.  The amount of time it would take to run that test would make it useless.  We&#8217;re talking months, if not years.  To highlight the point: at 50 conversions a day, half of the variations tested wouldn&#8217;t even have a single conversion after day 1.</p>
<p><strong>4) Which segments do I want to drill into?</strong> This one&#8217;s directly related to the amount of traffic you get.  Because let&#8217;s say you wanted to run a test with 100 different variations, AND you have 4 key segments you&#8217;re interested in, such as paid search, organic search, email, and affiliates, well now you are most definitely talking about a test that will take over a year.  The point is not that you can&#8217;t technically run a test for that long, but as an online marketer competing against other agile marketers, what would be the point?</p>
<p><strong>5) What will I learn if the alternative is the winner?</strong> It&#8217;s always great to find a winning alternative in <img class="alignright" style="10px;" src="http://assets.omniture.com/en/images/blogs/lily_post15_image5.jpg" alt="" align="right" />a test. But if you just grab 20 different call-to-actions you found on the internet, and It turns out the one from T-Mobile is the winner, what did you learn?  Maybe you found that magenta really does rock, but maybe you just stumbled your way onto a winner.  The upside of that discovery is nice, but how do you actually build on that learning to evolve your marketing practice?</p>
<p><strong>6) What will I learn if there is no winner?</strong> The dreaded lack of statistical confidence…dum dum dum. This one&#8217;s going to hurt, no doubt about it.  But there are ways to find grace in this result.  The first is to make sure you had great answers to all of the questions above.  Oh, offering a 20% discount on subscription didn&#8217;t increase overall revenue?  Well, now we know that we don&#8217;t need to cut our price and pricing isn&#8217;t as impactful as we expected. Great, let&#8217;s move on!  Or how about those segments that we set up?  If you drill down, you may find that those Mac users really behaved differently than the Windows users, resulting in a cancel-out effect at the top.  Now we&#8217;ve got 2 separate winners, and more learnings to build upon!</p>
<p>Once you&#8217;ve asked yourself these questions and pared down your ideas list, we now need to prioritize what goes first.  I like to calculate a score because it forces people to emotionally detach from their favorites.</p>
<p>There are two factors you want to consider when rating a potential test idea:</p>
<p><img class="alignleft" style="20px;" src="http://assets.omniture.com/en/images/blogs/lily_post_15_image6.png" alt="" width="270" height="179" align="left" /><strong>1) How difficult will this be to implement (both technically and politically)?</strong> Again, you cannot underestimate the political impact of a test idea.  For example, you just want to test different treatments of women&#8217;s clothing on the homepage.  That shouldn&#8217;t be a problem, right?  Well, how do the merchandisers for accessories and children&#8217;s clothing feel about that?  Or what about changing the link to your sign-up form from small-font text to a big flashing button?  The homepage design team might have a problem with that even if it&#8217;s technically super-easy to implement.  I would recommend saving that test for a later date once the homepage design team has gotten a chance to see the extent of your testing prowess.</p>
<p><strong>2) What is the potential ROI (whether in learnings and/or conversion)?</strong> It&#8217;s hard to estimate the ROI from a test.  If it were easy, we probably wouldn&#8217;t need to test.  But there are still ways to get closer to a good estimate.  For example, testing a page that has a low conversion rate but only 100 visitors a day might be an interesting opportunity to learn, but the resulting revenue bump is probably not going to be impactful.  Testing the first page of your checkout funnel could be huge in potential ROI though, even if you&#8217;re just talking about 3% lift in revenue per visitor or total orders.</p>
<p>Here&#8217;s an example of how you might rate the previous list of ideas.</p>
<p><img src="http://omniture.secure.miisolutions.net/omniture/20090309_ratedtables.jpg" alt="" /></p>
<p>I think the two factors are actually pretty equal in weight, so I then go ahead and do a straight sum of both to get my idea score.  I&#8217;ve color-coded and sorted the different tiers of scores here.</p>
<p><img src="http://assets.omniture.com/en/images/blogs/lily_post15_image1.jpg" alt="" width="528" height="278" /></p>
<p>A lower score doesn&#8217;t mean the idea falls off the board, by any means.  It just means that you allow for more time to get that test idea implemented.  However, a lower score plus a low value/ROI rating should be grounds for being removed. Hopefully you have a platform that empowers you to run the easy stuff faster and with more control, meaning you&#8217;re able to leave IT alone to deal with the hard stuff.  We know that makes everybody happier!</p>
<p>The last step is constructing the testing roadmap.  Taking that list of ideas we&#8217;ve put together, we can now create a much more intelligent roadmap that takes into account the strengths and constraints of your organization, infrastructure and platform.  Behold!</p>
<p><img src="http://omniture.secure.miisolutions.net/omniture/20090309_testingtimeline.jpg" alt="" /></p>
<p>This testing roadmap will now inform how you implement your platform and build a knowledge base of learnings and best practices.  <img class="alignright" style="20px;" src="http://assets.omniture.com/en/images/blogs/lily_post15_image10.jpg" align="right" width="150" alt="" />  One piece of advice though, is to stay flexible.  This roadmap can and should be fluid, based on what you see in the test results.  If you find that testing call-to-actions is yielding significant lift early on, it could be worthwhile to keep digging in that direction for more conversion nuggets.  Similarly, if you find that your early attempts at shortening form length really aren&#8217;t doing much, you might want to push other tests in that vein further out in the timeline.  Ultimately, testing is about listening to your customers, even when they don&#8217;t know they&#8217;re being asked the question.  Don&#8217;t forget to remain open enough to truly hear their answers!</p>
<p>If you found this post helpful, re-tweet it with the link or text below!  My next post will cover Day 7: We&#8217;ve Got Our Testing Roadmap. Now What?</p>
<p><a href="http://twitter.com/home/?status=RT+%40sflily+Day+1%3A+I+Just+Got+a+Testing+Platform.+Now+What%3F+http%3A%2F%2Fis.gd%2FmZuf+%23omniture">RT @sflily Day 1: I Just Got a Testing Platform. Now What? http://is.gd/mZuf #omniture</a></p>
<p>Photo Credits:<br />
<a href="http://www.flickr.com/photos/martyn/402688339/">http://www.flickr.com/photos/martyn/402688339/</a><br />
<a href="http://www.flickr.com/photos/schoolstreet/163727710/">http://www.flickr.com/photos/schoolstreet/163727710/</a><br />
<a href="http://www.flickr.com/photos/tomchurchill/335300686/">http://www.flickr.com/photos/tomchurchill/335300686/</a></p>
<img src="http://feeds.feedburner.com/~r/omniture/blogs/author/lchiu/~4/8u1synYbPCw" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blogs.omniture.com/2009/03/11/day-1-i-just-got-a-testing-platform-now-what/feed/</wfw:commentRss>
		<feedburner:origLink>http://blogs.omniture.com/2009/03/11/day-1-i-just-got-a-testing-platform-now-what/</feedburner:origLink></item>
		<item>
		<title>Testing Social Media Traffic</title>
		<link>http://feedproxy.google.com/~r/omniture/blogs/author/lchiu/~3/pGdxsdyteJs/</link>
		<comments>http://blogs.omniture.com/2009/02/10/testing-social-media-traffic/#comments</comments>
		<pubDate>Wed, 11 Feb 2009 00:06:18 +0000</pubDate>
		<dc:creator>Lily Chiu</dc:creator>
		
		<category><![CDATA[Testing and Targeting]]></category>

		<guid isPermaLink="false">http://blogs.omniture.com/?p=190</guid>
		<description><![CDATA[I have a confession to make: I&#8217;m not a Twitterholic. Not even close. I could shut TweetDeck down for a few days and continue stumbling blindly through my life without the tweets of friends and strangers streaming by out of the corner of my eye. But I digress.
Twitter has taught me there is a serious [...]]]></description>
			<content:encoded><![CDATA[<p>I have a confession to make: I&#8217;m not a Twitterholic. Not even close. I could shut TweetDeck down for a few days and continue stumbling blindly through my life without the tweets of friends and strangers streaming by out of the corner of my eye. But I digress.</p>
<p>Twitter has taught me there is a serious segment out there that feels differently. They share the things they watch, read, and buy, and they can start a movement very quickly. For evidence, just read sugarrae&#8217;s <a href="http://www.sugarrae.com/dont-need-seo-rank-google/">excellent post</a> about launching tweetwasters. So even if you don&#8217;t have much traffic coming in from tweets, blogs, and shares today, it doesn&#8217;t mean you might not have a spike tomorrow. Here are some of the things I would set up and test to stay ahead of the game.</p>
<p><strong>Provide Your Own Shortened URLs</strong></p>
<p>The toughest part about testing social media traffic is detecting where the traffic came from. Most URL-shortening services use a 301 redirect when taking visitors to their destination, and that type of redirect cleans up after itself. Unfortunately for us, that means we can&#8217;t even detect they came from a shortened URL.</p>
<p>The best solution I can think of is to provide your own shortened URL on the page and make it as easy as possible for your visitors to use it.  There are a couple ways to make sure you can track people using your URL.  You can use one of the URL-shortening services that provides tracking (<a href="http://www.briansolis.com/2008/12/saying-more-with-less-directory-of.html">good list here from Brian Solis</a>), or you can append a URL parameter to the URL that allows you to track this segment within your analytics.  For example, instead of shortening the URL &#8220;<a href="http://www.omniture.com">http://www.omniture.com</a>&#8220;, I would shorten &#8220;<a href="http://www.omniture.com/?src=scl">http://www.omniture.com/?src=scl</a>&#8221; instead.</p>
<p>If you&#8217;re worried about how that might impact your visitors, test it!  In addition to the normal conversion event you might assign to a test, I would also look at the incremental traffic received from providing the URL.</p>
<p><span style="text-decoration: underline;"><strong>Sample Test Design</strong><br />
</span>Audience:<br />
- General<br />
Element(s):<br />
- Hide or Show Shortened URL<br />
Conversion(s):<br />
- Standard conversion event (e.g. add to cart, page views, orders)<br />
- Traffic coming from shortened URL<br />
Segments:<br />
- All Visitors<br />
- Visitors coming from shortened URL (src=scl)</p>
<p><strong>Here&#8217;s a screenshot of how that segment would be set up in Test&amp;Target:</strong></p>
<p><img src="http://assets.omniture.com/en/images/blogs/lily_post_14_image1.png" alt="" width="904" height="354" /></p>
<p><img src="http://assets.omniture.com/en/images/blogs.PNG" alt="" /></p>
<p><strong>Formulate Hypotheses</strong></p>
<p>Let&#8217;s assume that you can now track the traffic coming from different outlets like blogs, Twitter, Digg, etc.  Based on that, I would try to keep the social ball rolling with the following ideas:</p>
<p>Test whether displaying the ability to share more prominently is effective in increasing traffic.  I would imagine that people who followed shared links are much more likely to return the favor.</p>
<p>Does your brand have a presence on Twitter yet? If so, test displaying your most recent tweets in a Twitterstream sidebar.</p>
<p>Do you have product reviews on your site?  Jump on the social bandwagon and make sure they&#8217;re front and center. Test defaulting to reviews instead of standard product detail copy.</p>
<p>Know which site the traffic is coming from?  Reinforce it and serve related content.  For example, back in our Offermatica days, MarketingSherpa had a complimentary article about Offermatica so we created a targeted homepage campaign for that specific segment of traffic coming from the article.   Through that campaign, we dedicated real estate that highlighted not only the MarketingSherpa mention but also other related articles in the press.</p>
<p><strong>Let&#8217;s Talk</strong></p>
<p>Hopefully this post has got you thinking about how you can better leverage the social media traffic coming to your site.  For those of you who will be attending our customer Summit in a couple weeks, I&#8217;d love to talk more in person about your plans for optimization in 2009!  I&#8217;ll be presenting with Experian on using Test&amp;Target iteratively to reveal valuable customer insights. <a href="http://twitter.com/brianwatkins">Brian Watkins</a> will also be presenting with Forrester&#8217;s <a href="http://twitter.com/jowyang">Jeremiah Owyang</a> and Comcast&#8217;s <a href="http://twitter.com/comcastcares">Frank Eliason</a> in a session called &#8220;MyFaceLinkSpaceTwitBook: Boosting Conversion with Social Networks&#8221;. Jeremiah is a thought leader in the space and I don&#8217;t think it&#8217;d be an understatement to say that &#8220;Comcast Frank&#8221; has pioneered the emerging corporate brand presence on Twitter.  Oh yeah, and feel free to tweet me at <a href="http://twitter.com/sflily">@sflily</a> with your thoughts as well. I aspire to call myself a Twitterholic someday. Hey, a girl can dream…</p>
<p>For more information, check out this <a href="http://www.getelastic.com/ecommerce-twitter-tools/">great post</a> by Linda Bustos on tracking Twitter links.</p>
<img src="http://feeds.feedburner.com/~r/omniture/blogs/author/lchiu/~4/pGdxsdyteJs" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blogs.omniture.com/2009/02/10/testing-social-media-traffic/feed/</wfw:commentRss>
		<feedburner:origLink>http://blogs.omniture.com/2009/02/10/testing-social-media-traffic/</feedburner:origLink></item>
		<item>
		<title>My 2009 Optimization Wish List</title>
		<link>http://feedproxy.google.com/~r/omniture/blogs/author/lchiu/~3/fqGiA4gHOIY/</link>
		<comments>http://blogs.omniture.com/2008/12/30/my-2009-optimization-wish-list/#comments</comments>
		<pubDate>Tue, 30 Dec 2008 15:54:48 +0000</pubDate>
		<dc:creator>Lily Chiu</dc:creator>
		
		<category><![CDATA[Testing and Targeting]]></category>

		<category><![CDATA[optimization]]></category>

		<guid isPermaLink="false">http://blogs.omniture.com/?p=173</guid>
		<description><![CDATA[With 2009 predictions whizzing around the web, I decided to write instead about what I&#8217;m wishing for in 2009. I&#8217;m hoping for an &#8220;if you build it, he will come&#8221; moment. Without further ado…
1) Agencies Get On Board
Aside from the handful of agencies that specialize in testing and conversion optimization, I&#8217;ve seen far less progress [...]]]></description>
			<content:encoded><![CDATA[<p>With 2009 predictions whizzing around the web, I decided to write instead about what I&#8217;m wishing for in 2009. I&#8217;m hoping for an &#8220;if you build it, he will come&#8221; moment. Without further ado…</p>
<p><strong>1) Agencies Get On Board</strong></p>
<p>Aside from the handful of agencies that specialize in testing and conversion optimization, I&#8217;ve seen far less progress than I expected this year. To do a sanity check, I googled &#8220;[agency name] multivariate&#8221; on the top 4 digital agencies of 2007 from AdAge. Here&#8217;s what I found:</p>
<p><img src="http://assets.omniture.com/en/images/blogs/lily_post_13_image1.jpg" alt="" /></p>
<p><img src="http://assets.omniture.com/en/images/blogs/lily_post_13_image2.jpg" alt="" /></p>
<p><img src="http://assets.omniture.com/en/images/blogs/lily_post_13_image3.jpg" alt="" /></p>
<p><img src="http://assets.omniture.com/en/images/blogs/lily_post_13_image4.jpg" alt="" /></p>
<p>Avenue A | Razorfish is the only search that yields any substantial result, and that is to a partner&#8217;s press release focusing on the platform rather than their own in-house expertise. Contrast that with searching for &#8220;[agency name] creative&#8221;, and you&#8217;ll find that Digitas and Ogilvy rank #1 in SEO and Avenue A | Razorfish at #3.</p>
<p>I know that part of the problem is that agencies have a tough time convincing clients to test. But I suspect that agencies are also not yet accountable for testing, so why deliver some options that may quantifiably fail when you can deliver a single option that unquantifiably wins? The latter requires less level-of-effort and chance of hassle. Unfortunately it also has less upside for the customer. Hopefully agencies will consider the significance of providing more value to their customers, and what that may yield for them long-term.</p>
<p>My reason for wanting agencies to get on board is selfish. I believe that agencies (at their best) are the strategic partners of customers, and they can help prove the value of testing. But it feels a bit like the chicken-and-the-egg. Agencies aren&#8217;t compelled to actively bring testing skills and experience in-house without clients asking for it, and clients may not be educated enough to take on testing without an agency resource!</p>
<p><strong>2) Offsite + Onsite = 1 Visitor Experience</strong></p>
<p>I&#8217;ve definitely seen great strides already taken this year in trying to treat a visitor&#8217;s path through offsite and onsite as one cohesive experience. Some of our customers are doing really interesting projects involving the testing of retargeted ads out on 3rd-party sites and building a single profile that can be extended and reinforced at every online touch point. I&#8217;m excited to see how that plays out in 2009.</p>
<p>However, I&#8217;ve also seen a lot of poorly executed landing page experiences that show there&#8217;s no discussion going on between those in charge of acquisition and those in charge of the site. If there is any confusion around where to begin testing, I&#8217;d highly recommend starting there. Landing pages are typically easier to change and tag, and transforming a post-click experience from general and 80% irrelevant to targeted and 100% relevant usually yields great lift!</p>
<p><strong>3) Multivariate Testing (MVT) Becomes Another Tool in the Toolbox</strong></p>
<p>There&#8217;s no question that <a href="http://www.omniture.com/en/products/conversion/testandtarget" target="_blank">multivariate testing </a>is an incredibly powerful tool. But it&#8217;s certainly not the only tool <img class="alignleft" style="float: left;" src="http://assets.omniture.com/en/images/blogs/lily_post_13_image5.jpg" alt="" width="535" height="192" />you need or have to increase conversion on your site. I think of it as the hammer in the saying, &#8220;when all you have is a hammer, everything looks like a nail.&#8221; There are many efforts that <a href="http://www.omniture.com/en/products/conversion/testandtarget" target="_blank">multivariate testing</a> is not the best tool for, including massive functionality changes (e.g. 5-page checkout vs. 1-page checkout) and automated <a href="http://www.omniture.com/en/products/conversion/testandtarget" target="_blank">behavioral targeting</a>. The problem with looking at MVT as the all-purpose cleaner is that it limits your vision to consider other types of tests, and it also reinforces a fragmented marketing division. I can&#8217;t count how many meetings I&#8217;ve been to where the catalyst is an RFP for MVT. Once we start talking about the site&#8217;s initiatives though, we begin to understand that there is also interest around segmentation and targeting. However, that&#8217;s a separate project manager and a separate RFP, and nobody is interested in getting together in the same room.</p>
<p><strong>4) Targeting Belongs in the Same Toolbox</strong></p>
<p>Targeting for the sake of targeting is not always effective. I have seen numerous cases where the first attempt strikes out. Sometimes people don&#8217;t want to see their first name read back to them, but they do like seeing their search terms repeated. Others like to see an offer reinforcing the deal they saw in the ad, but they may not want to see the same exact image. Without testing, you&#8217;re still not making data-driven decisions. At best, you&#8217;re making more educated guesses.</p>
<p><strong>5) Web Optimization Collaboration Takes Off</strong></p>
<p>Are you sensing a trend here? : I want more collaboration between acquisition marketers and site marketers, companies and agencies, vendors and companies! I think everybody wins when we share more of our testing experience and I&#8217;m convinced there has to be a way to do it without giving up competitive intelligence. So far the <a href="http://groups.google.com/group/weboptimization">weboptimization group</a> has had some good discussion around getting testing buy-in, and some very spicy discussion around vendor comparisons. Tell me how you think a forum should be constructed to be most beneficial, and then let&#8217;s work together to make it a reality.</p>
<p><strong>6) Succeed Often and Fail Fast</strong><img class="alignright" style="float: right;" src="http://assets.omniture.com/en/images/blogs/lily_post_13_image6.jpg" alt="" width="240" height="159" /></p>
<p>This one&#8217;s a little off the web optimization rails, but I wish President Obama all the best in making 2009 a year of recovery and successes. I don&#8217;t think it&#8217;s possible to not fail, especially given these tumultuous and uncertain times, so I&#8217;d just like to encourage him and all the rest of us to fail fast and keep on truckin&#8217;!</p>
<p>Happy New Year!</p>
<p><strong>Photo credits:<br />
</strong><a href="http://www.flickr.com/photos/jolienvallins/1505871497/">http://www.flickr.com/photos/jolienvallins/1505871497/</a><br />
<a href="http://www.flickr.com/photos/down_under_images/679400938/">http://www.flickr.com/photos/down_under_images/679400938/</a></p>
<img src="http://feeds.feedburner.com/~r/omniture/blogs/author/lchiu/~4/fqGiA4gHOIY" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blogs.omniture.com/2008/12/30/my-2009-optimization-wish-list/feed/</wfw:commentRss>
		<feedburner:origLink>http://blogs.omniture.com/2008/12/30/my-2009-optimization-wish-list/</feedburner:origLink></item>
		<item>
		<title>Who Owns Optimization?</title>
		<link>http://feedproxy.google.com/~r/omniture/blogs/author/lchiu/~3/Tacetz7o990/</link>
		<comments>http://blogs.omniture.com/2008/12/09/who-owns-optimization/#comments</comments>
		<pubDate>Tue, 09 Dec 2008 22:00:21 +0000</pubDate>
		<dc:creator>Lily Chiu</dc:creator>
		
		<category><![CDATA[Testing and Targeting]]></category>

		<category><![CDATA[agencies]]></category>

		<category><![CDATA[optimization]]></category>

		<guid isPermaLink="false">http://blogs.omniture.com/?p=166</guid>
		<description><![CDATA[I&#8217;ve been struggling with this question a lot lately as I talk to companies trying to figure out how to organize internally for testing.  Some companies want to own testing and start running from day one, while others want to ramp up slowly with a few resources working part-time on it.  Some are [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve been struggling with this question a lot lately as I talk to companies trying to figure out how to organize internally for testing.  Some companies want to own testing and start running from day one, while others want to ramp up slowly with a few resources working part-time on it.  Some are content to run just a few tests a year through IT, and still others want to outsource the whole operation to a vendor or agency.</p>
<p><strong>Should Testing Be Outsourced?</strong></p>
<p><img class="alignleft" style="float: left;" src="http://assets.omniture.com/en/images/blogs/lily_post_12_image1.jpg" alt="" width="240" height="180" />That last segment is the one I grapple with the most.  I don&#8217;t think the question is whether you can outsource testing and optimization, but whether you should.  For any company serious about their online channel, I believe that their marketers should already be thinking every day about how to improve the site and all acquisition efforts leading to the site.  Those ideas should be the fuel powering the optimization engine, so what would make a company want to turn that over to somebody else to manage?  Does that mean there&#8217;s no fuel in-house, or that the fuel is bad grade?  If so, that seems to point to a larger problem for the company than just whether testing can be outsourced.</p>
<p>None of this is to say that I don&#8217;t believe in the value of vendors, consultants and agencies contributing to your optimization efforts.  I&#8217;ve seen many cases where 3rd-parties have helped produce fantastic results for their clients.  They bring their extensive experience with other companies and fresh insights to help marketers think about their decisions from a testing perspective.  But I&#8217;ve also seen companies slash those parties off the budget without thinking twice because nobody at the company actually cared about testing.  Here are the main reasons why I don&#8217;t think testing can be fully outsourced:</p>
<p><strong>1) No Testing Culture -</strong> There is a huge unquantifiable benefit to having a testing culture instilled at a company.  It means that people are more thoughtful and less careless because they are forced to make data-driven decisions.  It also means that they feel more empowered to have ideas because they will get to see them in action on the site.  <img class="alignright" style="float: right;" src="http://assets.omniture.com/en/images/blogs/lily_post_12_image2.jpg" alt="" width="240" height="180" />An employee who sees that he or she has made hundreds of thousands of dollars for their company through a great idea that got tested on the site will certainly be motivated and motivate others to produce more stellar results!</p>
<p><strong>2) Less Learnings -</strong> If a 3rd-party is managing a company&#8217;s testing efforts, then all the learnings that come out of that testing don&#8217;t usually make it back out to the rest of team, especially if those tests produce negative ROI.  They are still incredibly valuable though, as they can inform how designs should be planned moving forward.  Imagine if an agency tests a big hero image against several small product images and finds one much more compelling than the other.  That could change how other marketing efforts such as site redesigns and direct mail pieces are designed, but only if that information is circulated.</p>
<p><strong>3) Easily Removed -</strong> As I said before, divorcing optimization from the company makes it easily removable as a nice-to-have instead of a must-have.  This issue is not isolated to just outsourcing the operation though.  I&#8217;ve also seen it happen many times when there is only one person at a company managing testing.  That champion might be generating many testing successes, but once they leave, nobody knows how to run it or wants to take on extra work.  Beware of tribal knowledge!  The most successful testing companies maintain a knowledgebase so they can easily reference previous learnings and not be back at square 1 if a subject matter expert leaves.</p>
<p><strong>4) Less Collaboration -</strong> Testing forces <a href="http://blogs.omniture.com/2008/12/04/it-takes-a-testing-village/">people to talk to each other</a>.  Disconnected landing page experiences are often a result of disconnected marketers.  An acquisition marketer is incented to get people to the landing page.  A site marketer is incented to drive people to conversion.  There needs to be some common objective that forces them to talk to each other.  I&#8217;ve also seen testing help align marketing and IT.  Instead of asking IT to simply put another tag on the page, marketing should explain what that tag&#8217;s purpose is and that it is a 1-time effort that will actually make their lives easier moving forward.  That helps IT understand the value of implementation and provides context for why it&#8217;s different from the other tags on the page.</p>
<p>Again, there are amazing resources out there to help you start testing successfully.  This post is not meant to detract from the immediate value they offer to jumpstart your optimization program.  Take advantage of the best practices learned by others and use the valuable strategy, advice and creativity they can provide.  But please, consider the benefits of using 3rd-parties to get your testing legs under you so that you can run on your own eventually!  Spread the love and bring people into the optimization process.  It&#8217;s more fun to have a running partner than to watch other people running laps around you.</p>
<p>Photos credits:<br />
<a href="http://www.flickr.com/photos/cindy47452/144655993/">http://www.flickr.com/photos/cindy47452/144655993/</a><br />
<a href="http://www.flickr.com/photos/avalonstar/163502744/">http://www.flickr.com/photos/avalonstar/163502744/</a></p>
<img src="http://feeds.feedburner.com/~r/omniture/blogs/author/lchiu/~4/Tacetz7o990" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blogs.omniture.com/2008/12/09/who-owns-optimization/feed/</wfw:commentRss>
		<feedburner:origLink>http://blogs.omniture.com/2008/12/09/who-owns-optimization/</feedburner:origLink></item>
		<item>
		<title>It Takes a Testing Village</title>
		<link>http://feedproxy.google.com/~r/omniture/blogs/author/lchiu/~3/G-x9lAIziOI/</link>
		<comments>http://blogs.omniture.com/2008/12/04/it-takes-a-testing-village/#comments</comments>
		<pubDate>Thu, 04 Dec 2008 16:17:27 +0000</pubDate>
		<dc:creator>Lily Chiu</dc:creator>
		
		<category><![CDATA[Testing and Targeting]]></category>

		<category><![CDATA[Web 2.0]]></category>

		<category><![CDATA[Google group]]></category>

		<category><![CDATA[web optimization]]></category>

		<guid isPermaLink="false">http://blogs.omniture.com/?p=161</guid>
		<description><![CDATA[
Testing is inherently collaborative.  It feeds off the behaviors of your visitors, but it also requires coordination among multiple groups for successful execution, including marketing, creative, and development.  Those who begin testing for the first time can truly benefit from the experiences of those who went before them.  So it begs the [...]]]></description>
			<content:encoded><![CDATA[<p><img src="http://assets.omniture.com/en/images/blogs/lily_post11_image1.jpg" alt="" /></p>
<p>Testing is inherently collaborative.  It feeds off the behaviors of your visitors, but it also requires coordination among multiple groups for successful execution, including marketing, creative, and development.  Those who begin testing for the first time can truly benefit from the experiences of those who went before them.  So it begs the question - why isn&#8217;t there more collaboration going on out there?</p>
<p>I could hypothesize that it&#8217;s because testing is still a competitive advantage at this point.  I certainly have some clients who feel this way and are very protective of their test designs and results. But I believe they&#8217;re in the minority.</p>
<p>The best conversation I&#8217;ve read about testing in the last year took place in Avinash Kaushik&#8217;s <a href="http://www.kaushik.net/avinash/2008/11/experiment-die-reasons-awesome-testing-ideas.html">blog</a> <a href="http://www.kaushik.net/avinash/2008/11/experiment-die-reasons-awesome-testing-ideas.html">comments</a> recently.  And while I love all the responses the post stirred up, I can&#8217;t help thinking that there&#8217;s got to be a better place to keep the conversation going.</p>
<p>Toward that end, I&#8217;ve created a <a href="http://groups.google.com/group/weboptimization">group focused on web optimization </a> where I&#8217;m hoping a lot more collaboration will take place.  This is a group for marketers interested in or currently testing and optimizing their sites today, regardless of platform or vendor.  I invite companies, agencies, and vendors to join the conversation.</p>
<p>I&#8217;ll most likely be creating discussions there around best practices and adding a lot of the questions I commonly get around testing.  Even though it&#8217;s fun to blog here, I get a little lonely banging around on my laptop alone.  I&#8217;d much rather get more feedback from those of you on the front line and I&#8217;m hoping we can all find ways to help each other as the testing community continues to grow.</p>
<p>I encourage anybody interested in testing and optimization to join the group today and participate!  Participation is key.</p>
<p>Group: <a href="http://groups.google.com/group/weboptimization">http://groups.google.com/group/weboptimization</a></p>
<img src="http://feeds.feedburner.com/~r/omniture/blogs/author/lchiu/~4/G-x9lAIziOI" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blogs.omniture.com/2008/12/04/it-takes-a-testing-village/feed/</wfw:commentRss>
		<feedburner:origLink>http://blogs.omniture.com/2008/12/04/it-takes-a-testing-village/</feedburner:origLink></item>
		<item>
		<title>Highlights from Pubcon: People are Testing, They’re Really Testing!</title>
		<link>http://feedproxy.google.com/~r/omniture/blogs/author/lchiu/~3/5XW1RIznd1c/</link>
		<comments>http://blogs.omniture.com/2008/11/17/highlights-from-pubcon-people-are-testing-theyre-really-testing/#comments</comments>
		<pubDate>Mon, 17 Nov 2008 20:19:36 +0000</pubDate>
		<dc:creator>Lily Chiu</dc:creator>
		
		<category><![CDATA[Testing and Targeting]]></category>

		<category><![CDATA[PubCon]]></category>

		<category><![CDATA[social media]]></category>

		<category><![CDATA[testing]]></category>

		<guid isPermaLink="false">http://blogs.omniture.com/?p=150</guid>
		<description><![CDATA[I spoke on a Landing Page Optimization panel at PubCon in Las Vegas last week, and the big learning I came away with is that more people are testing!  It was pretty exciting to poll the audience on who&#8217;s currently testing and see well over 50% of the room raise their hands.  Of [...]]]></description>
			<content:encoded><![CDATA[<p>I spoke on a Landing Page Optimization panel at <a href="http://www.pubcon.com/">PubCon</a> in Las Vegas last week, and the big learning I came away with is that more people are testing!  It was pretty exciting to poll the audience on who&#8217;s currently testing and see well over 50% of the room raise their hands.  Of those who weren&#8217;t, at least half raised their hands to the next question of who was planning on beginning within the next year.</p>
<p>That&#8217;s really encouraging news, especially in a downturn economy.  It shows that marketers are realizing that testing is one of the few strategies that truly enable you to do more with less.  Instead of having to invest linear amounts of money to acquire traffic, you can instead invest your ideas and hypotheses to increase conversion and revenue on your site.</p>
<p>I often find that the Q&amp;A is the most interesting and engaging part of a session.  It&#8217;s the closest we get to understanding what&#8217;s really on the minds of marketers today, and what they were hoping to learn from those of us on the panel.  One of the questions that stuck in my mind was, &#8220;What are good strategies for optimizing social media traffic going to landing pages?&#8221;</p>
<p>To be honest, I didn&#8217;t have a great answer because I haven&#8217;t seen many tests involving social media traffic.  Maybe it&#8217;s because we don&#8217;t have customers who are investing much in social media yet.  But I thought about it more on the plane, and then at home, and I think the answer lies in going back to the standard best practices of first defining what your success event will be, and then forming a hypothesis around how to improve it.</p>
<p>For example, if you told me that you ran a content site and wanted to increase page views, I&#8217;d say that those who come from social media probably have a higher likelihood of sharing content with friends.  My test idea might be to test promoting sharing links higher up on the page, or repeatedly throughout the article.  But if you told me that you ran a retail site and you wanted to increase orders, I might try to promote highly-rated products based on the hypothesis that social media visitors place a greater premium on the opinions of peers.</p>
<p>Another question I got was, &#8220;Okay, you talk a lot about testing, but how do I test on my site?  Do you sell a product?&#8221;  Yikes, the dreaded vendor pitch trap!  I have to admit there was a bit of spastic product naming as I tried to give a very neutral answer.  I struggle quite a bit with the balance of giving information and opinions without selling any specific platform, both in places like PubCon and here in this blog.  I know that you, as the reader, have come here knowing that it&#8217;s a corporate blog run by Omniture, but I also think that you&#8217;re more interested in learning about marketing principles and customer insights than about what we&#8217;re selling.  So I err on the side of avoiding the product conversation completely, to the detriment of those who are already customers.  Luckily, my very capable colleague, Brian Hawkins, has begun a <a href="http://blogs.omniture.com/author/bhawkins/">blog</a> recently about the ins and outs of Omniture Test&amp;Target, so I would direct readers there for specifics on how to implement many of the examples and case studies we show.</p>
<p>The last question I have is for you, the marketer who attends conferences like PubCon.  When you go to a session about landing page optimization, what are you hoping to hear?  Are you looking for tactical advice, or customer case studies, or market research findings?  Would you rather see a presentation that tells you about the latest marketing strategies and where we see the market going, or the one that lays out 10 easy tips to try on your site today?</p>
<img src="http://feeds.feedburner.com/~r/omniture/blogs/author/lchiu/~4/5XW1RIznd1c" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blogs.omniture.com/2008/11/17/highlights-from-pubcon-people-are-testing-theyre-really-testing/feed/</wfw:commentRss>
		<feedburner:origLink>http://blogs.omniture.com/2008/11/17/highlights-from-pubcon-people-are-testing-theyre-really-testing/</feedburner:origLink></item>
		<item>
		<title>Election 2008: Who’s Working on Relevancy and Engagement?</title>
		<link>http://feedproxy.google.com/~r/omniture/blogs/author/lchiu/~3/ZcE3faNM00U/</link>
		<comments>http://blogs.omniture.com/2008/10/23/election-2008-whos-working-on-relevancy-and-engagement/#comments</comments>
		<pubDate>Thu, 23 Oct 2008 18:24:26 +0000</pubDate>
		<dc:creator>Lily Chiu</dc:creator>
		
		<category><![CDATA[Testing and Targeting]]></category>

		<category><![CDATA[election]]></category>

		<category><![CDATA[engagement]]></category>

		<category><![CDATA[onsite experience]]></category>

		<guid isPermaLink="false">http://blogs.omniture.com/?p=146</guid>
		<description><![CDATA[There&#8217;s been a lot of talk about what the Obama and McCain campaigns are doing in both paid and organic search optimization, but not as much on what they do with that traffic once visitors land on the site.  Campaign sites pose a unique challenge because they have multiple goals for visitors who land [...]]]></description>
			<content:encoded><![CDATA[<p>There&#8217;s been a lot of talk about what the Obama and McCain campaigns are doing in both paid and organic search optimization, but not as much on what they do with that traffic once visitors land on the site.  Campaign sites pose a unique challenge because they have multiple goals for visitors who land from different sources with a wide range of intentions.</p>
<p><strong>One Site, Many Goals</strong></p>
<p>These are the 3 major objectives I think a campaign site has to accomplish:</p>
<p><strong>1) inform<br />
2) persuade<br />
3) solicit</strong></p>
<p>The problem is that not all visitors progress through each stage, nor do they follow them in any particular order.  It&#8217;s a bit of a chicken and the egg…and, uh, the cow problem. <img class="alignright" style="float: right;" src="http://assets.omniture.com/en/images/blogs/lily_post_9_image_1.jpg" alt="" width="210" height="101" /> Luckily, it&#8217;s also the perfect scenario to bring your acquisition marketers and site marketers together.  Your acquisition channels can help segment your visitors by goal and communicate that back to the site.  More on that later through real examples from the Obama and McCain campaigns…</p>
<p><strong>Time = Voters</strong></p>
<p><img class="alignleft" style="float: left;" src="http://assets.omniture.com/en/images/blogs/lily_post_9_image_2.jpg" alt="" width="169" height="156" />What I find interesting about political campaigns is the urgency that drives execution at a much faster pace than most companies out there can accomplish today.  I suspect that the marketing team behind each candidate ranks near the top for agility and speed because there simply is no other option.  The primary problem is not whether there has been enough budget and headcount allocated for 2009, it&#8217;s about who bid on the right keywords representing the issues voters are searching for today and who can react fastest to the latest event to hit the headlines.</p>
<p>As we&#8217;ve all seen over the last few months, advertising is one of the major vehicles driving a campaign&#8217;s messaging and branding.  It shows us which topics candidates are focusing on and which channels they are spending the most money on.  What&#8217;s sometimes missed, though, is what that advertising then tells them about us.  There are few advertisements that don&#8217;t ask you to do something in return, whether it&#8217;s donating on a website or joining a mailing list.  Below is a comparison of each campaign&#8217;s ad on the same day in the same location, along with the corresponding landing page.</p>
<p>The McCain campaign&#8217;s ad on Drudge Report:</p>
<p><img src="http://assets.omniture.com/en/images/blogs/lily_post_9_image_3.jpg" alt="" /></p>
<p>Ad&#8217;s Landing Page:</p>
<p><img src="http://assets.omniture.com/en/images/blogs/lily_post_9_image_4.jpg" alt="" /></p>
<p>Obama Campaign&#8217;s Ad on Drudge Report:</p>
<p><img src="http://assets.omniture.com/en/images/blogs/lily_post_9_image_6.jpg" alt="" /></p>
<p>Ad&#8217;s Landing Page:</p>
<p><img src="http://assets.omniture.com/en/images/blogs/lily_post_9_image_7.jpg" alt="" /></p>
<p>You&#8217;ll notice that there is a widget available to input information about your income so that you can calculate how much you could potentially save under the Obama/Biden tax plan.</p>
<p><strong>Connect the Offsite and Onsite Experience</strong></p>
<p>Could these two experiences be any more different?  McCain&#8217;s ad is a straightforward call-to-action to donate.  It focuses singularly on the &#8220;solicit&#8221; goal.  However, there are key elements of that ad that are lost once the visitor lands on the site.  For example, what does it mean to &#8220;Invest in Victory&#8221;?  Should we at least see that headline reinforced on the landing page, if not elaborated on with how individual contributions can help?</p>
<p>It&#8217;s also interesting to note that the call-to-action specifically uses $50 as the amount to contribute, but it is neither highlighted nor pre-selected once the form to donate is presented.  I would imagine that some market analysis led to the emphasis of $50 in the ad, so why not continue that through the experience by making the process to donate $50 just a little bit simpler.</p>
<p>In contrast, Obama&#8217;s ad is targeting voters based on the issue of taxes.  It takes the approach of focusing on the &#8220;inform&#8221; and &#8220;persuade&#8221; goals.  You&#8217;ll see that the landing page calculator asks for anonymous information and then returns an estimate of savings.  Here&#8217;s what the page looks like after filling out the calculator:</p>
<p><img src="http://assets.omniture.com/en/images/blogs/lily_post_9_image_8.jpg" alt="" /></p>
<p>Note that the calculator has changed into a form that now asks for my information to keep in touch.  We&#8217;re now moving into the next stage of solicitation.</p>
<p><strong>Engage the Visitor</strong></p>
<p>From a design, flow, and relevancy perspective, I think this ad to landing page experience is very well-executed.  Beyond that though, I think it&#8217;s also a clever way to get a lot of information about your visitors in a way that is not explicit.  Let&#8217;s take a closer look at what we learn as the visitor progresses through the ad and landing page.</p>
<p>After the visitor clicks on the ad:<br />
We can infer that this visitor is interested in learning more about taxes and saving money.</p>
<p>After the visitor fills out the calculator:<br />
At a minimum, we know the visitor&#8217;s annual income and filing status.  On top of that, we may know how many dependents they have, whether they are over 65, if they have child care expenses, if they are saving for retirement, the outstanding balance of their mortgage, and if they have college expenses.  That is A LOT of information when you look at it from a profile targeting and segmentation perspective.  Imagine how much more relevant and engaging you can make this visitor&#8217;s experience across multiple channels including display, email, and site by having this type of data.</p>
<p>After the visitor fills out the &#8220;Stay Informed&#8221; form:<br />
We now have the visitor&#8217;s email address and zip code to tie all the information together in the database.</p>
<p>To recap, here&#8217;s the wealth of information that the Obama campaign has in their database now after a visitor clicks one ad and fills out two short forms:</p>
<ul>
<li>email address</li>
<li>zip code</li>
<li>issue interest</li>
<li>income bracket</li>
<li>filing status</li>
<li>age*</li>
<li># of dependents*</li>
<li>mortgage balance*</li>
<li>saving for retirement*</li>
</ul>
<p><em>*optional field</em></p>
<p>Would you send a different email to the voter in a swing state making $40,000 a year vs. the voter in New York making $300,000 a year?</p>
<p><strong>These Principles Apply to More Than Politics</strong></p>
<p>The strategies employed here are not unique to politics.  They might just require a shift in how you approach your business and define the goals of your acquisition marketing efforts.</p>
<p>For example, let&#8217;s say you&#8217;re a retailer that sells HDTVs.  Instead of an ad promoting a specific model, maybe you show an ad that provides information on how to select the right HDTV for you.  The landing page then asks the visitor about their budget, preferred size, and other relevant parameters.  Maybe that then leads them to personalized search results, or you display another short form that enables them to receive alerts when an HDTV goes on sale within their budget.</p>
<p>Think about how you can make each touch point with your visitor more relevant and engaging so you can draw them through a cohesive experience that both leads them to the water and increases your bottom line. In other words, ask not what your visitor can do for you, but what you can do for your visitor.  And don&#8217;t forget to vote!</p>
<img src="http://feeds.feedburner.com/~r/omniture/blogs/author/lchiu/~4/ZcE3faNM00U" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blogs.omniture.com/2008/10/23/election-2008-whos-working-on-relevancy-and-engagement/feed/</wfw:commentRss>
		<feedburner:origLink>http://blogs.omniture.com/2008/10/23/election-2008-whos-working-on-relevancy-and-engagement/</feedburner:origLink></item>
		<item>
		<title>Building a Business Case for Optimization</title>
		<link>http://feedproxy.google.com/~r/omniture/blogs/author/lchiu/~3/dGY6ldlMo6s/</link>
		<comments>http://blogs.omniture.com/2008/10/17/building-a-business-case-for-testing/#comments</comments>
		<pubDate>Fri, 17 Oct 2008 21:40:06 +0000</pubDate>
		<dc:creator>Lily Chiu</dc:creator>
		
		<category><![CDATA[Testing and Targeting]]></category>

		<guid isPermaLink="false">http://blogs.omniture.com/?p=144</guid>
		<description><![CDATA[We have to go back to the basics.  I gave a seminar on Tuesday about optimization to a group of marketers in Los Angeles, and it really opened my eyes to the current state of online site marketing today.  While it was a great, interactive session, the slide that got the most nodding [...]]]></description>
			<content:encoded><![CDATA[<p>We have to go back to the basics.  I gave a <a href="http://events.omniture.com/register/seminars/us2008/index.html">seminar</a> on Tuesday about optimization to a group of marketers in Los Angeles, and it really opened my eyes to the current state of online site marketing today.  While it was a great, interactive session, the slide that got the most nodding heads was the one that listed the challenges marketers face with just getting content up on the site today.  Many people took notes when we talked about different testing ideas, ways in which you can break your audience up into impactful segments, and the successes that our customers have enjoyed themselves through using Test&amp;Target.  But the most telling point came when I asked people to raise their hand if they hadn&#8217;t started testing yet, but would be starting within the next year.  No one raised their hand.</p>
<p><strong>Hitting a Roadblock</strong></p>
<p>It was hard to get people to talk about the reasons why during our session, but I spoke to these marketers afterwards, and the overriding sense I got was that they were completely handcuffed and roadblocked by processes and politics.  No one felt like they actually owned the site they were supposed to be marketing on.  Changing content on the site, let alone testing it, felt like an insurmountable challenge.</p>
<p><img class="alignright" style="float: right;" src="http://assets.omniture.com/en/images/blogs/lily_post_8_image_1.jpg" alt="" width="314" height="210" /></p>
<p>I realized that I could show as many examples of bad landing page experiences, wasted opportunities for testing and targeting, and case study successes as I wanted, but the problem these marketers faced was not a lack of belief in testing -  it was the inability to sell this belief up the chain.  With that in mind, I want to help arm you with an arsenal of reasons why your company can&#8217;t afford to delay testing another year.</p>
<p><strong>1) Testing Drives Results</strong></p>
<p>ZeroDash1 conducted an independent <a href="http://www.zerodash1.com/ABMultivariateTestingLandscape.aspx">study</a> at the eMetrics show in San Francisco this year, and one of the key questions they asked was whether marketers who were testing thought it was worth it.  Take a look at the results.  (Note: this survey was not solicited by Omniture in any way)</p>
<p><img style="vertical-align: middle;" src="http://assets.omniture.com/en/images/blogs/lily_post_8_image_2.jpg" alt="" width="328" height="218" /></p>
<p><strong>92%</strong> saw positive ROI!  How many other initiatives can you say that about?  It also makes me really proud to point out that 54% of those who say they &#8220;can&#8217;t live without it&#8221; use Omniture Test&amp;Target.  As part of a company that has been evangelizing testing for the last 5 years, it&#8217;s incredibly rewarding to see affirmation of the original bet that Offermatica&#8217;s founders made - to make a product designed for marketers, not statisticians or IT.</p>
<p><strong>2) Optimizing On-Site Increases Off-site ROAS</strong></p>
<p>I recently surveyed the web to see the state of landing pages today.  What I found was that companies are still missing out on so many opportunities to increase relevancy and engagement on their sites.  I&#8217;m only going to show one example here, but it certainly reflects the majority of pages I visited.</p>
<p><img src="http://assets.omniture.com/en/images/blogs/lily_post_8_image_3.jpg" alt="" /></p>
<p>Note the ad at the top of the page.  It&#8217;s a timely ad considering we all have savings on the mind these days.  Here&#8217;s the page I landed on when I clicked through.</p>
<p><img src="http://assets.omniture.com/en/images/blogs/lily_post_8_image_4.jpg" alt="" /></p>
<p>Was that what you were expecting?  I was looking for more sale information, a preview of those thousands of items, the hundreds in savings.  Instead, I got sent to the lighting page.  Do I think that Design Within Reach&#8217;s marketing team thought the lighting page was the best place to send this traffic?  Nope.  I think the media marketers probably weren&#8217;t talking to the site marketers, and even if they were, the site marketers probably couldn&#8217;t change anything about the page or put up a new sale preview page in time.  This example represents a huge missed opportunity though.  Imagine the difference in bounce rate if a user had landed on a sale preview page instead.</p>
<p><strong>3) Hope is Not a Strategy</strong></p>
<p>In the same ZeroDash1 survey conducted at eMetrics, marketers were asked whether their pre-test hypotheses were always correct.  &#8220;100% of survey respondents admit that their pre test hypotheses are not always correct.&#8221;   100% means not one single person can say he or she has always been right.  Even though it sounds like a no-brainer, it means that anybody who is not testing today has been wrong at least once about a new idea or design that&#8217;s been pushed out to production.  Testing allows you to understand whether your ideas actually impact your success metrics and then make data-driven decisions instead of hope-driven leaps of faith.</p>
<p>Put another way, optimizing your site enables you to <em>fail fast</em>.  One of the marketers in our session said that some of his most significant test results are those that show him which ideas don&#8217;t succeed.  To know that something doesn&#8217;t work on your site allows you to put that debate to bed and move on to the other ideas on the list.</p>
<p><strong>4) Time is of the Essence</strong></p>
<p><img class="alignleft" style="float: left;" src="http://assets.omniture.com/en/images/blogs/lily_post_8_image_5.jpg" alt="" />The window of time to get a head start on the competition is closing quickly.  69% of marketers who have not already begun testing plan on implementing it within the next year.</p>
<p>If you look at the companies who are producing the most innovative products and sites, you&#8217;ll notice they all have one thing in common - they are ahead of the curve.  When Amazon created a retail site, they didn&#8217;t wait until their competitors figured out that whole personalization thing first.  When Southwest Airlines came up with a new way to ticket and board people, they didn&#8217;t wait to see whether the process would fail in another airline&#8217;s hands first.</p>
<p>Optimizing your site is a way to innovate.  Understanding how your customers react to content and layout and design gives you a huge advantage. Linking their offsite experiences with their onsite experiences allows you to reach out across multiple channels.  That integration is not only an opportunity to increase revenue and conversion, but also a way to present a cohesive message about your brand.</p>
<p>I have a very successful customer who I&#8217;ve been trying to get out to conferences to talk about the stellar test results he&#8217;s seen and the ways in which he went about installing a testing culture at his company.  He&#8217;s hesitant to talk about anything related to his optimization efforts though.  He realizes he&#8217;s found a competitive edge at a time when there are few edges to be found, and now is the time for him to exploit it for all it&#8217;s worth.</p>
<p><strong>5) Arm Yourself With Data</strong></p>
<p>You probably have analytics running on your site today that can help you identify problem areas, places where your visitors are bouncing at a high rate or clicking away from the purchase path.  Think about what you could test in those areas to improve your success metrics, and then bring both the data and the correlating ideas with you.</p>
<p>Have you considered segmenting your audience as well?  Make the case for targeting large segments intelligently.  The segments that I would recommend examining include traffic source (email, PPC, organic search, banner ads, etc), search queries (branded vs. non-branded), time of day (work hours vs. non-work hours), day of week (weekday vs. weekend), and loyalty (new vs. return vs. past purchase history).  Bring data that is specific to your company, your business, and your competitors.</p>
<p>Lastly, bring case studies that show other companies deriving value from testing and targeting on their sites.  If you need any inspiration, check out Omniture Test&amp;Target&#8217;s own <a href="http://www.omniture.com/en/resources/case_studies">repository</a>. Here are a few specific Test&amp;Target ones to check out:</p>
<ul>
<li><a href="http://www.omniture.com/offer/117">Dallas Morning News&#8217; Subscription Optimization</a></li>
<li><a href="http://www.omniture.com/offer/117">BabyCenter&#8217;s Landing Page Optimization</a></li>
<li><a href="http://www.omniture.com/offer/114">Musician&#8217;s Friends&#8217;s Affiliate Reinforcement</a></li>
<li><a href="http://www.omniture.com/offer/115">CNET&#8217;s Engagement Opmitization</a></li>
</ul>
<p>Implementing a new culture of testing and data-driven decision-making does require changes in your organization, there&#8217;s just no way around it.  It doesn&#8217;t happen overnight and it doesn&#8217;t happen without someone to enthusiastically support it, preferably someone high up on the food chain.  But let&#8217;s also recognize that while change can be scary and political, it is also necessary for any company trying to keep up online today.  And hey, the goal is not to keep up, the goal is to win.  We&#8217;ve seen many of our optimization champions go on to be recognized as rock stars within their companies, people who can point to data and attribute annualized gains in the millions back to their specific testing efforts.  Is that something you can say about yourself today?</p>
<img src="http://feeds.feedburner.com/~r/omniture/blogs/author/lchiu/~4/dGY6ldlMo6s" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blogs.omniture.com/2008/10/17/building-a-business-case-for-testing/feed/</wfw:commentRss>
		<feedburner:origLink>http://blogs.omniture.com/2008/10/17/building-a-business-case-for-testing/</feedburner:origLink></item>
		<item>
		<title>Optimization Is Greater Than the Sum of Its Parts</title>
		<link>http://feedproxy.google.com/~r/omniture/blogs/author/lchiu/~3/Z3ewoq5eUUA/</link>
		<comments>http://blogs.omniture.com/2008/10/09/optimization-is-greater-than-the-sum-of-its-parts/#comments</comments>
		<pubDate>Thu, 09 Oct 2008 21:00:40 +0000</pubDate>
		<dc:creator>Lily Chiu</dc:creator>
		
		<category><![CDATA[Testing and Targeting]]></category>

		<category><![CDATA[optimization]]></category>

		<category><![CDATA[targeting]]></category>

		<category><![CDATA[testing]]></category>

		<guid isPermaLink="false">http://blogs.omniture.com/?p=131</guid>
		<description><![CDATA[Optimization is a fuzzy word.  It&#8217;s been used to describe everything from decreasing page load time to improving user experience.  I&#8217;m guilty of using it as a catch-all as well, but today I want to focus on two key components when it comes to optimizing your site for conversion:
1) Testing - the process [...]]]></description>
			<content:encoded><![CDATA[<p>Optimization is a fuzzy word.  It&#8217;s been used to describe everything from decreasing page load time to improving user experience.  I&#8217;m guilty of using it as a catch-all as well, but today I want to focus on two key components when it comes to optimizing your site for conversion:</p>
<p>1) Testing - the process of testing alternatives on your site to see what converts best.  Testing is most often implemented as simultaneously delivering alternative content to your visitors in a randomized fashion.</p>
<p>2) Targeting - the process of displaying relevant content to a particular segment or individual based on implicit and explicit variables such as gender, search terms, and intent.  Targeting is most often implemented as delivering content to your visitors in a rules-based fashion.  For some companies with enough site traffic, targeting can be delivered to the individual in an automated fashion.</p>
<p><strong>Testing and Targeting: 1+1=3</strong></p>
<p>Both efforts rely on the ability to deliver content dynamically on your site.  Both are designed to increase key success metrics on your site.  However, they are often separated as two completely different initiatives within a marketing organization.  While people seem to be interested in the idea of combining them, they are usually already siloed as different projects with different teams, budgets and timelines by the time we have the discussion. I think bringing testing and targeting together is really one of those cases where 1+1=3 though.</p>
<p>Let&#8217;s first talk about testing by itself.  It&#8217;s a great way to figure out what version your visitors prefer.  If you&#8217;re just throwing new designs up on your site today on a wish and a prayer, testing is definitely a must.  But then think about who your visitors are.  Are they all people who are coming for the first time?  Are they all visiting during work hours?  Do they all enter on the same page looking for the same thing?</p>
<p>If your answer is no to any of these questions, then you have to ask yourself if it makes sense to assume that they all prefer the same winner in any given test.  The easiest way to figure this out is to segment your reporting. That doesn&#8217;t change anything about how the test is designed or implemented, but it can give you additional learnings in the reporting and analysis.</p>
<p>What if you found out that the reason a particular version won was because it resonated deeply with your new visitors coming organically to your site?  And balancing out that great lift was actually a negative result with other smaller segments such as direct mail and branded queries coming from paid search?  This type of data is incredibly valuable for any organization trying to get deeper insights into what their visitors are looking for and responding to.  What makes it invaluable is to then take action on those learnings by delivering that targeted, winning experience to your organic, first-time visitors and then simultaneously beginning a new test on the rest of the traffic.</p>
<p><a href="http://www.eharmony.com/">eHarmony</a> ran a test with us to understand whether adding tabbed navigation to a landing page would be more effective in getting users to convert.  The hypothesis was that providing more information about the service directly on the landing page would be a positive change.  Here are the different versions.</p>
<p><img src="http://assets.omniture.com/en/images/blogs/lily_optimization_image1.jpg" alt="" width="535" height="188" /></p>
<p>What we found was that the test actually performed worse for overall traffic, and that people preferred the simplified page without the AJAX navigation.  Once we dug into our segments though, we found a more complex and interesting story.  We had set up geo-segments to track how people from different countries behaved, and it turned out that visitors from Canada significantly preferred the navigation.  This learning would never have been found without segmentation, and worse, the tabbed navigation would have probably been thrown out based on the overall negative lift.</p>
<p><strong>What is Targeting Without Testing?</strong></p>
<p>What is targeting without testing though?  Isn&#8217;t it the same as just putting your hypothesis out onto the site and hoping your hunch aligns with your visitors?  For example, let&#8217;s say you own a retail clothing site, and you want to target visitors who look at accessories and then return to the home page.  You may wonder which accessories to now reinforce upon their return, but what if you should instead be asking yourself whether accessories is the right category to show?  What if you should be featuring women&#8217;s clothing instead because there is a high correlation between the two or the potential for higher margin profit?  Or what if showing 2 featured products instead of 6 would make all the difference?  Do you know which price range you should be staying between?  All of these questions are great opportunities to combine testing and targeting into a single initiative focused on creating conversion and revenue on your site.</p>
<p><a href="http://www.babycenter.com/">BabyCenter</a> ran a test with Test&amp;Target to understand the impact of increasing relevancy on one of their most highly-trafficked keywords: &#8220;baby names.&#8221;  Below is the control version, along with the alternatives tested against it.  What&#8217;s interesting to note here is that all of the alternatives have some element of targeting in them.  Recipe B offers some relevant text, Recipe C adds some category links, Recipe D provides top 5 names of 2005 for both girls and boys, and Recipe E builds on Recipe B with a few more bullets of information.  Can you guess which one won?</p>
<p><img src="http://assets.omniture.com/en/images/blogs/lily_optimization_image2.jpg" alt="" /></p>
<p>If you guessed Recipe D, then you are in sync with most of the marketers who see this case study.  However, the answer is Recipe B, the alternative that provides the simplest reinforcement of just a headline and a couple lines of copy.  Here&#8217;s the test data:</p>
<p><img src="http://assets.omniture.com/en/images/blogs/lily_optimization_image1new.jpg" alt="" width="802" height="227" /></p>
<p>You can see that Recipe B provided <!--[if gte mso 9]><xml> <w:WordDocument> <w:View>Normal</w:View> <w:Zoom>0</w:Zoom> <w:TrackMoves /> <w:TrackFormatting /> <w:PunctuationKerning /> <w:ValidateAgainstSchemas /> <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid> <w:IgnoreMixedContent>false</w:IgnoreMixedContent> <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText> <w:DoNotPromoteQF /> <w:LidThemeOther>EN-US</w:LidThemeOther> <w:LidThemeAsian>X-NONE</w:LidThemeAsian> <w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript> <w:Compatibility> <w:BreakWrappedTables /> <w:SnapToGridInCell /> <w:WrapTextWithPunct /> <w:UseAsianBreakRules /> <w:DontGrowAutofit /> <w:SplitPgBreakAndParaMark /> <w:DontVertAlignCellWithSp /> <w:DontBreakConstrainedForcedTables /> <w:DontVertAlignInTxbx /> <w:Word11KerningPairs /> <w:CachedColBalance /> </w:Compatibility> <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel> <m:mathPr> <m:mathFont m:val="Cambria Math" /> <m:brkBin m:val="before" /> <m:brkBinSub m:val="&#45;-" /> <m:smallFrac m:val="off" /> <m:dispDef /> <m:lMargin m:val="0" /> <m:rMargin m:val="0" /> <m:defJc m:val="centerGroup" /> <m:wrapIndent m:val="1440" /> <m:intLim m:val="subSup" /> <m:naryLim m:val="undOvr" /> </m:mathPr></w:WordDocument> </xml><![endif]--><!--[if gte mso 9]><xml> <w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"   DefSemiHidden="true" DefQFormat="false" DefPriority="99"   LatentStyleCount="267"> <w:LsdException Locked="false" Priority="0" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Normal" /> <w:LsdException Locked="false" Priority="9" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="heading 1" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8" /> <w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9" /> <w:LsdException Locked="false" Priority="39" Name="toc 1" /> <w:LsdException Locked="false" Priority="39" Name="toc 2" /> <w:LsdException Locked="false" Priority="39" Name="toc 3" /> <w:LsdException Locked="false" Priority="39" Name="toc 4" /> <w:LsdException Locked="false" Priority="39" Name="toc 5" /> <w:LsdException Locked="false" Priority="39" Name="toc 6" /> <w:LsdException Locked="false" Priority="39" Name="toc 7" /> <w:LsdException Locked="false" Priority="39" Name="toc 8" /> <w:LsdException Locked="false" Priority="39" Name="toc 9" /> <w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption" /> <w:LsdException Locked="false" Priority="10" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Title" /> <w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font" /> <w:LsdException Locked="false" Priority="11" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtitle" /> <w:LsdException Locked="false" Priority="22" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Strong" /> <w:LsdException Locked="false" Priority="20" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Emphasis" /> <w:LsdException Locked="false" Priority="59" SemiHidden="false"    UnhideWhenUsed="false" Name="Table Grid" /> <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text" /> <w:LsdException Locked="false" Priority="1" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="No Spacing" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 1" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 1" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 1" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 1" /> <w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision" /> <w:LsdException Locked="false" Priority="34" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="List Paragraph" /> <w:LsdException Locked="false" Priority="29" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Quote" /> <w:LsdException Locked="false" Priority="30" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Quote" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 1" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 1" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 1" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 1" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 1" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 2" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 2" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 2" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 2" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 2" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 2" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 2" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 2" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 2" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 3" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 3" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 3" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 3" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 3" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 3" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 3" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 3" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 3" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 4" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 4" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 4" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 4" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 4" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 4" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 4" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 4" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 4" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 5" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 5" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 5" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 5" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 5" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 5" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 5" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 5" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 5" /> <w:LsdException Locked="false" Priority="60" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Shading Accent 6" /> <w:LsdException Locked="false" Priority="61" SemiHidden="false"    UnhideWhenUsed="false" Name="Light List Accent 6" /> <w:LsdException Locked="false" Priority="62" SemiHidden="false"    UnhideWhenUsed="false" Name="Light Grid Accent 6" /> <w:LsdException Locked="false" Priority="63" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6" /> <w:LsdException Locked="false" Priority="64" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6" /> <w:LsdException Locked="false" Priority="65" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 1 Accent 6" /> <w:LsdException Locked="false" Priority="66" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium List 2 Accent 6" /> <w:LsdException Locked="false" Priority="67" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6" /> <w:LsdException Locked="false" Priority="68" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6" /> <w:LsdException Locked="false" Priority="69" SemiHidden="false"    UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6" /> <w:LsdException Locked="false" Priority="70" SemiHidden="false"    UnhideWhenUsed="false" Name="Dark List Accent 6" /> <w:LsdException Locked="false" Priority="71" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Shading Accent 6" /> <w:LsdException Locked="false" Priority="72" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful List Accent 6" /> <w:LsdException Locked="false" Priority="73" SemiHidden="false"    UnhideWhenUsed="false" Name="Colorful Grid Accent 6" /> <w:LsdException Locked="false" Priority="19" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis" /> <w:LsdException Locked="false" Priority="21" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis" /> <w:LsdException Locked="false" Priority="31" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference" /> <w:LsdException Locked="false" Priority="32" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Intense Reference" /> <w:LsdException Locked="false" Priority="33" SemiHidden="false"    UnhideWhenUsed="false" QFormat="true" Name="Book Title" /> <w:LsdException Locked="false" Priority="37" Name="Bibliography" /> <w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading" /> </w:LatentStyles> </xml><![endif]--> 65.32<span style="font-size: 12pt; font-family: ">%</span> lift against control with very high statistical confidence.  In fact, nearly every alternative performed better than the control except for Recipe D, the version that people most often pick as the winner.  It makes sense that we naturally gravitate to Recipe D because it provides us with the most relevant information given that we are searching on the term, &#8220;baby names.&#8221;  However, since we are measuring the success of the landing page based on those who sign up for the magazine, we have to balance driving both relevancy and engagement.  Without testing this targeting effort though, we would have no idea whether we picked the right mix.</p>
<p>If you are in the process of testing today, I&#8217;d strongly advocate setting up segments so you can begin to see which ones behave differently.  Targeting is a natural extension of testing, but don&#8217;t forget to go back and test your hunches as well, whether they apply to one segment or all of your traffic.  Taking action on your data is the best way to do more with less, a strategy we will all have to follow more closely through the immediate future.</p>
<img src="http://feeds.feedburner.com/~r/omniture/blogs/author/lchiu/~4/Z3ewoq5eUUA" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blogs.omniture.com/2008/10/09/optimization-is-greater-than-the-sum-of-its-parts/feed/</wfw:commentRss>
		<feedburner:origLink>http://blogs.omniture.com/2008/10/09/optimization-is-greater-than-the-sum-of-its-parts/</feedburner:origLink></item>
		<item>
		<title>Fractional-Factorial vs. Full-Factorial: An Ideological War?</title>
		<link>http://feedproxy.google.com/~r/omniture/blogs/author/lchiu/~3/v94SC5a2KjM/</link>
		<comments>http://blogs.omniture.com/2008/08/27/fractional-factorial-vs-full-factorial-an-ideological-war/#comments</comments>
		<pubDate>Wed, 27 Aug 2008 16:27:17 +0000</pubDate>
		<dc:creator>Lily Chiu</dc:creator>
		
		<category><![CDATA[Testing and Targeting]]></category>

		<category><![CDATA[fractional-factorial]]></category>

		<category><![CDATA[full-factorial]]></category>

		<category><![CDATA[multivariate testing]]></category>

		<guid isPermaLink="false">http://blogs.omniture.com/?p=110</guid>
		<description><![CDATA[There&#8217;s been quite a storm brewing around the best methodology to use for multivariate testing: fractional-factorial vs. full-factorial. (For a quick primer, definitions of both are included at the bottom of this post.) I have to say that some of the arguments I&#8217;ve heard border on ideological in both their passion and rigor. Are there [...]]]></description>
			<content:encoded><![CDATA[<p>There&#8217;s been quite a storm brewing around the best methodology to use for <a href="http://www.omniture.com/en/products/conversion/testandtarget" target="_blank">multivariate testing</a>: fractional-factorial vs. full-factorial. (For a quick primer, definitions of both are included at the bottom of this post.) I have to say that some of the arguments I&#8217;ve heard border on ideological in both their passion and rigor. Are there scenarios where one methodology makes more sense than the other? Absolutely. Is it possible that one methodology is right for every scenario? No. I have my own thoughts on when each approach is applicable, but I&#8217;d first like to see if we can agree on a few statements:</p>
<p>1) The Internet changes every day, whether it&#8217;s based on oil prices, local and global news, or your competition switching tactics and prices.</p>
<p>2) What worked on your site six months ago may not be the same thing that works today, and will most likely not be what works six months from now.</p>
<p>3) The most successful Internet marketers are light on their feet - agile, flexible, and able to adapt quickly.</p>
<p>4) There is no magic formula to the Internet. We cannot say that if A &amp; B, then C will happen each and every time.</p>
<p>In a perfect theoretical world where none of the statements above were true, I would run full-factorial each and every time. That way, I get to understand which exact combination is best out of all the possible combinations of elements, and even calculate all the different levels of interaction between elements. However, we unfortunately don&#8217;t have the gift of infinite time when running tests and analyzing results.</p>
<p>I recently read a case study touting full-factorial and the 576 different combinations tested. It had great graphs and charts of data, but, in my opinion, there were 2 huge things missing:</p>
<p>1) How long did this test take to run? If I go by Google&#8217;s <a href="http://www.google.com/support/websiteoptimizer/bin/answer.py?answer=61688&amp;hl=en_US">handy calculator</a>, I would estimate it took nearly half a year:</p>
<p><img src="/wp-content/uploads/2008/08/lilychiu_post_6.jpg" alt="" /></p>
<p>I don&#8217;t know many companies who have the luxury of running a test longer than one month, let alone five months!</p>
<p>2) How did different customer segments perform? Were segments even set up and tracked? With 576 combinations to test, even setting up two coarse segments such as new visitor and return visitor would double the amount of time the test had to run. In this case, we&#8217;re now looking at closer to a year! How can any company with various acquisition points and customer behavioral segments run a test and not slice their population up to understand where the differentiation lies though? Consider the customers who search on &#8220;guitar center&#8221; vs. those who click a PPC ad after searching for &#8220;les paul guitar&#8221; - is it possible they might react differently in a test? I would say it&#8217;s quite likely.</p>
<p>Does all this mean there are no cases where full-factorial might be more effective? Not at all. I have recommended running a full-factorial to clients in the past when the elements they were testing were highly graphical and seemed interdependent. Take, for example, a row of different photo categories (Abstracts, People, Close ups, B&amp;W, etc) to choose from where each category&#8217;s photo representation would be considered an element to test. That seems like the appropriate place to run a full-factorial because you may not want 2 pictures that look very similar to appear side-by-side. However, there are trade-offs to dedicating the time and traffic to full-factorial. You most likely have to severely limit the number of elements you will be testing at once. You may also have to forgo customer segmentation unless you are one of the few companies with the benefit of millions of visitors a day.</p>
<p>I think that one of our own customers actually summed it up best for me last week. John Pace, a true champion of testing and the head of optimization at <a href="http://www.realnetworks.com/">Real Networks</a>, likened fractional-factorial testing to a barometer. He&#8217;s a sailing man, so forgive me if the analogy doesn&#8217;t sync up for you. A barometer measures atmospheric pressure, but its value is not so much in the precise measurement as the notification that there is a directional change in pressure.</p>
<p>In much the same way, testing is supposed to give you directional feedback on what is performing and resonating best with your visitors. Testing is not a document or proof that you can use to be 100% sure of how your visitors will behave moving forward. Because of that, I question how valuable it is to spend 5 months running 1 single test for learnings that may no longer be applicable by the time the test has completed and the data pumped through analysis. Instead, why not take the winnings and learnings of your week-long fractional-factorial multivariate test and then run another test that builds off that new and improved baseline. If you can approach your testing program that way, I&#8217;m confident that you&#8217;ll find more upside in both lift and learnings in the same 5-month period.</p>
<p>At the end of the day, no matter which methodology you end up using, the race for conversions and revenue is not going to be won by the might of your statistics. Your strengths should be creativity, innovation, and the ability to listen and react to your customer. Employing those in testing will get you to the finish line; it&#8217;s just a matter of whether you get there sooner or later than the rest of the pack.</p>
<p><em><strong>Definitions</strong></em></p>
<p><em><strong>Multivariate Test:</strong> A multivariate (MVT) test enables you to test multiple elements simultaneously. A multivariate test example would be to test the banner, headline, copy, and call-to-action on a landing page. The benefits of running a multivariate test are that you can test more elements at once than an A/B test, and you also get information about which elements were most significant and which alternatives produced the most lift.</em></p>
<p><em><strong>Full-Factorial Design:</strong> Full-factorial design tests all of the different combinations of elements and their alternatives. For example, if you had 7 elements on a page with 2 alternatives each, a full-factorial design would test all 128 (2^7) combinations.</em></p>
<p><em>Fractional-Factorial Design: Fractional-factorial design tests a subset of all the different combinations of elements and their alternatives. In the same test example above, a fractional- factorial design using the Taguchi method would test 8 combinations.</em></p>
<img src="http://feeds.feedburner.com/~r/omniture/blogs/author/lchiu/~4/v94SC5a2KjM" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://blogs.omniture.com/2008/08/27/fractional-factorial-vs-full-factorial-an-ideological-war/feed/</wfw:commentRss>
		<feedburner:origLink>http://blogs.omniture.com/2008/08/27/fractional-factorial-vs-full-factorial-an-ideological-war/</feedburner:origLink></item>
	</channel>
</rss>
