Webdam makes it easy to share assets in your DAM or embed those assets in a web page or email. Your core assets will remain secure inside the DAM, but admins and contributors have access to links that can be used or shared externally. Some common uses of these links include:
- Using images in custom HTML elements of your Brand Connect
- Creating a gallery on an external website
- Sharing quick previews with business partners
- Creating an email with images from the DAM
Note: Some features are only available to enterprise edition customers.
To share a link or embed an asset:
- Log into Webdam.
- Double click an asset to see its asset details page.
- Click the get links icon
in the actions toolbar. The Get Links window will display the following links:
-
- Page Links
- Direct and Embeddable Links
- Direct Download Link
- Public File Links
-
Here’s how they work:
-
- Page links: Links to the asset details page. The Brand Connect link points directly to the asset on your Brand Connect and the Webdam Admin link points to the asset in your Core Library. Users who click the link will need to log into Webdam and have group permissions to access the asset.
- Direct link: Links to a preview of the asset in the browser. People who click the link will be able to save the asset and are not required to log into Webdam to view it. You can choose the maximum pixel size for this preview before sending by selecting a value in the Embeddable size section. The direct links can be used on most external platforms, but Webdam does not track usage data.
- Embeddable link: HTML code that embeds the asset into a blog, website, etc. You can choose the maximum pixel size for this asset before embedding by selecting a value in the Embeddable size section. You do not need a Webdam login to view the asset. The embeds can be used on most external platforms, and Webdam tracks download data in your reports.
- Direct Download Link: A link to the original asset. An external user will not need to login to access it. By default, direct download links don't expire. If necessary, you can click the Expiration dropdown to set the expiration for the asset.
No expiration
The direct download link won't expire.
Set date
Use the date picker to set the expiry date for the direct download link.
Expire with the asset
Select this option if you want the direct download link to expire at the same moment as the asset expires. - Public File Links: This link functions as the base URL, which you can use to create Dynamic Asset Transformations (DAT). Read more about about Dynamic Asset Transformations.
- Page links: Links to the asset details page. The Brand Connect link points directly to the asset on your Brand Connect and the Webdam Admin link points to the asset in your Core Library. Users who click the link will need to log into Webdam and have group permissions to access the asset.
- Click Done to close the Get Links screen.
Read more about other Webdam embeddables such as Carousel and Embeddable Downloads.
Updated
Comments
10 comments
I'm trying to send a direct link to an MP3 file, but it's just giving me a link to the MP3 png image file. Can we not share direct links of MP3 files? This is the direct link it is providing: https://static2.webdamdb.com/images/mp3_100.png
Also, the embed link is requiring authentication. I add it to our sharepoint site, but when clicked, it goes to the WebDAM login screen.
Thanks!
@Donella Grant
I'm trying to send a direct link to an MP3 file, but it's just giving me a link to the MP3 png image file. Can we not share direct links of MP3 files? This is the direct link it is providing: https://static2.webdamdb.com/images/mp3_100.png
Webdam Response:
-------------
If you want to send a direct link someone who has access/Webdam credentials, you'll want to send them the URLs under the section "Page Links." If the user only has access to Brand Connect, send them the Brand Connect URL. If the person has both access to CORE and Brand Connect (with the correct permissions), then either/or URLs can be provided. Alternatively, you can also email the link to the user as well.
If you are sharing this to a guest user (who doesn't have Webdam credentials), then the best practice would be to share the asset via Email Download.
--------------
Also, the embed link is requiring authentication. I add it to our sharepoint site, but when clicked, it goes to the WebDAM login screen.
Webdam Response:
-------------
If your page is utilizing the Page Links and your Brand Connect Portal is not public, then the user will be prompted to log in.
Hi,
I want to use Direct link in one of my mobile app dynamically, is there a way I can construct this direct link dynamically.
Thanks,
Hello Kamesh,
I think you'll find a solution by calling the asset information from our API. You can find full documentation on using our Open API at the article, https://www.damsuccess.com/hc/en-us/articles/202134055-REST-API. Thanks.
Hi there, is there still no way to have a direct link to an asset using its actual size? In other words, an image that is 105 pixels wide needs to be forced into 100 or 150?
Hi Kirk,
Not as such. The direct links are pre-populated at fixed pixel dimensions. That said, if you select an option larger than the dimension of the image, it will remain at the original dimension. So in your example, when selecting 150, the image would still be at the 105 px dimension.
That should solve my problem, but just curious... Is there a reason (technical or otherwise) that it's set up that way? I see the value of being able to serve multiple sizes from a single asset, but why no option for actual size?
That's a good question, and one that cuts to the root balancing act that is an online DAM platform. Most brands we work with want to keep the core assets secure. The permalink options weren't meant to be a way of serving the assets broadly, they are more like previews. Hence why they are only JPGs, securely hashed, etc,.
Some of the ways I've seen them used are in custom integrations, mobile apps, and just ad hoc sharing with stakeholders. Most that want to link their images to an image server tend to integrate directly through the API, or use a connector with their CMS while keeping the core asset secured in the DAM.
Thanks Bill, that last bit--serving the images--is what we are looking to move toward. Can you point me to documentation about how all of that works so I can start planning it out for the longterm? In the meantime we are just getting the basic downloadable assets set up. Linking up for image serving is a phase 2 (or 3 or 4 ...).
Sure thing, Kirk. We have off the shelf solutions for Drupal and Wordpress (links below), and should have AEM and Sitecore soon. If your team is so inclined, they can build off our API and if you need something more custom, I encourage you to work with your Customer Success Manager to see if it's something we would take on.
Drupal: https://www.damsuccess.com/hc/en-us/articles/204362455-Asset-Chooser-Plugin-for-Drupal
Wordpress: https://www.damsuccess.com/hc/en-us/articles/204362395-Asset-Chooser-Plugin-for-WordPress
Article is closed for comments.