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 Experience Cloud
Score 8.2 out of 10
N/A
Salesforce Marketing Cloud Engagement (formerly Salesforce Experience Cloud or Salesforce Community Cloud) is an online forum powered by Salesforce that enables businesses to connect with their employees, customers, partner organizations, and prospects. Designed to help facilitate communication and information sharing, customers can ask questions and request help, administrators can integrate data from third-party apps, and employees can collaborate across projects and…
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.
Adobe Experience Manager provides way more. It is a much more holistic tool to help us manage the entire customer Journey. I, however, do not have enough power to make those decisions. I did not in fact choose Adobe Experience Manager, but I do like it better.
Adobe's integration with all of its other products requires digital marketing, making its system stand out from the rest. AI integration takes it to the next level.
I selected Adobe Experience Manager because it was the easiest to connect to our platforms, the best cost for the size of our company, and I was using Adobe for almost everything else at the time. I think this was the best solution for our smaller company at the time.
Yeah, so we've utilized a few different evaluations of products. Most of them are website or WordPress base, intranet, hidden backend applications. It's just because all the data we have already and we have multiple experience clouds, it allows us to leverage SSO or single …
It's one of its kind because other products are worked as an internal user, so whosoever whatsoever product you're using the experience cloud work with any of the other product as well is just external view will provide an external view with any of your product, whether you're …
As our business heavily relies on Sales Cloud, Service Cloud, and Marketing Cloud, we need a CMS that works natively with our existing Salesforce Data. Other platforms would require third-party connectors or custom API development, making integration more complex and expensive. …
Pulls data from Sales Cloud, Service Cloud, and Marketing Cloud to dynamically update content, we didn't want to use too many 3rd party tools that would expose our busines to threats
I used to use WebWave at my previous firm and felt like it was more for website creation rather than content sharing internally. I was also in a different role so I meant my needs at my last firm. My focus has changed and now Salesforce CMS is the best product for my team to …
I love that this is available to compete with Adobe and stay afloat. It's a fantastic tool and product. What sets it apart is the ease of use and the collaborating factor using it within Salesforce. It has kept our organization functioning smoothly and we get a lot more done …
Even just a single administrator can be enough to address the needs of the end users with Salesforce CMS. It provides extensive support for customer service and marketing processes. Salesforce CMS creates highly personalized customer journeys across all communication channels …
I have used Oracle Fusion and it was super slow if compared to Salesforce. The loading time was longer and information was not organized in a simple way like Salesforce. Even though I haven't participated in the decision process of subscribing to Salesforce, as an employee I …
This product is a little bit cleaner and easier to use. It has a better user interface and is more fun. I really like how it operates. It is more approachable for new users and offices that are just breaking into some of these things. I think it works really well in that …
Salesforce Experience Cloud was selected due to its tight integration with our existing Salesforce CRM platform. Customization of the portal was much, much simpler compared to Sharepoint - especially with role-based security parameters that are ultimately inherited based on …
Salesforce Experience Cloud (formerly Salesforce Community Cloud) is better when you are using Salesforce for applications. Drupal is a solid open-source web content management system for internal and external websites, but if you are using Salesforce for services or case …
Salesforce CMS is directly integrated with Salesforce CRM. As part of Salesforce Suite, all the activities of Salesforce CMS are integrated and organized with the information stored on Salesforce CRM, reflecting in a very simple and user-friendly usage of the tool. For this …
Salesforce CMS beats the competition due to UI, user friendliness, support, and ease of use as well as deployment. The entire system and process is simple to understand, has many different places for you to store key information, and is easily implemented at your company. …
We are currently using Vanilla to manage our community (including our knowledge base & ideas), but will be moving to [Salesforce Experience Cloud (formerly Salesforce Community Cloud)] within the quarter. We decided to move forward with Experience Cloud because it integrates so …
Does not have direct access to the Salesforce data, must integrate and maintatin that integration which is costly. Just having a single source login is valuable.
I have used Datatel/Colleague/Recruiter before. There were issues because only one person at the institution was able to have the student's record open at a time. This was problematic when collaboration between departments was necessary especially in the case of admissions, …
Salesforce has a wide variety of services and its user interface was easy to understand and use. Our teams [thought] Salesforce to be better. When we were comparing the features as per our Marketing and Branding teams needs and uses, Salesforce came out on the top.
The Microsoft solutions were used previously, and were probably easier to use since they integrate with windows desktops so well. However, Salesforce is more integrated with mobile and the cloud platform, therefore it is inherently client device agnostic, which is ultimately …
After evaluating others on the market, we found that Salesforce Community Cloud comes with many more features than it competitors. Also Salesforce Community Cloud is way more user-friendly than others. And above all, we were looking for faster sales support in which Salesforce …
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.
HR and Employee Self-Service Portals: Organizations using Salesforce Experience Cloud can leverage Salesforce CMS to create centralized knowledge hubs for HR policies, onboarding resources, and internal communications. Employees can access up-to-date content without IT involvement, improving efficiency and reducing HR’s administrative burden. Multi-Channel Content Distribution: Businesses needing to push content across different touchpoints (web, mobile, email, and customer portals) benefit from Salesforce CMS’s ability to deliver consistent messaging seamlessly. A sales enablement team can publish case studies and product updates on a customer portal while simultaneously integrating content into marketing emails. Personalized & Dynamic Content: Companies using Salesforce CRM can leverage Salesforce CMS to deliver AI-driven, tailored content based on user behavior, preferences, or past interactions. For example, a recruiting team can show custom job recommendations based on a candidate’s past applications.
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.
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.
The documentation for implementing Experience Cloud can be a bit confusing as their rebranding hasn't made it's way into all articles, resulting in different terminology being used to refer to the same thing
Some things are not as intuitive regarding their customizability, so there's a bit of a learning curve (i.e. Lightning apps can't be used to customize layouts in Experience Cloud)
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.
Considering I'm completely self-taught on Adobe Experience Manager, I have to rate usability quite high since plenty of aspects were easy to figure out on my own. With its cloud-based platform, access from anywhere it super great for overall usability. Edits can also be made pretty quick and easy, which is another great feature.
It's very easy to train users on this, even external facing customers. Our users were already familiar with Salesforce user interface since we use the platform for other reasons. We built custom Visualforce pages with a simple, clean layout so we didn't need to train customers. That's ultimately the goal for external facing stuff, that we don't need to train them; they just "get it."
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.
Again, since we provide and recommend solutions, I can't speak to every client's individual experience, but can offer general reflections as to keep their collaborations private, that they are satisfied with the experience. We hear a lot about how this system helps to encourage collaborations between their own business partners, customers, and internal members, and enables quality integrations with other products that help drive revenue.
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.
Although support from Salesforce itself can be quite unresponsive sometimes, the community hub is incredibly helpful. The large user base of Salesforce products contribute to troubleshooting and the forums are a powerful tool for finding solutions and possible bugs and response times can be quite fast compared to your regular support channels.
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
Yeah, so we've utilized a few different evaluations of products. Most of them are website or WordPress base, intranet, hidden backend applications. It's just because all the data we have already and we have multiple experience clouds, it allows us to leverage SSO or single sign-on approach across of our experience cloud. So it's less because all one platform, it's less complex for the end user and less confusing.
