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
Salesforce CMS
Score 8.4 out of 10
N/A
Salesforce Marketing Cloud Personalization (formerly Salesforce CMS) is a hybrid CMS allowing users to author content once and deliver it anywhere, in or out of Salesforce. Users create content, define content access, and define channels so they can share content and limit access to appropriate contributors. For an experience built with Salesforce, users can choose from two of the company's “what-you-see-is-what-you-get” (WYSIWYG) tools: Experience Builder and Commerce Page Designer. If the user…
N/A
Pricing
Adobe Experience Manager
Salesforce CMS
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Adobe Experience Manager
Salesforce 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
Salesforce CMS
Features
Adobe Experience Manager
Salesforce CMS
Security
Comparison of Security features of Product A and Product B
Adobe Experience Manager
8.4
Ratings
2% above category average
Salesforce CMS
10.0
Ratings
21% above category average
Role-based user permissions
8.40 Ratings
10.00 Ratings
Platform & Infrastructure
Comparison of Platform & Infrastructure features of Product A and Product B
Adobe Experience Manager
8.0
Ratings
4% below category average
Salesforce CMS
10.0
Ratings
27% above category average
API
7.80 Ratings
10.00 Ratings
Internationalization / multi-language
8.10 Ratings
10.00 Ratings
Web Content Creation
Comparison of Web Content Creation features of Product A and Product B
Adobe Experience Manager
7.5
Ratings
2% below category average
Salesforce CMS
10.0
Ratings
26% above category average
WYSIWYG editor
7.40 Ratings
10.00 Ratings
Code quality / cleanliness
6.70 Ratings
10.00 Ratings
Admin section
7.00 Ratings
10.00 Ratings
Page templates
7.60 Ratings
10.00 Ratings
Library of website themes
7.30 Ratings
10.00 Ratings
Mobile optimization / responsive design
7.80 Ratings
10.00 Ratings
Publishing workflow
8.10 Ratings
10.00 Ratings
Form generator
7.60 Ratings
10.00 Ratings
Web Content Management
Comparison of Web Content Management features of Product A and Product B
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.
If you have a large customer base and a large amount of data on each of your customers, it is really strong in creating personalized content that your salespeople can use in their pitch meetings—and then setting up workflows for automated for lifecycle journey creations to automatically go out to customers.
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.
Easy to use, just like Salesforce's other products. Many users can sit down and figure it out in no time, and with a little training become power users.
Fast and secure - Salesforce is a leader in the cloud world so you get consistently fast results and security that is top notch in the industry.
Accessible from anywhere - if you use cloud CMS already this is a no-brainer, but for those that do in-house CMS still, this is a major difference. Mobile access from anywhere on the planet without a VPN is something you just can't do without the cloud.
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
Organizations that are new to Salesforce need to be prepared for report building and other configurations. Customization is a great feature, but it can be overwhelming if not impossible for a brand new user.
Salesforce Trailhead is robust but can be confusing and overwhelming.
I'm currently comfortable with only using Salesforce CMS or any iteration on a desktop.
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.
It will be too difficult to change to a different software. We are fully integrated, and if things are not working well, it would be way worse to try to move to a different platform.
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
Strengths: - Intuitive for Salesforce Users – If you’re already working within the Salesforce ecosystem, the Salesforce CMS is easy to navigate, with a clean UI, drag-and-drop content management, and reusable assets for quick updates. - Seamless Integration – Since it connects natively with Experience Cloud, Marketing Cloud, and CRM, it allows for efficient multi-channel content distribution without needing extra third-party tools. - AI-Powered Personalization – The ability to deliver dynamic content based on user profiles and engagement data is a huge plus, making content delivery more relevant and impactful. Challenges: - Learning Curve for New Users – If you're not already familiar with Salesforce, the interface can feel overwhelming, requiring training to fully leverage all features. - Limited Customization & Workflow Automation – While it works well for structured content, advanced approval workflows and deep editorial customization are limited compared to enterprise CMS platforms like Adobe Experience Manager. - Media & Design Limitations – Salesforce CMS is not as robust for managing rich media-heavy content, which can be frustrating for teams needing more flexibility in multimedia presentation.
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.
I've never really had to contact support. It's at the point where we have people in the organization that are our specific go-to inhouse support teams for Salesforce. Again, that goes back to what I said about there being a point where just too much is added to Salesforce that you have to hire someone to be the go-to person of Salesforce. There is only so much their support team can do for you. I wouldn't expect Salesforce Support to have any sort of understanding of the weird issues I deal with!
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
Salesforce CMS is way better with both optimization and reporting both of which Sonar Scheduling lacked. Our ability to skill technician or prioritize was lacking with Sonar. The API was very delayed with Sonar so changes on the Gantt had a delay that would throw off other team members. Sonar was cheaper but Salesforce CMS is way more capable.