Optimize Wide To Narrow

If you consider the path that a user takes through your website from landing page to successful conversion, you can think of the number of users that make it to each point along the way to a successful conversion as similarly shaped to that of a funnel. In a typical setup, you may have a very small percentage of your users make it to a successful conversion, but there are several areas along the way that either improve the chances the user will convert or decrease those chances.

As an example, lets say your landing page had 1,000,000 unique users reach it, and 10%, or 100,000 clicked on the call to action button, taking them to the next step. On step 2, lets say that 5% of the 100,000 were able to make it through, which would be 5,000 users. Step 3 is the conversion step, and lets say that only 20% of the remaining users make it through, for a total of 1,000 successful conversions.

If you were to look at it based on raw conversion percentages, you would think that the best step to work on increasing conversion rates would be step 2 as it has the lowest raw percentage conversion rate. However, if you were to make step 2 the first improvement location, you could be optimizing the conversion process for the wrong user. Instead, if you were to optimize step 1 until it reached some conversion rate goal, you could see a much greater number of users make it to step 2 in the process. At that point, you may find out that there was nothing wrong with step 2 itself, as the problem was step 1 all along.

If you do determine that step 2 does not meet its conversion rate goals, focus on optimizing it until you reach the goals you have set. Finally optimize the last step in the conversion process to remove any final roadblocks to conversion for your users.

The important thing to remember is that if you optimize from the narrow part of the funnel outwards, you may be optimizing conversion success for a very narrow subset of users, and when there is a larger stream of users making it further in the conversion process, your optimized step 3 may not work as you had hoped for this expanded audience to your conversion endpoint.

Tags:

Related Posts

Mar 17, 2015
2 minutes

When Is Enough CSS Enough?

One of the major pushes in web development today is to try to do as much of the styling of a website as is possible from within the CSS of the site. The idea behind this is that when you do so, you remove styling responsibilities from your JavaScript and HTML content, resulting in a much better separation of concerns. The other aspect of this is that CSS styling is typically handled in a more native fashion in the browser as compared to what you can accomplish via Javascript.

#internet-explorer #responsive-web-design #javascript
Read More
Mar 12, 2015
3 minutes

The Number 1 Cause of the Not Invented Here Syndrome

One of the quickest ways to get a new internal tool bootstrapped is to utilize an existing design, making slight adjustments to ensure the design matches the requirements of the current project. Instead of using another internal tool as the basis for the new design, I used a design that was purchased specifically for this project.

This particular design was unique in that there were multiple working examples using AJAX, pure HTML, and AngularJS. While it was nice having supposed working examples, when you start to look at the readme file for how to get this functionality working on your own hosting setup, thats when the niceties disappear. Specifically when lookng at the readme file for AngularJS, it effectively says: “Because this is a well-known JavaScript framework, we are not including any documentation for how it works or how to get started with our design”. Granted, the inner workings of AngularJS need not be covered in the readme, but a simple walkthrough of what to expect this design to do would make things much more user/developer friendly.

#magento #jquery #javascript
Read More
May 23, 2014
2 minutes

Avoid SiteCatalyst's useForcedLinkTracking and target="_blank"

All sites rely upon some third party analytics software to track at the very least the number of visitors to a site. Many sites use Google Analytics, which provide much more information that just the number of visitors. Another option that some of the bigger sites use is Adobe Analytics, aka SiteCatalyst to enable more custom tracking options that are not evident through the Google Analytics interface.

One feature of SiteCatalyst is that it allows you to set an option useForcedLinkTracking that will track every link on your site for clicks whether or not you have setup custom tracking for the links or not. Effectively what the code does is create a JavaScript event handler to intercept all click events on the <a href="http://url.com">Link</a> hyperlinks. Once they are intercepted, SiteCatalyst sends its tracking information to its servers and then procedes to attempt to make sure that the link functions properly. Unfortunately, in some versions of the SiteCatalyst code, it attempts to create a synthetic click event that works in many cases. However, if you are using Safari with the popup blocker turned on, and a target="_blank" in the hyperlink, then it will trigger the popup blocker, which simply ignores the click, and the user sees nothing happen at all. In order to fix it, hopefully the latest version of the SiteCatalyst code will handle it, turn off useForcedLinkTracking, or, as the very last resort, convert the <a /> links to another type of element and use JavaScript to open the new window manually when listening for the click event on the new element. It seems this works all the time, but it will prevent SiteCatalyst from tracking those clicks.

#javascript #rant #sitecatalyst
Read More