Optimizely Feature Experimentation Reviews & Product Details - Page 8

I really enjoyed my experience as it provided very in-depth analytics on my feature and the respective environments. In this way, I was able to make inferences from the traffic and relay important information to my team Review collected by and hosted on G2.com.

I did think that the time for changes to propagate in the envs was a bit longer than I liked Review collected by and hosted on G2.com.

It's straightforward to do feature tests and A/B tests. There is excellent documentation for developers, and the results page is detailed and valuable. The history page makes it easy to track changes to experiments. Review collected by and hosted on G2.com.

The website can sometimes be slow to load. It might be clearer to include "Variations" and "Traffic Allocation" so it's easier to understand how much traffic is going precisely to each variation. Review collected by and hosted on G2.com.

I always use Optimizely full-stack for my AB tests on contentful. It integrates well and setting up an experiment doesn't take much time. Review collected by and hosted on G2.com.

AB test results overview could be better visually with more customization options. It's not as intuitive as it could be for people who are not used to it. Review collected by and hosted on G2.com.

I use the flag feature a lot as a QA. I like how simple the UI is to use e.g., to know which environments have which flags on which is super helpful to see at a glance and make comparisons in our products to ensure certain features are working correctly. Review collected by and hosted on G2.com.

I dislike that we only use some features in my workplace, so I'm not utilizing the full tool! Review collected by and hosted on G2.com.

Optimizely Full Stack has an intuitive UI, and it's easy to set up and test experiments. Forcing variants is easy, and it's simple to control traffic.

Experiment code is created for many programming languages, so a simple copy/paste will be enough to get your experiment up and running. Review collected by and hosted on G2.com.

I occasionally receive notifications that we've reached our traffic quota, but it would be helpful if these were broken down by experiment. I find it challenging to track down which experiments are causing us to exceed our quota. Review collected by and hosted on G2.com.

easy to use SDK, slack community, stat engine is good on average, sticky user profile to keep treatment the same.not a lot to like Review collected by and hosted on G2.com.

bad customer support, not flexible pricing strategy, not good for offline event, no product analytics support, not sure how multiple comparison is adjusted when you have more than 2 variant, snowflake data doesn't match result UI number and couldn't get tech support to debug. not sure what's the consequences of using different randomization id Review collected by and hosted on G2.com.

The ability to remotely control experiments and changing them from experiments to running features easily (so that also product managers can use them). Review collected by and hosted on G2.com.

The lack of support for exclusion groups with setting forced variations (we currently use our own "hack" for it, but I wish this was an out of the box solution). Review collected by and hosted on G2.com.

The level of granularity and flexibility to bucket visitors into experiments is beneficial. Review collected by and hosted on G2.com.

There's no notification or email to the owner of the experiment (or "watchers") to get notified when the experiment reached 100% stat sig. Review collected by and hosted on G2.com.

The React SDK of Optimizely Full Stack comes with easy-to-use hooks which we use to run experiments on both the server and client side. Review collected by and hosted on G2.com.

There are no downsides known to me at this point. Review collected by and hosted on G2.com.

As a developer, I found their documentation to be comprehensive, straightforward, and up-to-date. Review collected by and hosted on G2.com.

There was one small detail that was missing from the developer documentation where it never says that event logs are temporarily stored in local storage in case the request to submit errors in the case of a time-out or page refresh. Review collected by and hosted on G2.com.