Predictable URLs in Dynamic Asset Transformation (DAT)

  • Updated

Dynamic Asset Transformation (DAT) allows you to generate optimized derivatives on demand for use in external systems. With predictable URLs in DAT, you can seamlessly retrieve assets based on metaproperty options, which provides automated and efficient access to the right content based on specific asset characteristics. By leveraging the specific characteristics of assets through metaproperties, users can programmatically retrieve the most relevant content and deliver it seamlessly to end users and downstream systems. The feature enhances efficiency, enables targeted content delivery, improves SEO efforts, and ensures brand consistency within a connected ecosystem.

Predictable URLs are available to customers on specific DAT plans. Please contact your Customer Success Manager to learn more about DAT.

Structure of Predictable URLs

Your URLs will be based on metaproperty options. Below is the structure to build the URLs. 

https://baseurl/match/metaproperty_name/metaproperty_option/name

Example:
https://byndair.bynder.com/match/Country/France/EiffelTower

Important information:

  • Public Assets: In order to utilize predictable URLs, assets need to be public within the DAM. Learn more about marking assets as public assets here.
  • Additional Metaproperties: You can add additional metaproperties and options by following the same format.
  • Supported Metaproperties types: Select, Auto complete, and Select2 metaproperty types in the legacy taxonomy, and Single and Multi select metapropery types in the new taxonomy are supported. Text and Date metaproperties are not supported.
  • Multiple Results: If a metaproperty combination has multiple asset results, the URL will retrieve the most recently uploaded asset that matches the given criteria by default. However, you can set the default based on the date uploaded, date created, date updated, or the asset name in descending or ascending order. If you’d like to update this, please reach out to your Customer Success Manager.
  • Database name: You must use the database name for the metaproperty and option, rather than the label.
  • Case Sensitivity: The URL is case-sensitive for both metaproperty names and options. Ensure that the capitalization matches the metaproperty configuration to retrieve the desired asset.
  • Trailing Slash: When the URL ends with a metaproperty option, a trailing slash must be included. Example: https://byndair.bynder.com/match/Country/France/
  • Cache Invalidation: If a change is made to the asset, then the cache will be invalidated so that the most up to date asset is displayed.

    Note

    We don’t currently invalidate when there’s an edit made to the metaproperties, such as editing or deleting a metaproperty or option, only when there is a change made to the asset, such as when a new version is added, the focus point is updated, or the asset is deleted.

  • Transformations: Transformations can be applied on your predictable URL assets by adding the same parameters offered in DAT after your last metaproperty option or name.

Was this article helpful?

0 out of 0 found this helpful

We're sorry to hear that!

Find out more in our community

Have more questions? Find out more in our community