<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: 3 Ways to Drive Web to Print Adoption</title>
	<atom:link href="http://thewebandprint.com/web-to-print/drive-web-to-print-adoption/feed/" rel="self" type="application/rss+xml" />
	<link>http://thewebandprint.com/web-to-print/drive-web-to-print-adoption/</link>
	<description>A conversation about print and the web, print ecommerce, and creating and growing your overall print business online.</description>
	<lastBuildDate>Thu, 10 May 2012 08:56:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Jennifer Matt</title>
		<link>http://thewebandprint.com/web-to-print/drive-web-to-print-adoption/comment-page-1/#comment-210</link>
		<dc:creator>Jennifer Matt</dc:creator>
		<pubDate>Thu, 29 Jul 2010 16:20:32 +0000</pubDate>
		<guid isPermaLink="false">http://thewebandprint.com/?p=781#comment-210</guid>
		<description>Heath,

If you have a clear call to action on your site which says, Sign up for Our Free Webinar!&quot; Lets say you ask the users for name, e-mail, and phone number (3 fields) in order to register for the free webinar. If you changed that form (removed the phone field) you would increase your conversion rate by 20%. Adding more fields would drop your conversion rate. Every step you force a user through adds &quot;friction&quot; to the transaction. Remove friction and increase the conversion. Personal information carries a higher friction value - so you better be giving something valuable away in exchange for the personal information. 

Obviously some transactions require lots of information (credit card transactions, etc...), the key is to make sure you&#039;re asking for only exactly what you need, in a form that is brilliantly easy, and provide all the information you can (auto fill from profile is the user is known), etc... From a web to print standpoint, can you imagine the differences in conversion rate between a solution that has authentication integration (e.g. LDAP) vs. one that requires a separate registration and login? If the addition of a single field can drop conversion rates by 20%, can you imagine what a complete extra process including remembering yet another registration and login could do to web to print user adoption?</description>
		<content:encoded><![CDATA[<p>Heath,</p>
<p>If you have a clear call to action on your site which says, Sign up for Our Free Webinar!&#8221; Lets say you ask the users for name, e-mail, and phone number (3 fields) in order to register for the free webinar. If you changed that form (removed the phone field) you would increase your conversion rate by 20%. Adding more fields would drop your conversion rate. Every step you force a user through adds &#8220;friction&#8221; to the transaction. Remove friction and increase the conversion. Personal information carries a higher friction value &#8211; so you better be giving something valuable away in exchange for the personal information. </p>
<p>Obviously some transactions require lots of information (credit card transactions, etc&#8230;), the key is to make sure you&#8217;re asking for only exactly what you need, in a form that is brilliantly easy, and provide all the information you can (auto fill from profile is the user is known), etc&#8230; From a web to print standpoint, can you imagine the differences in conversion rate between a solution that has authentication integration (e.g. LDAP) vs. one that requires a separate registration and login? If the addition of a single field can drop conversion rates by 20%, can you imagine what a complete extra process including remembering yet another registration and login could do to web to print user adoption?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Heath</title>
		<link>http://thewebandprint.com/web-to-print/drive-web-to-print-adoption/comment-page-1/#comment-207</link>
		<dc:creator>Heath</dc:creator>
		<pubDate>Thu, 29 Jul 2010 13:25:56 +0000</pubDate>
		<guid isPermaLink="false">http://thewebandprint.com/?p=781#comment-207</guid>
		<description>Your points related to streamlining are well presented. 

Can you expand or explain further the sentence: &quot;For every field you add to a form in an ecommerce user experience, your conversion drops 20%.&quot; ?

As I read that logic is means that a form that captures (5) pieces of information would yield a 100% failure rate when it comes to conversion I&#039;m aware of very few commerce applications that don&#039;t have at least that number.</description>
		<content:encoded><![CDATA[<p>Your points related to streamlining are well presented. </p>
<p>Can you expand or explain further the sentence: &#8220;For every field you add to a form in an ecommerce user experience, your conversion drops 20%.&#8221; ?</p>
<p>As I read that logic is means that a form that captures (5) pieces of information would yield a 100% failure rate when it comes to conversion I&#8217;m aware of very few commerce applications that don&#8217;t have at least that number.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

