Optimizely Feature Experimentation

We are using Optimizely Feature Experimentation (FE) across all of our live eCommerce websites and we are actively using it across core experiences to test, analyse, experiment as well as activate features and control them on the spot through the various entities. The scope spans across multiple markets (UK/US) and we are aiming to always experiment major changes or go live in small alpha and beta groups before hitting the whole userbase with new features.

[...] is in the process of migrating Optimizely Full Stack (OFS) to Optimizely Feature Experimentation in the next few months. Optimizely Feature Experimentation's backward capabilities allow OFS to migrate to Optimizely Feature Experimentation safely without a code change.

We have instrumented Optimizely Feature Experimentation on UI, and Backend.

Optimizely Feature Experimentation is used in backend services to automate pricing test capabilities and other features. Optimizely Feature Experimentation is used for many UI experiments, such as enabling features on UI. We plan to address more Optimizely Feature Experimentation's feature variable capability to eliminate experiment variation configs.

We have a SPA, so it is more effective to use Optimizely Feature Experimentation for Experimentation, especially for complex experiments. Our developers also prefer the control and flexibility they have with Optimizely Feature Experimentation, which allows other teams to make controlled changes to the website easily and rapidly.

We use Optimizely Feature Experimentation for managing our releases, A/B testing of new features, and measuring the impact of our releases. It's used by our entire product organization for feature flagging too.

We use Optimizely Feature Experimentation for feature flagging services and ultimately to hide or show upcoming feature implementations based on the values these flags return. We also built out audiences and experiments to finely tune how we want to serve these features. We then look at the results and make business decisions on these.

It's a great tool to introduce new features and conduct experiments. We used it to try out new beta capabilities as experimentation. The scope includes all US and Canada users who make mobile orders.

We use Optimizely Feature Experimentation to test and optimize user experiences on our digital platforms. It addresses issues like user engagement and conversion rates. By A/B testing different features, we gain insights into user preferences, enabling us to make data-driven decisions to enhance our website's performance.

It's easy to grant users access via the admin portal. We have it set up through Okta SSO which makes the Integration and setup/use that much more intuitive. Creating projects and flags is also easy and can be done by users without technical support. I appreciate using the tool and being an admin for it.

We use Optimizely Feature Experimentation for its feature flag features, which lets my team and I develop features of our product privately behind a gate before rolling it out to steadily larger internal and then external audiences. We then use the feature to fully release to the full user base.

We're an online store dealing with a market that evolves quickly. Optimizely Feature Experimentation assists us in meeting the vital demand of refining our site to improve purchases. We apply it all over our internet site, assessing and perfecting new characteristics and experiences and examining various features, designs, and content from the start page to the payment page. It helps us solve important business issues, such as improving user experiences and increasing conversion rates.

We use Optimizely feature experimentation to AB test various web components on our website. Feature experimentation lets us compare conversion rates and generated revenue between different versions.

Create meaningful experiments and personalization that allow us to have an impact on the business and customers. We try to create different variations and test different metrologies that allow us to account for different goals and strategies. Meanwhile, we would like the feature experimentation tool to be more design/user-friendly we’re we can still visualize the flags and variations created optimally similar to the web.

We are using Optimizely Feature Experimentation to help us with A/B testing new changes. We have used it for layout tests to test if user conversion is increased by changes and we have also used it for new features to see if general user engagement with the website increases.

While working at CreditSesame we usually want to test different versions or pages to see which one peforms the best, luckily Optimizely Feature Experimentation has made it very easy for us to do that. I am an Adnroid engineer, and once its set up, there is very little time spent creating variations and adding new variations. I haven't used any other A/B testing tool, so there might be a better one out there, but Optimizely Feature Experimentation definitiely is good enough for most cases.

In DocuSign, we use Optimizely in many projects. In our eSigning, eSending and InProduct Communication apps, I have used Optimizely for multiple purposes. For example, in the eSending app, we have integrated with Optimizely via its JavaScript SDK to manage our system level feature flags for certain environments. We use the Optimizely Features for that.<br>As for our eSigning app, we use the Optimizely Experiments to run several A/B testing campaigns. The integration was done with JavaScript SDK.<br>In InProduct Communication apps, we use Optimizely to run A/B testing campaigns. The integration was done via C# SDK<br>All in all, we are quite happy with what Optimizely offers and their support.

we used it for AB testing and it worked pretty well. Later on, the marketing department started using it for page modifications. For example, if you need to compare what text will influence on a customer more, then Optimizely is the right tool. The same goes for colors, sizes, displaying elements, etc.

Currently being used across the entire organization, and helps address the issue of testing and validating UX changes to our website.