Optimizely series-Post 3

(Technical in nature)

If you have not read first two posts covering what is Optimizely and how QAs can use it to improve businesses in leads to customer conversions, here are they :

Post 1 : What is Optimizely and how does it matter to QAs

Post 2 : Nuts and bolts of Optimizely setup for testing

When you are done reading the post 1 and post 2, come back here to continue with Post 3. This post is more in technical on how to add Optimizely code, into web or app and how we can leverage that to advantage of testing.

For the discussion, we look into the features/user journeys of an e-commerce site :

When we talk about Optimizely, we obviously talk about increasing the business revenue , so, keeping that in mind, we can set objectives using a SMART method, similar to below :

1. Homepage to the product detail page

Objective (SMART):

• Specific: Increase clicks from the homepage to the product detail page by 15%.
• Measurable: Track clicks on product links and measure the increase.
• Achievable: Use a prominent product grid with a CTA button for better engagement.
• Relevant: Direct navigation to product detail pages is key to conversions.
• Time-bound: Achieve the target in 30 days.