3. While logged in with edit rights for the Redirect Toolkit module, locate and click the Add Redirect link in Module Actions. You will be redirected to the form for defining a new rule.
4. Then using Redirect Random option you need to set the conditions so it match Percentage of Users. Note that only one operator is available for this rule, the Equals
5. Add the percent you want (in our case 50) in Value
6. So far, we told Redirect Toolkit what to match. Next, we'll tell it what to do when the condition matches. In our scenario, we want to redirect 50% of users to target URL or page.
So in the Redirect section, set Action to Redirect to Page (or Redirect to URL) then select the alternative page from the dropdown that activates below (this is B version that contains the proposed change)
7. When Redirect Toolkit matches a rule, it can be configured with Additional Actions to do before executing the redirect. These actions are useful for reporting, so for our purpose set Log Redirects which provides full logging capabilities.
Then, harnessing the amazing power of Google Analytics, you can track the user interactions on your portal, set goals and get concrete data on which page is producing the best results!
All you have to do now is wait for the stats to come in and then choose the winning version. As always with Google, you get clear stats that you can interpret in hundreds of different ways.
Once you determine which version is the winner, you can scrap the lower performing version, create a new one, and restart the test all over again. Now just repeat until you get the absolute best performing version of your test subject.
Using Redirect Toolkit for A/B testing you will have quantifiable web design data that you’ll use to optimize your portal for maximum performance.
Okay, enough of me talking. What’s your experience with A/B testing in DNN?