Acquia DAM (Widen) helps brands manage and distribute assets across teams, tools, and channels. A configurable metadata schema provides business-specific search and workflow capabilities. Plus, AI-powered auto tagging makes assets instantly findable. Content can be synced across systems using the API or pre-built integrations with over 50 tools, from creative suites to project management. Product-based companies can use Acquia DAM to build a unique 360º view of their product content. It…
N/A
Adobe Experience Manager
Score 8.0 out of 10
N/A
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
Pricing
Acquia DAM (Widen)
Adobe Experience Manager
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Acquia DAM (Widen)
Adobe Experience Manager
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
Required
No setup fee
Additional Details
Guided or full-service implementation options and annual subscriptions based on capabilities required. Workgroup and unlimited user options available. Storage with Amazon Web Services.
Professional services available for strategy consulting, change management, administration services, design services, and managed integrations.
We decided to stick with Acquia DAM (Widen) in the short term but will be reviewing the options this or next year to better integrate with Social, Web, and Creative team needs. We use Sitecore for all our web services, so it needs to be compatible with that, Social also needs …
Acquia DAM (Widen) had all the features we needed at a price that was not unaffordable. Also, having unlimited users and Admins is something few others have.
There are a number of features that competitors provide that I would love to see incorporated into Acquia DAM (Widen) but the pricing for Acquia DAM (Widen) is the best value for us.
Verified User
Account Manager
Chose Acquia DAM (Widen)
Acquia DAM (Widen) offers a specific set of solutions in the Experience management landscape.
Bynder was our solution and we just didn't see any innovation over the last couple of years. AEM is where we house technical documentation, but we need a more capable DAM, not just a place to stick PDFs. MediaValet was close but we just felt Acquia DAM (Widen) was a bit more …
While I was not involved in the selection of Acquia DAM (Widen), as a previous user of AEM, I find Acquia DAM (Widen) to be much more user-friendly and functional out of the box. AEM seems to allow a higher degree of customization but requires a higher development cost. While …
I inherited Acquia DAM (Widen) when coming into this role 2.5 years ago. The search functionality and AI-driven data layer is much more intuitive with Brandfolder. There is a lot of manual metadata entry in Acquia DAM (Widen) that is cumbersome and often ignored, leading to a …
Acquia DAM (Widen) seems to have much more experience with a DAM than Adobe currently does. Also, AEM is used more for web content while we are focused on a solid working DAM right now.
Widen is a great digital asset manager internally. I loved the framework that the platform has. However, we created a main portal to share with our external partners so we could control what was private and what was public. The portal framework was not as user-friendly and we tried too much to make it like a website when it was meant to be a DAM. The main reason we switched providers is that we wanted to have the option to have a consistent framework internally and externally that was more user-friendly with better search capabilities.
Adobe Experience Manager allows web content managers to share the work of site maintenance while being able to set access/publishing. Editors don’t need to have advanced HTML experience to make edits or even build new pages. Having workflows to allow authors/editors to request publish gives content managers the ability to review content before it is made public. Being able to set on and off times for pages helps control when content is released and retired. AEM is not ideal for highly specialized and customized designs with lots of interaction/automation
They offer valuable guidance and educational resources to Administrators
Their I.T. support is knowledgeable and responsive. And friendly!
They build community among Acquia DAM (Widen) Admins
They aren't as salesy and pushy as many of the other DAM Vendors that we considered. I don't feel like they are constantly trying to upsell me or take advantage. I hope this continues to be the case with the acquisition by Acquia.
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.
Improvements in the cropping and editing features within Acquia DAM are essential to ease the workload for our graphic designers. The current functionality falls short in providing the necessary tools and precision required for efficient asset manipulation, not helping with that time management at all.
Enhancing the onboarding experience, we propose creating more video tutorials for Acquia DAM. These visual guides, covering topics from account setup to collaboration features, offer dynamic, step-by-step learning.
To improve the onboarding experience, we recommend expanding introductory tools and templates in Acquia DAM. Introducing more user-friendly features and providing a variety of templates will empower new users to navigate the platform with ease, fostering quicker proficiency and enhancing overall usability.
It's still, at the end of the day, a very traditional platform in by that we mean it's a bulk air platform. There are too many components, which means a lot more operating costs in terms of manageability and things like that. We have tried to streamline that as much as we can, but the multiple components still exist. If anything, Adobe could kind of think about that a little bit to maybe decouple some of those and make them a more slimmer platform. I think that would help. I think that a lot of customers are still in the traditional environment and as we ourselves are looking to move to the cloud, I think some of that will get taken care of, but I think that's one area where it would help if Adobe can put some thoughts into that.
Acquia DAM (Widen) is changing its pricing model and at this point, we are unsure whether it is a good thing for us or not. While we consider this a robust tool, we will take our time to evaluate the competitors.
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.
We used to have to respond to any email questions from our library users about how to find assets. With Acquia DAM (Widen), the system is similar to online shopping, workable with keywords for those who like to search that way, or with filters for those who like to browse.
Adobe launched the Touch UI experience a few years back, I think it's been four to five years now. I didn't see much improvements in terms of usability. So there's definitely there's room for improvement there, especially around our authoring team. They really struggle when it comes to finding things in them or navigating easily to pages. It's always a struggle for them. I think the overall authoring user experience, the way authoring UI, the way it is set up, can be optimized. I think in its current state, I don't think it's that well set up. It can definitely be redesigned for sure.
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.
There have been a couple of rare instance where after I uploaded an asset, I was unable to rename it, or after uploading it it took a while before it actually appeared and can be viewed in the DAM.
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.
It's very seldom that I have to reach out for support, but when I have, there are quick solutions and follow-ups to make sure the system is working how it should be. My customer support team is also great at reaching out on a regular basis to keep me up to speed on emerging features I may be able to leverage to improve my experience.
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.
The training was very thorough. The recordings for all our traning sessions were provided to us so that we could go back and review. Our trainer was always available for follow up questions. Our trainer shared a spreadsheet with us as a checklist for all things that needed to be done to ensure proper import and setup of our assets and DAM.
It was a lot of work! But worth the effort to get our assets cleaned up and organized. Enough time and personnel need to be allotted for any implementation, but we had some advantage in having our assets in a previous DAM with attached metadata in XML, and our users were prepared with knowledge of our existing DAM at that time. Though old habits present their own issues, a company that is starting from scratch with no DAM has to think farther ahead about how it will organize and collect assets. Far more pre-planning with stakeholders would be needed for a company starting an implementation from scratch.
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
We decided to stick with Acquia DAM (Widen) in the short term but will be reviewing the options this or next year to better integrate with Social, Web, and Creative team needs. We use Sitecore for all our web services, so it needs to be compatible with that, Social also needs to integrate but is not fixed on a single system, but Canva would be a good fit. The creative team always prefers local storage to link to rather than the cloud due to speeds.
At Canadian Tire Financial, in the time I've been there, we've always used AEM, but in past places I've used WordPress, I've used Squarespace. Things that are more general user-friendly where you're like building your own blog or you're creating a small business website where it's basically just text, you're not intaking information or something like that. I think the customization options in AEM are huge. My experiences with WordPress were pretty straightforward. Again, it was like, I don't know, like college newspaper website or something like that where you're just like putting content up for people to look at. You're not necessarily taking in any other information. Maybe you might allow people to log in or something and save articles or something pretty straightforward, but then even then I remember that stuff taking me forever to do, to figure out and scroll through tons and tons and tons of documentation. It's just not fun. No one enjoys doing that and then even then you might not have the answer available to you. And that's so frustrating. Hey, it's super user-friendly, figuring out the content editor is pretty straightforward. You're not clicking around and being, "what the heck am I looking at?" Or you're not looking at a bazillion menus to be like, "maybe the thing I want is in here." I can't stand that. I want to be able to look at a page, see what I'm going to be getting in production, and then publish it. I don't want to look around in menus to figure out how to add something to a page.
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.
The Acquia DAM (Widen) helped our company transition more quickly to remote work, giving users access to files much faster than the company servers could.
The Acquia DAM (Widen) has given non-web devs the ability to quickly build clean web pages that share out marketing resources and information.
Well I can't speak monetarily but I can say it's allowed us to get some sites out and messages out very quickly. We've been able to stand up some sites incredibly under very tight timeframes. Messaging, especially during the pandemic, we were able to not only get information out about COVID, we were able to get messages out to the general population about information about their insurance, about issues that were happening, how to find test sites, how to find test kits, how to find information about your insurance, how to get information about storms or anything happening. So we found it was able to get up messaging very quickly and turnaround sites pretty fast. Once we got rolling on it, we were able to do it and we found that it was just able to get that messaging and sites out very fast.