Try modeling different types of drop-out within your e-commerce site. You'll be amazed how much improving conversion by a 1% at any step in the process can affect the bottom line.
Modify the funnel to represent your e-commerce or transaction flow. Study the graphical model to understand your most precipitious drops. To create your mode, use add (++) / delete (--) to remove or add steps for your task flow. Click on the task names to edit the name to match your domain.
After you create a model, you can save it to your clipboard. You can then generate a report to share the conversion differences of model variations.
In related terms, are you doing a good job maximizing the intersection of your business goals and your customer's needs?
The default configuration provided here is typical for an e-commerce transaction flow, but the principles of conversion can apply to lead generation and generally any type of workflow in which key landmarks in your clickstream can be used to monitor business success.
In my experience, almost every website experiences significant issues with engaging visitors.
Many visitors will reach your homepage but go no further. They may have come to the site with
the wrong expectations, the phone might ring or the baby begin to cry, or the site may not have engaged them.
The last of these causes is the one to focus on primarily. While good copy can help search engine
referrals enter with better expectations, you're not likely to reduce telemarketing or infant biorhythms!
In an e-commerce scenario, a variety of factors can influence add-to-cart behavior, both from internet technology and basic business principles:
|Business Variable||Technology Variable|
|Brand name||Perceived trustworthiness via design|
|Product selection||Product presentation|
|Add to cart UI|
|Customer service & fulfillment||UI around fulfillment policies|
This is an update to the Uzilla funnel concept with a 2006 DHTML implementation using the MochiKit library. Read more about how mochi helped.
Send feedback to conversionFunnel (at) gmail.com. Get more at the blog, AlwaysBeTesting.com