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
OpenText Web CMS
Score 5.0 out of 10
N/A
OpenText
Web CMS (TeamSite) accelerates and simplifies the end-to-end digital content and campaign
lifecycle, from content creation and rich media management to omnichannel
publication, optimization, automation, commerce, and community. According to the vendor, with
TeamSite, users can:
Capture diverse digital
audiences with amazing brand experiences – Give customers and prospects consistent, high-quality brand
experiences across devices and channels, and foster closer…
N/A
Pricing
Adobe Experience Manager
OpenText Web CMS
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Adobe Experience Manager
OpenText Web CMS
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Adobe Experience Manager
OpenText Web CMS
Considered Both Products
Adobe Experience Manager
Verified User
Anonymous
Chose Adobe Experience Manager
End to end capabilities as well as integrations with upstream and downstream systems to make work flows, easier and faster time to market
SSO is one fits all, so we don't have to have a separate SSO for each application of Adobe The integration with Analytics works perfectly and bring directly value really quickly Target remains more complicated to set up, but can also bring a lot of value once integrated with …
Adobe Experience Manager is what I use most frequently. While the other tools I listed above are important, they are ultimately a secondary tool utilized on a need by need basis where as AEM is what we use daily for content creation, content updates, content optimization, etc.
AEM is comparable to Sitecore and less agile than Bynder, but Adobe products were already being used across the org and adding AEM allowed us to link it all together.
It offers more content editing features at a relatively low cost thus overall deployment is lower in cost. It has great customer support who are always there to support and answer to our needs thus making the process of deployment seamless at every stage and offering training …
OpenText TeamSite has been more powerful and resourceful as compared to Storyblok. The cost of deployment was relatively low and it has more content editing features. The customer support team members are always online 24/7/367 and they offer the best training of working with …
It offers an intuitive user experience, modern, versatile and consistent in performance. It simplifies the whole process of managing the digital experience across all marketing channels, which is done from a unified interface. This tool has enabled us to take control of our …
OpenText went through an RFP process against IBM Content Management back in 2012. OpenText not only met our business and technical requirements, but we asked both vendors to show a use case and OpenText provided an extensive solution that IBM could not. Also the content …
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.
OpenText TeamSite is well-suited to large, enterprise-wide implementations where customization, content governance, and dynamic content distribution is needed or prioritized. It is probably not ideal for smaller sites with simple architecture and few resources to manage custom implementation.
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.
easier way to make universal changes for multiple websites at a time (ie pushing out a new experience fragment to all as opposed to having to individually add to each site)
easier way to get site images to look and be sized exactly as I want directly from the site page editor
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.
Sure there are a few quirks in the interface, but once you learn them, building and editing pages is fast and efficient. Once you have the content and the planned design decided (how the pages will look and which components you will use), page builds and publishing are quick. I was able to build a 10-page specialized site with cards built using the list component in an afternoon
Overall, it's a solid package with the potential to offer much functionality with appropriate resources applied. There are a few issues with the authoring interface that OpenText should address before its a top shelf authoring experience.
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.
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.
Our technical resources engage with OpenText TeamSite so I don't have direct experience. However, critical issues that we need help with seem to get the attention they deserve without issue. However, training and user resources for business owner roles are a bit lacking and some annoying issues with the authoring interface should be addressed sooner.
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
SSO is one fits all, so we don't have to have a separate SSO for each application of Adobe The integration with Analytics works perfectly and bring directly value really quickly Target remains more complicated to set up, but can also bring a lot of value once integrated with the rest of the Adobe platform The fact that the solution is Cloud services is also a big advantage for maintenance
It offers more content editing features at a relatively low cost thus overall deployment is lower in cost. It has great customer support who are always there to support and answer to our needs thus making the process of deployment seamless at every stage and offering training for working with their product.
We integrated with google analytics, now we have the proper comprehension of our audience data reception and behaviors - we've greatly improved on personalized marketing.
Quick publication of content across the main digital channels.
We run our digital campaigns swiftly.
We've maintained our brand consistency for three years.