ConfigCat allows the user to launch new features and change software configuration without (re)deploying code. ConfigCat SDKs enable easy integration with any web, mobile or backend applications. The ConfigCat website enables non-developers too to switch ON/OFF application features or change software configuration. This way the user can decouple feature launches and configuration from code deployment.
$0
per month
Optimizely Web Experimentation
Score 8.7 out of 10
N/A
Whether launching a first test or scaling a sophisticated experimentation program, Optimizely Web Experimentation aims to deliver the insights needed to craft high-performing digital experiences that drive engagement, increase conversions, and accelerate growth.
N/A
Pricing
ConfigCat
Optimizely Web Experimentation
Editions & Modules
Free
$0.00
per month
Professional
$49.00
per month
Unlimited
$199.00
per month
Dedicated on-premise infra
$1499.00
per month
Dedicated hosted infra
$1499.00
per month
No answers on this topic
Offerings
Pricing Offerings
ConfigCat
Optimizely Web Experimentation
Free Trial
Yes
Yes
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
Optional
Additional Details
Fair pricing policy: All features available in all plans, even in Free. Simple and predictable prices. No hidden fees. We don't charge for team size. We don't charge for MAUs (monthly active users). Our plans only differ in limitations.
ConfigCat isn't 'battleship' class with tons of bells of whistles when compared to Optimizely or LaunchDarkly. Having said that, it does what we needed it to do and had a roadmap to add any functionality that we have felt as a shortcoming. ConfigCat is also a fraction of the …
Optimizely Web Experimentation
No answer on this topic
Features
ConfigCat
Optimizely Web Experimentation
Testing and Experimentation
Comparison of Testing and Experimentation features of Product A and Product B
ConfigCat
-
Ratings
Optimizely Web Experimentation
7.9
163 Ratings
6% below category average
a/b experiment testing
00 Ratings
9.0163 Ratings
Split URL testing
00 Ratings
8.5135 Ratings
Multivariate testing
00 Ratings
8.4139 Ratings
Multi-page/funnel testing
00 Ratings
7.9126 Ratings
Cross-browser testing
00 Ratings
8.197 Ratings
Mobile app testing
00 Ratings
8.175 Ratings
Test significance
00 Ratings
8.4147 Ratings
Visual / WYSIWYG editor
00 Ratings
8.1133 Ratings
Advanced code editor
00 Ratings
7.9125 Ratings
Page surveys
00 Ratings
6.217 Ratings
Visitor recordings
00 Ratings
8.418 Ratings
Preview mode
00 Ratings
7.6145 Ratings
Test duration calculator
00 Ratings
7.8112 Ratings
Experiment scheduler
00 Ratings
8.2112 Ratings
Experiment workflow and approval
00 Ratings
7.890 Ratings
Dynamic experiment activation
00 Ratings
7.674 Ratings
Client-side tests
00 Ratings
7.896 Ratings
Server-side tests
00 Ratings
7.250 Ratings
Mutually exclusive tests
00 Ratings
8.180 Ratings
Audience Segmentation & Targeting
Comparison of Audience Segmentation & Targeting features of Product A and Product B
ConfigCat
-
Ratings
Optimizely Web Experimentation
8.2
152 Ratings
7% below category average
Standard visitor segmentation
00 Ratings
8.4147 Ratings
Behavioral visitor segmentation
00 Ratings
7.7122 Ratings
Traffic allocation control
00 Ratings
9.1144 Ratings
Website personalization
00 Ratings
7.8111 Ratings
Results and Analysis
Comparison of Results and Analysis features of Product A and Product B
If you are looking for an experimentation/feature flag style tool that is quick to adopt and provides enough functionality for light/medium use cases, then this is the tool for you. Additionally, they are growing and expanding their functionality and feature set so they can grow alongside you and your needs. The publicly accessible roadmap is also a great benefit to see where time is being spent on which feature next.
I think it can serve the whole spectrum of experiences from people who are just getting used to web experimentation. It's really easy to pick up and use. If you're more experienced then it works well because it just gets out of the way and lets you really focus on the experimentation side of things. So yeah, strongly recommend. I think it is well suited both to small businesses and large enterprises as well. I think it's got a really low barrier to entry. It's very easy to integrate on your website and get results quickly. Likewise, if you are a big business, it's incrementally adoptable, so you can start out with one component of optimizing and you can build there and start to build in things like data CMS to augment experimentation as well. So it's got a really strong a pathway to grow your MarTech platform if you're a small company or a big company.
The Platform contains drag-and-drop editor options for creating variations, which ease the A/B tests process, as it does not require any coding or development resources.
Establishing it is so simple that even a non-technical person can do it perfectly.
It provides real-time results and analytics with robust dashboard access through which you can quickly analyze how different variations perform. With this, your team can easily make data-driven decisions Fastly.
I rated this question because at this stage, Optimizely does most everything we need so I don't foresee a need to migrate to a new tool. We have the infrastructure already in place and it is a sizeable lift to pivot to another tool with no guarantee that it will work as good or even better than Optimizely
Just everything from the website to locating what i need (docs) specific to my platforms is super easy. Not to mention the support articles answering previous questions
Optimizely Web Experimentation's visual editor is handy for non-technical or quick iterative testing. When it comes to content changes it's as easy as going into wordpress, clicking around, and then seeing your changes live--what you see is what you get. The preview and approval process for sharing built experiments is also handy for sharing experiments across teams for QA purposes or otherwise.
I would rate Optimizely Web Experimentation's availability as a 10 out of 10. The software is reliable and does not experience any application errors or unplanned outages. Additionally, the customer service and technical support teams are always available to help with any issues or questions.
I would rate Optimizely Web Experimentation's performance as a 9 out of 10. Pages load quickly, reports are complete in a reasonable time frame, and the software does not slow down any other software or systems that it integrates with. Additionally, the customer service and technical support teams are always available to help with any issues or questions.
They have a community Slack channel that is open to anyone. They always seem to have people in there, even over the weekends and are always happy to answer any questions you have,
They always are quick to respond, and are so friendly and helpful. They always answer the phone right away. And [they are] always willing to not only help you with your problem, but if you need ideas they have suggestions as well.
The tool itself is not very difficult to use so training was not very useful in my opinion. It did not also account for success events more complex than a click (which my company being ecommerce is looking to examine more than a mere click).
In retrospect: - I think I should have stressed more demo's / workshopping with the Optimizely team at the start. I felt too confident during demo stages, and when came time to actually start, I was a bit lost. (The answer is likely I should have had them on-hand for our first install.. they offered but I thought I was OK.) - Really getting an understanding / asking them prior to install of how to make it really work for checkout pages / one that uses dynamic content or user interaction to determine what the UI does. Could have saved some time by addressing this at the beginning, as some things we needed to create on our site for Optimizely to "use" as a trigger for the variation test. - Having a number of planned/hoped-for tests already in-hand before working with Optimizely team. Sharing those thoughts with them would likely have started conversations on additional things we needed to do to make them work (rather than figuring that out during the actual builds). Since I had development time available, I could have added more things to the baseline installation since my developers were already "looking under the hood" of the site.
At iBinder we searched for and vetted several suppliers of a feature toggle service to handle feature toggling in our production environment. In addition to our functional requirements, it was crucial for us to find a partner that could deliver an EU-compliant service. We finally decided to sign a service agreement with ConfigCat. This has been a real success story for us – in addition to being compliant, ConfigCat delivers an amazing, flexible, and reliable service. They continue to impress by also being very transparent and having a fantastic support and they are very solution oriented and accommodating when it comes to our feature requests etc. We have now used ConfigCat for approximately 2 years and we give our warmest recommendations to anyone who needs a stable, reliable and EU-compliant feature toggle service.
The ability to do A/B testing in Optimizely along with the associated statistical modelling and audience segmentation means it is a much better solution than using something like Google Analytics were a lot more effort is required to identify and isolate the specific data you need to confidently make changes
We can use it flexibly across lines of business and have it in use across two departments. We have different use cases and slightly different outcomes, but can unify our results based on impact to the bottom line. Finally, we can generate value from anywhere in the org for any stakeholders as needed.
Allowed us to migrate seamlessly from a major customer communication system to another, reducing end-user friction and production bugs by being able to turn features off if they didn't work as intended.
We went from zero experimentation to running 10-20 experiments concurrently across systems. Engineering teams are thinking in an experimentation mindset.
We're able to share definitive annualized revenue projections with our team, showing what would happen if we put a test into Production
Showing the results of a test on a new page or feature prior to full implementation on a site saves developer time (if a test proves the new element doesn't deliver a significant improvement.
Making a change via the WYSIWYG interface allows us to see multiple changes without developer intervention.