Adobe Experience Manager is a combined web content management system and digital asset management system. The combined applications of Adobe Experience Manager Sites and Adobe Experience Manager Assets is offered by the vendor as an end-to-end solution for managing and delivering marketing content.
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'll answer the second one because I mean, the first one I don't have an issue with. The second scenario is we oftentimes have the need to spin off very small campaign style sites or sites that generate leads but are unbranded and that sort of thing. So that's hard to do in AEM because you have to then create another organization within AEM to do that. And we're talking about sites that are maybe five to 10 pages in size. So we've been investigating Edge, but then that's a different workflow, so we'd have to train people on that. So it would be nice if there was something within the AEM structure that could allow you to do something very similar to Edge, where you make some small micro sites that are not necessarily branded, that you could still host within the platform and not have to retrain everybody on a completely different platform.
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.
It allows us to scale so that we can make a change on a global footer. And it applies to all of the different property websites. It allows us to set up components and compartmentalize things in a way. The big thing is that it's scalable. And then it also ties into Adobe Analytics and other Adobe products. So we are a complete Adobe shop. Every Adobe product that we can use, we use. I don't think we do it for marketing so much, but for doing target testing and analytics, data scientists are using the same product and so it all speaks.
Can sometimes be difficult to troubleshoot bugs/issues as they arise
Sometimes difficult to set up restrictions on how components can be designed to make sure they fit in with existing content
While the integration with Adobe target works fairly well, the process can be a bit opaque and hard to understand, making it difficult to troubleshoot when issues arise
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.
We had and still have a fantastic experience using Adobe CQ. Lots of flexibility, great integration with other Adobe products we already use and a powerful technology make it a great fit for our corporate environment. Also as the community grows, it makes it easier to network with other developers and users to get new ideas on how to continue to get the best out of the software.
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.
It depends if it is from an administrator point of view or from a business content author point of view. I think from business author point of view the solution is good and with the GEN AI capabilities coming it is doing better and better, however from an administration point of view there are still a lot of improvements to ease the maintenance of user access management and as well as the integration configuration aspect.
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.
Being part of Adobe Suite means you are already notified when the tool has any outages. However, I have never faced unplanned outages. Whenever you face any issue with the site, it is clearly stated if there were any planned outages and how quickly you will be back to normal. So, I will say that even the outages are planned and managed in a great way like their other services.
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.
With respect to performance, Adobe experience manager is one of the best in the CMS space. We didn't observe frequent slowness on platform, however the systems which are accessing experience manager should be of good specifications without which slowness would be observed. Adobe experience manager works well in integration with other solutions, unless the destination application is designed to trigger frequent calls to AEM.
Adobe Experience Manager, in all its capacity, is a great alternative to any other CMS you are using. It helps in rapid development and makes life easier for maintaining the website for multi-language sites. Technical know-how is eliminated at content authoring. Better documentation in terms of live examples with videos would be appreciated.
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 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.
Depending on your individual needs, It is really quite simple to create an authoring experience for a website that looks really good. I have been part of many implementations and many teams and have seen many projects that were super successful and others that were not implemented well. AEM has room for a lot of flexibility in the implementation process compared to other CMS like SharePoint
Overall, I prefer AEM as an enterprise site management tool. It allows levels of access control and delegation, while leaving the server management and updates to a specialized team. I do miss the flexibility of being able to search and replace that I have in a WordPress site, and I miss the ability to have one file for redirects like I had in percussion
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.
Instead of being directly involved in the tool purchase, I am involved in analysis or what we can use to maximize the tool. Small organizations may find it expensive. However, if the team or organization focuses more on your ROI or the features you will get, then it will definitely be worth it. Pricing is based on a number of factors, including team size or the use of the tool. The user can select the pricing option that best fits their needs based on the number of form submissions they make or the number of pages they wish to publish on their global/multisite sites.
The professional services team within adobe is one of the best in terms of technical and solutioning knowledge. However, considering the billing charges of adobe professional services team, it is always recommended to involve them during platform initial setup or when a complex solution is to be built with platform customizations.
too soon to tell on increased conversion rates based on external marketing factors in play but having increased visibility into customer engagement trends will most likely lead to improvement of our conversion rates.
There have been productivity gains from the perspective of actually migrating all of our externally managed sites to the same in-house Adobe Experience Manager platform and then being able to utilize those universal components.
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.
