Feature Toggle vs. Optimizely Feature Experimentation

It's helpful that the tool takes URL parameters into account but that requires the URL structure to be of desired quality, to begin with. This tool is best suited for those working off of solid foundation in terms of web presence

Incentivized

Based on my experience with Optimizely Feature Experimentation, I can highlight several scenarios where it excels and a few where it may be less suitable. Well-suited scenarios: - Multi-Channel product launches - Complex A/B testing and feature flag management - Gradual rollout and risk mitigation Less suited scenarios: - Simple A/B tests (their Web Experimentation product is probably better for that) - Non-technical team usage -

Incentivized

• Limit software options - prevents rework time
• Allows for beta testing - allows for better later buy-in

Incentivized

• Its ability to run A/B tests and multivariate experiments simultaneously allows us to identify the best-performing options quickly.
• Optimizely blends into our analytics tools, giving us immediate feedback on how our experiments are performing. This tool helps us avoid interruptions. With this pairing, we can arrive at informed decisions quickly.
• Additionally, feature toggles enable us to introduce new features or modifications to specific user groups, guaranteeing a smooth and controlled user experience. This tool helps us avoid interruptions.

Incentivized

• More help/how-to literate or use cases.
• Conditional logic could be improved.
• More dynamic interface.

Incentivized

• We had to create our own GA4 system to track variation assignments
• The Play/Pause button can be hard to find when looking at a specific rule
• It would be great to be able to see reports on tests without having to navigate away from the flag that it is associated with

Incentivized

Competitive landscape

Incentivized

I think setting up experiments is very straightforward. It's also very easy to get started on the code side. I think if someone was new to Optimizely Feature Experimentation there could be some confusion between a flag and an experiment. I still get confused sometimes by if I turned the right thing on or off.

Incentivized

I'm not sure about the support ....we didn't use it.

Incentivized

It’s straightforward. Docs are well written and I believe there must be a support. But we haven’t used it

Incentivized

Togglz has more detailed documentation and recurring updates. But the Togglz default setting to "HTTP" caused some glitches.

Incentivized

We haven't evaluated other products. We have an in-house product that is missing a lot of features and is very behind from making the test process easier. Instead of evolving our in-house product with limited resources, we decided to go with Optimizely Feature Experimentation when we saw that other big organisations are partnering with you.

Incentivized

had troubles with performance for SSR and the React SDK

Incentivized

• The cost of a programmer is certainly a ticket to budget. Neg
• The cost savings of limiting operational database errors is certainly more positive than the negative just mentioned.

Incentivized

• We have improved various metrics throughout the course of our experimentation program with Optimizely and therefore sharing numbers is tricky. Essentially we only implement versions of the product that perform the best in terms of CVR, revenue/visitor, ATV, average order value, average basket size and so forth dependent on the north star we are trying to move with each release.

Incentivized