Short answer
An embargo is a restriction that prevents an asset from being used or published before a set date and time. Embargoes protect product launches and announcements. An embargo in a DAM needs a date, a time and a time zone, because a launch at 09:00 in Amsterdam happens at 08:00 in London.
How an embargo works in a DAM
An embargo works in a DAM as a date and time field plus a rule that hides or locks the asset until that moment. At the release time, the DAM lifts the restriction without human action and records the change.
During the embargo, the DAM applies three controls:
- Visibility: only named users or groups, such as the launch team, see the asset.
- Delivery: portals, share links, the API and CDN URLs return nothing for the asset.
- Preview: selected partners see a watermarked preview to prepare their own materials.
At release, the asset appears in search, the brand portal and connected channels at the same moment. The embargo then hands over to the normal asset lifecycle and usage rights.
Example of an embargo
Worked example: a consumer electronics brand launches a new product at 09:00 Central European Time on launch day. The brand keeps launch images hidden from portals until 09:00 on launch day.
Retail partners in 12 markets receive watermarked previews two weeks ahead, so they can build product pages. At 09:00 the DAM releases the clean images to the brand portal and to the PIM feed. Retailers in the UK see them at 08:00 local time.
Embargo in a DAM selection
An embargo is defined at Checkpoint 2: Define and proven at Checkpoint 5: Test with a live timer. Set an embargo 10 minutes ahead during the demo and watch what each channel returns before and after.
Ask each vendor to show these points:
- Set an embargo with date, time and time zone on a batch of assets.
- Open a direct CDN link and an API call to the asset before the release time.
- Give one agency a watermarked preview during the embargo.
- Release the assets at the set time and confirm the portal updates.
- Show the audit entry for the release.
The demo script generator adds an embargo scenario to the script. The rights management guide places embargoes next to licence terms.
Common embargo mistakes
The most common embargo mistake is enforcing it in the DAM interface only, while CDN links already work. A partner who guesses or receives the link then publishes early. Other recurring errors:
- No time zone, so a release fires an hour early or late in another market.
- Manual release by a person who is in a meeting at launch time.
- Confusing embargo with expiry, which needs a separate end-date rule.
Related terms: Asset lifecycle, Usage rights.
Frequently asked
What is the difference between an embargo and an expiry date?
An embargo blocks use before a set date and time. An expiry date blocks use after the licence or release ends. An asset can carry both: an embargo until launch day and an expiry date when the usage rights end.
Can agencies see embargoed assets in a DAM?
Agencies can see embargoed assets when the DAM grants them a named exception. The usual pattern gives the agency a watermarked preview or access to one restricted collection. Test that the exception covers only that agency and ends at release.