Acoustic Tealeaf vs VWO

• Tealeaf is exceptionally useful for troubleshooting technical issues and investigating conversion problems. It gives you the ability to look at individual sessions, so that you can see exactly what steps the customer has taken to cause the problem. This way you can recreate errors, or determine if the layout of the site is confusing the customer and preventing sales.
• Tealeaf allows you to create alerts to track specific problems. For example you can set an alert if the error handler on the site fires more than 5 times in 15 minutes, or if the completion rate of a specific process drops below a certain percentile. This lets your production support group get a jump on problems and gives them a chance to start working on a solution before the business users or the site help desk have reported the issue.
• Tealeaf allows you to create reports and dashboards to track activities on your site. You can set these up to monitor sales, sign-ups, errors, traffic load, just about anything. You can arrange to have these reports sent by e-mail, so business users can be kept up to date on the status of the web site.
• There are scorecards in Tealeaf that allow you to create reports to track a series of events. This let you see where people are falling out of a process so you can determine where customers are struggling and improve the customer experience.
• It's possible to shadow-browse a customer's web session, allowing a help desk analyst to provide better customer service by seeing what the customer is seeing and following along with their session.

Read full review

• VWO has a strong support team willing to help provide answers to questions during the setup process. During setup, we had some questions regarding implementation across a significant number of sites and they were able to ease dev team concerns and provide detailed best practices to streamline integration.
• Some of the initial results of a few of the initial tests raised some questions internally. We setup a call and were able to quickly address the questions and find some opportunities to leverage moving forward.
• I discovered a bug within the UI that lead to some questions internally. I was able to report it and the problem was fixed rather quickly and their team followed up with a thank you for reporting it and to report the issue was now resolved.

Read full review

• Loading sessions can take time or doesn't work smoothly.
• Visual pages are missing in some sessions which can make it difficult to understand a certain user pain point.
• Segmentation for complex user-facing websites could require initial coding.

Read full review

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

Read full review

• Provides context to developers - As with pretty much any programmer, they need context of user activity leading up to a problem in order for them to debug code. TeaLeaf does a great job of doing that. We can identify a problem in the code, search for a TeaLeaf (and Java application session) that has the problem in it and show the developers what the user was doing when the problem happened. This greatly speeds up the time to resolution.

Read full review

• 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

Read full review