Acoustic Tealeaf (formerly Acoustic Experience Analytics and before that IBM Tealeaf; Acoustic has restored the former branding), is an AI powered application providing site visitor session recording and replay, anomaly detection, and struggle analytics.
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.
Tealeaf is a must for any site that has a key business process that drives revenue for a company. It is not limited to only capturing a small percentage of visitors to your site, it captures every visitor to your site. A lot has changed to the last year for Tealeaf for the good. There are many more options to for capturing data including a cloud and SaaS offering. Take a look again if you haven't seen it in a while.
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.
Speed of searching for web sessions and users. This particular feature seems to impress me the most. When researching incidents where users report to have difficulty on our site, all we need is any of the unique identifiers of a user (email address used, IP address, user id) and we can locate their session(s) almost immediately in TeaLeaf.
Multiple conditional events - I really like how we can have events contain already existing events. This helps a great deal if issues being researched become even more complex.
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.
IBM is still working out a solution for seeing Mobile App traffic in Tealeaf. What they have now allows you to see the response and request, but it doesn't show where the customer is actually clicking. They've promised that newer versions will be better with this.
Tealeaf is pushing a web based viewer, trying to make this the standard over the more robust and extremely useful desktop based Tealeaf Viewer. the Web Based viewer is slow and clunky and just not as flexible, but IBM insists on pushing customers towards it. Last I heard, they plan for their mobile solution to only work in the web based viewer.
Recently IBM moved all the support documentation for Tealeaf to the IBM Support portal instead of Tealeaf.com where it has been for years. This completely broke the in application Tealeaf Help. At the time of my last use of Tealeaf near the end of November 2013, when you tried to search help from the Tealeaf web portal, you were sent to the IBM support site, and once you logged in, the search request was lost and you had to start the search again. The search of the help files is also nowhere near as good as the original tealeaf.com help site. Also, if your users tried to use help, they were out of luck because only the Tealeaf Admins have access to the IBM support portal. At first they insisted that they were not going to fix this for older versions of the software, but instead only release a fix when the next version of Tealeaf was release. There was a large discussion about this on the LinkedIn forum and IBM has said they're working on a solution, but I'm not sure when/if that will get release.
Tealeaf is a scalable product that works with complex user-facing environments. It is one of the leading products in the market that helps identify user pain points and increases defect identification. The user interface is simple, clean, and easy to use. Lastly, Tealeaf Support provides good customer service and is eager to help solve chalenges we face along the way.
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.
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.
