Contentful is a cloud based CMS solution that provides the ability to manage content across multiple platforms.The editing interface allows for managing content interactively and provides developers the ability to deliver the content with the programming language and template framework of their choice.
$489
Optimizely Web Experimentation
Score 8.8 out of 10
N/A
Optimizely Web Experimentation empowers teams to conduct experiments (without having to rely on developer resources) in order to test various user interactions, make website changes backed by data, and personalize customer experiences.
Well suited for our needs of multiple images for auto auctions from a variety of sellers. Pointing them to one platform is easier than attempting to use a variety of platforms as we were doing before (email, slack, Dropbox and Google Drive would randomly be used by a variety of employees )
Optimizely Web Experimentation is appropriate if you have a big budget and your company is mature enough in experimentation to take all the advantage of a such an expensive price model. If you are just starting into AB testing, or not enough budget, I do not recommend Optimizely Web Experimentation, as it becomes quite frustrating to manage usage limits and technical set up to avoid extra charges.
Contentful uses "references" to allow you to build very modular content. If I have a "slider" content type, I can create a "slide" content type which references a "button" content type, and so forth. This works well, but I occasionally wish there was a better solution for one-off content, like a settings page. Currently, this is done for creating an entire content type called "settings" with a single entry. Not a big deal, but not ideal, either.
There are a few quirks with GatsbyJS integration, etc, but these issues are being fixed and improved upon very quickly.
A minor gripe, but Contentful does not have a way to organize fields within an entry. Entries with many fields are somewhat tiresome to scroll through.
Because it's an incredible and essential tool for my line of work as a conversion optimization specialist. Really couldn't do my job nearly as effectively without it. It's paid for itself many times over and I feel like I'm only beginning to unlock the tools potential.
Usability is mostly great. I like the WYSIWYG functionality and adding in real code is simple as well. It's easy to target specific pages or audiences. I've knocked a couple of points off because of how difficult it is to set up URL redirect experiments, confusion around creating pages, and lack of data that can be further analyzed.
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 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.
In the past we've used WordPress to manage documentation content. WordPress was more flexible than Contentful but also prone to inconsistencies and we ended having a lot of hacks to accomplish various WordPress tricks. With Contentful there's less ambiguity so content producers are less likely to go astray. We also have our own in-house programmatic template solution for managing content, but this was a previous pain point when we needed to get the dev team to do a deploy for every content change.
Overall, the tools we compared against were great, but we went with Optimizely because it has all the features we needed and has the market leadership that gave us trust we would be successful in our experimentation efforts.
While granted, I am not the one making the changes to deploy the software; it seems basically as simple as placing the optimized snippet on your site. If you place it in the header, it should reach across your entire site easily. I do think the test setup can be a bit temperamental at times, and having too many cooks in the kitchen can lead to errors. So, I would caution how many people have the access needed to make actual changes.
Customer retention: We've reduced subscription service client churn by 20%+ using optimized unsubscribe flows.
Risk mitigation: Testing into full site redesigns has saved clients millions of dollars.
Feature prioritization: Identifying what painted door changes add value has allowed developers to focus on changes that add hundreds of thousands or even millions to the bottom line.
