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.
N/A
Pendo.io
Score 8.4 out of 10
N/A
Pendo.io is a product engagement platform with features for in-app analytics, surveys and feedback, and guidance.
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.
Pendo.io is useful in generating great dashboards that present user analytics in the best possible view that could be used for analysis & derive key insights on what could be done if there's a feature that's not being recognized by end users or if there are any pain points where users are struggling more around a workflow which is technically not that difficult. Pendo.io also can be used to create impactful guides where intercatoin of a user with the Guide can be created in less steps & have relevant information about that workflow that the user is completing. Pendo.io's resource center can act as a one stop hub to present any sidewide updates which could be information of Prod releases, New KB Articles, Register to any event, & much more. Segments can be created in as many variation as one can. In fact, Segments are the ruling property or feature that works so handy, which reduces a lot of iterative work.
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.
Preview is problematic if the Pendo.io user doesn't have access to the target environment or application where the guide is going to display
It would be ideal to have a gallery of thumbnail images of previously used guides to select from, either to pull a screen capture or to use as a template. It's cumbersome to go to the guides, find the one you want, click on Preview, etc.
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
We have had an excellent experience with Pendo. When we've had questions or concerns, Pendo is very quick to respond and communicate with us. We have experienced top-notch customer support and customer engagement. We have actually modeled some of our implementation and product processes after Pendo's examples.
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.
It is intuitive for core tasks like tracking feature usage, building Guides, and viewing dashboards. The interface is clean and well structured, making it easy for product managers and operational teams to get value quickly without heavy technical support. However, there is a noticeable learning curve when setting up advanced custom events, reports, or integrations, which can take some time and internal knowledge-sharing to master.
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.
Every time I have logged into Pendo, the service has been available for me to use. The page has never been down when I am trying to get info from there.
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.
They've been great anytime that we have needed help with something. They also have some really great help articles. We're able to figure most things out through their articles, but when we've had to call in they've been very helpful and we haven't had any problems. I'd highly recommend working with them.
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).
The training schedule was well thought out and tailored to meet our needs. Chantelle stayed with us through the whole implementation and made sure that we were good to go.
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
I have just very superficial experience with Google Analytics but I do believe that Pendo.io is a much much better tool in pretty much all aspects of it. It has a ton more features and capabilities and even for the capabilities where there is overlap, Pendo seems to come out ahead easily. There are aspects that Pendo could improve for sure such as what metadata it captures from the users; an example of this is screen resolution which Google Analytics captures but Pendo does not.
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.
Reducing development time with in-app guides and resource center, with product management being able to agilely create guides in real time, this could be as much as 1 full time developer in savings.
Reducing business time scoping "rock fetches" than are proven to be invaluable based on analytics, each time 1 single piece of analtical data saves around ~20 hours across multiple resources.
Increasing user satisfaction with in-app guides and resource center
Increasing usage of key features through targetted messaging, those key features either drive costs ou of our business or add value to customers business.
