ConfigCat vs. VWO

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.

It works better for either small or big companies because small companies can start with the free plan which is very decent and has everything they need. Also for big companies who get the best paid plans they get a lot of premium functionalities, the insight module, outstanding reports. But for medium size companies who can only afford the basic paid plan, it may not be the best tool as it is very limited. For example, they cannot analize a/b tests for new and ruturning visitors, neither based on the users device category.

Incentivized

• Fast and easy feature toggling that gets developers developing
• World class support in both speed and quality for how to best use the service
• Great ear for customer needs and fast paced development

• VWO is pretty easy to implement on websites and doesn't require a heavy technology lift
• The VWO interface is pretty intuitive and let's non-technical users make variants for testing
• The VWO reporting dashboard is excellent for determining statistical significance and understanding whether differences in conversion rates are meaningful or not

Incentivized

• No automatic push for flag changes - have to write our own webhooks
• No scheduling interface for flipping flags automatically on a schedule
• Interface is a bit cluttered for people who are just flipping flags

• The user interface within VWO does take a bit of time to get used to, especially as it pertains to switching back and forth between tests. When running multiple experiments on a site at a time, a clear and succinct dashboard for everything in one place would be helpful (as opposed to needing to switch between A/B, multivariate, etc).

Incentivized

ConfigCat has done the job, and has been great to work with.

It's great value and we think we've ironed out all the major teething troubles. However, if we experience any more bugs or problems that significantly slow us down then we're seriously considering switching to Optimizely, which I haven't personally tested but have heard great things about from my CRO peers

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

I gave Visual Website Optimizer a rating of 8 because it is overall a great product to use. Setting up and keeping track of various tests is easy and straight forward. The only reason why this product is not rated higher is because the support documents online leave a lot of room for improvement.

I have not experienced an application error or unplanned outage with VWO.

Incentivized

VWO doesn't appear to slow down our website at all, though some customers with adblockers like UBlock Origin have been known to not see entire pages if VWO is making changes to the page at a macro level (background, font, etc). This is rare though.

Incentivized

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,

While their online document support is lacking a simple email to their support team will almost always get responded to the next day. It has however taken more than one email to explain the problem to the support team till they understood the problem. The solution I was given also only half fixed the problem the rest I figured out on my own.

Training was good, just limited to the onboarding process. They walked through all of the steps it takes to get started in VWO and each of the modules, along with giving us ideas for starting our first test. I feel like it could be better if there was a guided process within the VWO program to continue to educate you along the way, and a way to turn that off for experienced users.

Incentivized

Overall, the implementation of VWO is straightforward. If you've got a straightforward way of deploying code to all of your test pages, either a good CMS or a TMS, then implementation should be a breeze. There is no tweaking to be done to the code itself, and once deployed it has the flexibility to cope with different VWO modules (tracking, conversion analysis, session analysis) without modification.

Incentivized

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.

There are significant differences in each platform when it comes to Optimizely and vwo. From a functionality and performance perspective they each have their pros and cons. It is important to go through the feature sets of each and ensure the solution you select will work specifically with your business objectives and conversion rate optimization goals

Incentivized

The product seems infinitely scalable for our needs (small business) and we've never had any issue with loading VWO-edited elements. I will say, though, that online customers with ad blockers have been known to not see certain VWO elements as their third-party scripts are disabled.

Incentivized

• 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.

• The ability to offer a CRO service is greatly enhanced by VWO, as it allows us to run tests for clients
• The editor means to some extent we don't need much developer resource to run the tests, lowering costs of doing so

Incentivized