Overall Satisfaction with Acquia DAM (Widen)
Tempur Sealy uses Acquia DAM (Widen) to organize and distribute its creative assets. The US has been using it for some time, and I am currently implementing a structure for Roles, Permissions, Metadata, Categories and introducing Portal use for the International Division. Tempur Sealy International works with various agencies to produce Marketing and Creative assets. I am onboarding as many agencies as possible to be able to deliver final assets directly to our Acquia DAM (Widen) Collective, which are then processed internally and released as appropriate. Once Phase 1 fundamentals are more established, I aim to integrate localized assets created by our numerous International Markets, which are currently created and stored in local silos. Longer-term targets are to deliver as much automation and integration with our current MarTech stack as possible, and longer-term PIM aspirations.
- Once the structure is planned and implemented, metadata functionality allows for robust search and filtering
- Asset organization options facilitate more than one way for users to find what they need. Once any complexity in planning and configuration is complete, with clear guidance the user experience is simplistic enough to increase chances of engagement and adoption
- Customer Success Managers, Live Chat Support, and Acquia DAM (Widen) Connect all combine to provide a real wealth of material to lean on while in the early stages of planning your Collective, and refining for continuous improvement once things are live
- I would like to see an Admin client which provides more flexibility in editing multiple assets' metadata and personalization of the system
- System configuration I'd like to see opened up a bit is exemplified by the inability to change certain field names like 'Title' in the user registration form. It would be much clearer and result in the correct info arriving if I could change it to 'Job Title'. It would also mean I'd only have to address users with incorrect info after changing the field name. Currently, I need to add a new field called 'Job Title' and migrate all the existing user data from the field named 'Title', before removing the field named 'Title' from my site's Access Request form.
- I would like to see the ability to simply share a search result that's been filtered. Currently, you have to configure an Advanced Search that replicates your filtering and share that. It seems as though there ought to be a way of sharing your search result with other users far more simply in one or two brief stops.
- A 'pinboard' feature would be very useful. Collections can be used, but a simpler way to drag assets in an ad-hoc fashion to form a pinboard of various assets to share or download would be very useful
- Further layers of metadata dependency, beyond the 2nd level currently available, would be useful
- Structure afforded by controlled vocabulary metadata
- Portals allowing curation, and effective 'spoon feeding' of assets
- Roles and Permissions allowing different user groups different access across all of our assets
- With no real structure to the International division's assets, user engagement and opinion of the platform was very low
- By introducing a more robust site map, to leverage improved Metadata, Categories and now Portals, we have started to deliver our biggest ever product launch with positive feedback from many Markets and internal users
- By leveraging the standard functionality we have been able to strategically share our new product assets and plans far more consistently and quickly than ever before.
I plan to leverage as much automation as possible and utilize the Comment, History, and Versioning features to implement a trackable proof and approval process within the system. I'm also keen to establish the use of embed codes that were apt and investigate what PIM integration options are available.
Coming in to deliver a useful Acquia DAM (Widen) system some years after it was first implemented, I found the CSMs I worked with (Frankie Buckle and Kaia Weber) incredibly helpful and knowledgeable. Similarly, the online chat and email support have always been prompt and helped me make decisions even when a solution wasn't possible.
Portals have enabled us to take the first steps towards more complex solutions, by confidently curating and delivering specific assets via a simple and clear UX. I expect user confidence and adoption to continue growing now and am therefore confident we can deliver more wins based on what is now a far more robust metadata foundation.
In my experience, censhare was far more flexible and configurable than Acquia DAM (Widen) and offered more extensive solutions than the more 'pure DAM' extent of Acquia DAM (Widen). censhare is what's often described as a Headless CMS, and integrated Product Information Management all in one platform.
Do you think Acquia DAM (Widen) delivers good value for the price?
Are you happy with Acquia DAM (Widen)'s feature set?
Did Acquia DAM (Widen) live up to sales and marketing promises?
I wasn't involved with the selection/purchase process
Did implementation of Acquia DAM (Widen) go as expected?
Would you buy Acquia DAM (Widen) again?
For out-of-the-box functionality, Acquia DAM (Widen) is well structured, with lots of features to help you organize and distribute assets. Support is provided from several angles and is very good in my experience. I would like to see more flexibility for configuration and personalization in terms of what the Admin user can get the system to do without having to submit feature requests. It would also be useful to have more than just a second level of dependency currently available in metadata structure.