Engineer perspective!
Overall Satisfaction with Optimizely Web Experimentation
We use Optimizely Web Experimentation to run front end experiments for pages on our legacy website. The business problems are wide ranging but my team specifically focuses on ancillary upsells and merchandising so for us it's usually to allow easy modification of upsell banners. We test different wordings, call to actions, etc. The scope is relatively thin since we only use it on our legacy website which is being rapidly modernized and moved to feature experimentation.
Pros
- Ease of use for non technical team members
- Being able to inject typescript helps us manage redirects from buttons easier even when it's not related to a test
Cons
- We have lots of issues with the preview browser
- Easier to mess up then code that has built in tests
- Increased conversions/revenue
- Dev time saved
We pair optimizely web with feature experimentation to round out our experiments. It usually just depends on where on the site we need one, whether it's back end or front end, and which team is responsible.
I don't personally deal with that but our experimentation team uses these tools to determine the success of an experiment. They've set up custom metrics that work best for them. Makes it easy for me to plug and play.
We use both, it just depends on the use case. I personally prefer feature experimentation but I see why both are useful.
Do you think Optimizely Web Experimentation delivers good value for the price?
Yes
Are you happy with Optimizely Web Experimentation's feature set?
Yes
Did Optimizely Web Experimentation live up to sales and marketing promises?
I wasn't involved with the selection/purchase process
Did implementation of Optimizely Web Experimentation go as expected?
Yes
Would you buy Optimizely Web Experimentation again?
Yes


Comments
Please log in to join the conversation