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
Contentful
Score 7.6 out of 10
N/A
Contentful is a cloud based CMS solution that provides the ability to manage content across multiple platforms.The editing interface allows for managing content interactively and provides developers the ability to deliver the content with the programming language and template framework of their choice.
$0
Sprinklr Service
Score 8.0 out of 10
N/A
Sprinklr Service is a cloud-native unified customer service platform powered by AI that enables customer and agent experience across 30+ digital, social and voice channels, and delivers real-time insights. Enables customers to interact with a brand on their preferred channel for consistent brand experience. Empowers agents with unified/360 customer view and recommends the most relevant responses with AI to improve agent productivity and experience.…
Adobe Experience Manager, built on Java, means that the pool of developers available to work on the platform is large. Adobe Experience Manager's front-ends and client library management tooling mean that front-end developers can feel at home despite a lack of Java knowledge.
We wanted a CMS which is known in market, which have a good ecosystem. With Adobe Experience Manager, we get integration with Target, Tag management, and other Adobe products.
First of all, I would say the technological advancement it has. AEM consists of a comprehensive web content management system, including more marketing-friendly site templates, easy-to-use developer tools, and AI-powered content generation tools for [a] better customer …
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.
It's a great all rounder for content projects. It's easy in the basics and powerful in the complex, data heavy scenarios. Extending the platform is straightforward and the SDK gives you everything you need. If you have many many varying content types , it gets expensive and perhaps not the best choice .
Sprinklr Service has always been well-suited for all of the work we do. As it's all social media content, and most require responses or escalations, Sprinklr Service covers all of that. The only time I think we wouldn't need it is if we were working with a much smaller client who didn't need us to have eyes on so many platforms at once.
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.
Automated notifications for certain types of content or posts from certain users
The reporting options are fantastic.
We've integrated a chatbot seamlessly with Sprinklr modern care so our team members can pick up a conversation if our bot isn't able to provide an answer.
There are some glitches in permissions inheritance that require us to toggle a save on permissions in groups that inherit from a group that was recently updated.
Large packages require stopping the workflow launcher OSGi components or many workflows will slow down the server.
Locked pages are hard to find unless I use /siteadmin... I often hear that the CQ tools will go away, but if we lose that, some small things might be harder to do, like finding locked pages.
Contentful uses "references" to allow you to build very modular content. If I have a "slider" content type, I can create a "slide" content type which references a "button" content type, and so forth. This works well, but I occasionally wish there was a better solution for one-off content, like a settings page. Currently, this is done for creating an entire content type called "settings" with a single entry. Not a big deal, but not ideal, either.
There are a few quirks with GatsbyJS integration, etc, but these issues are being fixed and improved upon very quickly.
A minor gripe, but Contentful does not have a way to organize fields within an entry. Entries with many fields are somewhat tiresome to scroll through.
I find it difficult to dive into analytics for each social post. The reporting tool gives me an overview of the channels but I would love to look at a breakdown of each post performance.
You currently can't add closed caption subtitles to videos uploaded through Sprinklr so this results in having to revert to the native platform.
I would love to be able to set up a newsfeed that includes posts from a number of our partner accounts, so I can keep up to date with what they're posting.
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.
The biggest reason we renewed, and kept up with Sprinklr Modern Care is because it is an active community and there is customer buy-in already. They continue to update and improve the product, but more importantly, the customers are using it. It's easy to switch products when it's not an active component in your daily structure, but switching and migrating the data or providing alternatives becomes difficult when customers have grown accustomed to a specific experience. As long as they continue to improve the available features and the community stays active, renewed use will continue.
Adobe Experience Manager overall is fairly easy to use and caters to a wide range of users when it comes to their technical abilities. It has the flexibility to enable UI/UX designers to pop in and easily design new content with drop in components. It also has sufficient capabilities for those who are more technically inclined and want to dig more into custom code or solutions
It is a very easy to use and configure application. I find that it is on the user to manage the content after the models have been created, yet I still do not encounter issues finding or creating new components for our site. It is easy to set up and easy to navigate.
I've spent year designing products so I'm a tough judge when it comes to other solutions. It's clear that Sprinklr Modern Care was designed for the average online consumer with a very user friendly interface. They have made improvements to the admin tools to make that area of the product easier to use as well.
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.
No issues with system availability. They manage updates in off-peak hours and I usually don't notice the changes until I log into the system the next day.
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.
Performance is great and is not negatively effecting our processes. We have to make sure it doesn't effect out load times. Not currently seeing any issues with widgets affecting page load times.
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.
I know the Sprinklr conference calls have been helpful, but sometimes submitting a ticket can be a little daunting. In the past, we've included information in screenshots that are then asked for by a member of the support staff. The turnaround time has been between 3 days, which isn't horrible.
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
Basic setup took me less than 30 minutes. This includes initial configuration, putting in the initial content, and getting the look-and-feel customized. The domain routing took the normal lag time any other website or blogging service. The really important thing was to get the user accounts setup and begin seeding the system with content before a public launch.
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
Easy to use and much more organized as a single platform versus multi. The layout is clean and easy to read and we don’t have to worry about certain users safe guarding data or content then losing it when they leave the company. It’s a one stop shop for imagery
First, we had a social studio which was good in terms of functionalities but slow. After that, we had the chance to use Talkwalker & social bakers which were good tools yet not enough compares to Sprinklr
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.
Contentful has saved us valuable development time that was previously spent doing deploys for minor content updates.
Contentful has helped us maintain consistent documentation, reducing time needed to review for consistency.
Can't say we've really experienced any negative ROI impacts from using Contentful, but we've run into some limitations in adding too many content models and the next pricing tier is substantially more expensive.
Increased employee efficiency: Having a clear, one-stop "shop" where users can leave feedback, ask questions, and find bug fixes or workarounds has saved me (and other community managers at my company) loads of time that was once spent responding to numerous emails on an individual basis.
Better customer service: Since everyone in the company is alerted of what's being written on our forum, it's easy to spot a high-priority issue, delegate to the person in charge, resolve it, and respond as soon as possible.
