Check the file. Confirm delivery.
A Digital Asset Management (DAM) workflow that checks advertising files, safely corrects them where possible, and asks a person when needed.
No live files are sent
Choose a scenario, follow the request and open the map to inspect the complete design.
Four starting points. More cases are grouped above.
Happy route
A complete request passes every check and reaches the chosen destination.
JPEG · 1.6 MB · 1080 × 1920
Original preservedRequest history 1 recorded event
One request keeps its original submission, corrections and outcome. These example limits are illustrative, not universal platform limits.
- The person submits the selected file and destination.
Workflow overviewFive stages, plus correction routes
Each return keeps the same request. A temporary service failure retries the same operation within its limit.
Every step in this example 9 steps, including returns
Submit asset
The person chooses a file and its advertising destination in the DAM, then submits it. The system keeps the file details and selections together as one request. A correction updates that same request, preserves its history, and starts the checks again.
In this example: The person submits the selected file and destination. Next: Required details?
Step details & other outcomes
The selected DAM file, its details, and the chosen destination.
Keeps one request reference and records the submission time.
The user has not submitted or saved their correction.
Implementation detail
Keep separate unique references for the file and its destination. Save the original submission time and the time of each later check. The selection list contains choices the person is authorised to use.
Quick glossary Plain meanings for the terms used here
- DAM
- Digital Asset Management: the system used to organise files, their details and approved versions.
- Asset
- The image, video or other file being submitted.
- Metadata
- Information about a file, such as its name, size and dimensions.
- Placement
- Where the advertisement appears, such as a feed or a story.
- Ad set / ad group
- A group inside an advertising campaign. Meta calls it an ad set; Google Ads uses ad group.
- API
- A connection through which one system requests information or actions from another.
- Mapping
- An approved relationship between a business choice and its destination. Direct selections can be checked using their unique IDs.
- Repair attempt
- One approved change to a copy of the file. This design allows two automatic attempts.
- Service retry
- Repeating a failed service request after a short wait. This design allows three retries after the initial call.
- Needs attention
- A request held for a person to resolve. Its correction and return route remain visible.
- Delivery confirmed
- The intended file is present in the intended destination. This does not mean an ad is approved or running.
Design assumptions & capability sources
This is an interactive demonstration of a production system design, not a connection to a live DAM or advertising account. The example uses a single image and destination. Rule values, file changes, receipts, approvals and messages are simulated. The two-repair and three-retry limits are chosen design policies. Human corrections preserve the original request and require a new validation pass. Real deployment requires platform-specific integration, permissions and acceptance testing.