Livefyre was acquired in 2016 and became part of the Adobe Experience Manager suite of products. The product has since been discontinued, and is no longer available for sale.
N/A
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.
I was strictly the implementor of Livefyre (for my company only). That task alone was at least 3 weeks worth of work. From a user standpoint, Livefyre is a good product which is why this review is strictly about how difficult it was to implement. Therefore, if a colleague was to ask me if I recommend Livefyre, it's not a straight answer. Questions like, 'how fast do you need it?', 'how centralized is your user database?', 'do you want social login?', all come into question and were details that made my job not easy (hence, my review of 5/10 for suggesting it to others). Once implemented, Livefyre is a great product (notice my overall review is higher), but based on my experience with implementation, it certainly requires a senior developer's dedicated time and patience to set up exactly as desired. For smaller companies with small/simple user bases and websites, the process may be more straightforward, but from my experience, it wasn't out-of-the-box at all.
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.
Implementation was not easy. Although flexible, I personally wrote at least 1,400 lines of code to get this implemented over a few week's time.
The social login aspect is cool, but again, hard to implement. They did not write any of those modules, although they could have. This required senior-level developmental skills and a knowledge of how social media is interfaced with programmatically. Lots of questions arose from this and it was difficult to implement with virtually no help from Livefyre, other than to provide the hooks into their system for when users were validated. I had to write at least 2 separate login/redirection scripts to accomplish this flow.
CSS tweaking was tricky. We could override lots of common CSS classes, but to get things just the way we wanted it, I ended up writing LOTS of jQuery listeners and functions to transform the output into exactly what we wanted. This was a surprise since the software was sold to us as being 'fully customizable'.
Documentation was sufficient, but not great. Getting the flow of the callbacks that are fired wasn't clear at first, and sometimes did not work as expected.
It should be noted that, after this review was published, Livefyre contacted me stating they now have better documentation and process for implementation (for version V3, specifically) and urged me to revise this review. However, I can only write of my experience with V2, and it WAS difficult to implement over 3 weeks of dedicated time. Another developer on my team implemented version V3 and his evaluation is very similar to mine, claiming much difficulty with the CSS customization.
We feel we have a real partnership with Livefyre and we both make each other better. Their customer service has been phenomenal even during a time of rapid growth.
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
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 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.
We felt Livefyre was more innovative and better at SEO. It felt like we were working with a partner for the long haul who was interested in our business and how to improve it.
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.
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.
