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 7.9 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…
N/A
Pricing
Adobe Experience Manager
Salesforce Experience Cloud
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Adobe Experience Manager
Salesforce Experience Cloud
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 Experience Cloud
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.
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 …
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 …
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, …
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 …
Before Community Cloud, a common alternative was the development of web sites externally with integration to Sales Cloud being made from external API calls. This is a far costlier and more complex endeavour since it requires a dedicated development team to create and maintain …
Associate Director, Client Leadership for Michelin
Chose Salesforce Experience Cloud
Overall, Salesforce is the most effective solution since it is part of an integrated stack to house and activate CRM audiences within an email, but also expand upon it via the DMP. This can allow for cross channel reach and exposure frequency measurement. If we were to partner …
Salesforce has highly customizable lead management and scoring, while HubSpot can get small businesses up and running quickly with lead generation via content marketing. HubSpot is unique in its focus on inbound and content marketing—in fact, that's at the core of what the …
As our client already used Salesforce CRM, it is a simple integration tasks to link Community to CRM. As such this was a quick deployment with the base data already being present and easily linked to.
I’m sure Salesforce does this as well but we were able to create many macros for Zendesk, that helped our agents interact with customers on a very consistent basis. We haven’t quite got that far in our organization, but I do think it would be useful to our agents.
Other online community forum software vendors include, HiveBrite, ForumBee and Memeni. the main competitor being HiveBrite. Additional tools with chat functionality may also include Slack which i have used. Having th ability to create groups by product / team / region etc.
We have only ever used a different internal program that was custom built by our web team. It was not functional with Outlook and all the other systems we use daily. Salesforce is our central hub for everything!
Community Cloud is directly connected to the database (Salesforce), so there is no need for a 3rd party or an API to bring systems together. This means that CRM users can see all Intranet items from Salesforce directly. It's also extremely straight forward in use, but can be …
I did not select Community Cloud, but since we had the Salesforce platform it was preferred to use this instead of Office 365. I currently use SharePoint at my new organization and there is a much higher level of participation, customization, storage, and synchronicity among …
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.
[Salesforce Experience Cloud (formerly Salesforce Community Cloud)] seems to be very well suited for what we want to use it for, which is to allow customers to have access to their ongoing and already-resolved cases, which will save our customer success team time and allow for transparency. It also seems well-suited for fine-tuning knowledge libraries, as it allows you to track the knowledge articles that are most impactful (and conversely, those that are less impactful) as you are able to track the path that customers use to self-serve ahead of submitting a ticket. I haven't run into any scenarios yet where we wanted to use Experience Cloud as a solution but discovered that it wasn't a fit.
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.
Complete integration with the Salesforce ecosystem. Data displayed in your Community portal reflects records from a Sales Cloud organization
Highly customizable. A Community Cloud portal can be totally customized both visually and with different funcionalities with little to no coding skills required
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
None that come to mind - integrations, experience, and use is great! However, if you're trying to learn it yourself, you may benefit from consulting an expert. Or, if you're wondering if it's good for you, a business analysis will suit you well before you implement to save yourselves, time, money, efforts, and even people.
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
Usability is pretty streamlined, especially if you're familiar with other Salesforce products, but even if not, take it from me, as I just entered the technological space about two years ago, that this product is pretty simple to learn. You don't have to jump in with your head underwater. Small wins and learnings along the way are what foster long-term understandings and enable your evolution alongside the product. I definitely recommend Salesforce Trailhead along with 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.
Through ease of use and expandability, I think that Community Cloud is a best in class at exposing Salesforce integrations, as well as expandability in working through building custom add-ons for Salesforce for collaborations and self-service. Additionally, the speed to market on these changes are lightning-quick and allow for experimentation.
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.
We have weekly calls with our Salesforce reps. They bring new ideas to the table and help with taxonomy builds. They have also answered many questions and connected us to the right people for us to grow our knowledge and utilization of the platform. They are a good partner overall in comparison.
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 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 attributes within the Salesforce CRM platform. Salesforce Experience Cloud was a natural fit for this customer-facing purpose.
Its given us much better issue and customer satisfaction tracking, since before Community Cloud much of our communications were extremely siloed within Outlook. We had no visibility because communications happened on an individual basis rather than a holistic level (the company).
We've increased user interaction and given our customers a reason to come to the website repeatedly.
Our costs have gone up, naturally, as the system proves to be a strong solution. We have pulled in other resources and teams which requires more licenses. I guess that's a sign of success but also a cost.