Stack Planning
Digital asset management for marketing
Digital asset management (DAM) gives a marketing team a controlled way to find, review and reuse approved creative files.
Digital asset management (DAM) is a managed repository and set of working rules for a marketing team to store, organise, find, review and reuse creative files. It covers digital files such as images, video, documents and audio, while keeping their metadata and working lifecycle together. DAM becomes useful when a shared folder cannot answer which version is current, where it may be used, who approved it and how another team can find it.
Set up the DAM around the work: choose the assets it will hold, define how files enter and move through the team, then assign responsibility for maintaining them. Day to day, use the repository as the shared starting point for finding and preparing approved material.
Define the asset's working life
Trace one campaign asset from brief to archive. A designer creates a source file, reviewers comment, a final rendition is approved, channel teams adapt it and an old version eventually stops being used. Record who owns each step and what information must follow the file. A DAM can hold versions, metadata and approval states, but those functions matter only if the team agrees what each state means.
Classify the assets that cause the most friction: product images, logos, videos, presentation files, campaign templates or licensed stock. They may need different rights and retention rules. An editable master and a compressed social export are related, not interchangeable. Keep their relationship visible so a team does not mistake the latest export for the approved source.
Make each hand-off explicit: creators supply files, reviewers comment, channel teams adapt material and marketers find or reuse approved assets. Assign an owner to each step and record what must travel with the file.
Workflow for Managing a Campaign Asset in DAM
- CreationDesigner creates source file (e.g., Photoshop or After Effects)
- ReviewReviewers add comments; approval status tracked in metadata
- ApprovalFinal rendition approved by brand manager or marketing lead
- AdaptationChannel teams create versions for social, email, website using approved master
- DeliveryPublished to channels via integrated delivery system (e.g., Adobe Experience Manager)
- ArchiveOld version retired and stored with retention policy; access revoked if needed
Map repository tasks to the workflow
A marketing repository may contain images, video, documents, audio and other media. Adobe Experience Manager Assets describes these as digital files managed in the repository, while distinguishing Content Fragments: structured, channel-neutral content that is managed separately. Keep that distinction clear when deciding what the marketing DAM is expected to hold.
Plan intake as a repeatable task. Adobe Experience Manager Assets supports uploading and importing files from local storage or connected sources, then organising them into folders and collections. Choose a structure that reflects how the team works with campaigns and content, rather than treating upload as the end of asset management.
Metadata can be edited after import to support searchability, governance and downstream delivery. Assign responsibility for maintaining those records as part of the workflow; a central repository only helps teams locate and reuse material when its organisation and metadata remain useful.
Dublin Core is a simple, widely used metadata standard recommended for imposing order on complex digital objects. Choose a consistent metadata approach for the repository and assign someone to maintain it.
Processing can include editing assets, creating renditions and applying transformations. These steps let teams prepare files for delivery while retaining the managed asset in the repository. Decide which processing tasks belong in the DAM workflow and which remain with the creative team.
During routine work, repeat the same sequence for each asset: import it, organise it, maintain its metadata, prepare any required renditions and publish it. Make someone responsible for each hand-off so the repository does not become an upload-only store.
Decide whether a library is enough
For the distinction between an asset library and full DAM software, see the sibling article. This pillar focuses on how a marketing team operates its DAM.
Make version and approval states unambiguous
For version control for brand assets, see the sibling article. This overview leaves that model selection to the deeper guide.
Search quality depends on metadata quality
For testing search and metadata in a DAM demo, see the sibling article. This overview focuses on day-to-day repository operation.
Keep permission to reuse beside the file
For licence tracking for reused marketing assets, see the sibling article. This pillar keeps that subtopic at the hand-off level.
Compare systems with the same evidence
Adobe Experience Manager Assets is a centralised DAM system, and Canto is a DAM platform designed to centralise brand assets and workflows. These are named examples, not a ranking; compare candidates against the same marketing tasks.
Use one sample set and a short task list across candidates: import and classify, search, revise, approve, share externally, revoke access and export with metadata. Record the specific plan and configuration shown. Note where the team needed a workaround, administrator action or manual spreadsheet. Do not call a sales demonstration a completed production test.
The result should be a decision about operating responsibilities as much as features. Name the metadata owner, approver, rights contact and person who retires old files. Also identify which DAM administrator supports repository management and which content creators provide files.
Key Features of DAM Systems: Adobe Experience Manager vs Canto
- Centralised Repository
- Yes – both systems support centralised storage of digital assets
- Metadata Management
- Yes – supports Dublin Core standard and custom fields
- Version & Approval Tracking
- Yes – tracks revisions and approval states across workflows
- Multichannel Delivery Integration
- Yes – integrates with CMS and marketing platforms for channel publishing
- User Access Control
- Yes – granular permissions for teams, roles and external partners
- Licensing & Rights Tracking
- Limited – requires manual input or third-party tools for full compliance
Connect management to delivery
Publishing is a distinct part of asset management: Adobe Experience Manager Assets describes publishing and delivering assets to the channels and experiences where they are consumed. Map the hand-off from the repository to each marketing destination so teams know where to obtain material intended for use.
A central repository can support creators, marketers and reviewers working with the same governed content. Adobe describes centralising assets and metadata as a way to help teams locate approved material, avoid recreating existing files and use current versions across channels. The practical benefit depends on teams using the repository as their shared working source.
Make the repository the normal starting point for asset requests. When a team prepares material for delivery, follow the agreed hand-off to its destination and keep the managed asset as the shared reference.
In this guide
- Comparing asset libraries with full DAM softwareCompare an asset library with a full DAM by the work people need to do, not the product category on the invoice.
- Evaluating version control for brand assetsVersion control for brand assets should tell users which file is approved, what changed and what to do with copies already in circulation.
- Testing search and metadata in a DAM demoTest DAM search with representative assets and questions from people who will use the library.
- Checking licence tracking for reused marketing assetsBefore reusing an image, video, font or illustration, check the permission attached to that specific asset and intended use.
