Delivery Metrics provides detailed analytics and insights on the usage of your assets outside of the DAM. This allows you to better understand how your assets are performing and being used across different channels.
The Delivery Metrics report includes information about how many times the asset has been viewed, the websites where it’s been viewed, and the top transformations, if you’re using Dynamic Asset Transformation (DAT). In this article, we’ll outline the technical information about how delivery metrics are collected.
Learn more about the asset level report that’s available here.
Asset views refers to the number of times a DAT or public link asset is requested externally. The term 'view' is used in consistency with other analytics tools, such as Google Analytics’ page views. Most websites follow lazy loading best practices, meaning that the content is only requested and shown when the user is navigating that section of the page, not just when the page is first loaded.
Every time a link is requested through the Bynder CDN, it is counted as a view. This includes when assets are viewed while embedded on a webpage, in a mobile app, in a separate tab, or when a user right clicks to download the asset.
It can take up to 2 days before an asset view is registered and displayed within the report.
The top websites where the asset is viewed will be displayed. We identify the websites where an asset is used with the referer header. This header is sent along with the request for an asset. For example, if an asset is used on https://support.bynder.com/, the asset request to https://assets.bynder.com/ would have https://support.bynder.com/ as the content of the referer header.
If a request does not include the referer header, the website will be counted under a hyphen “-” in the Top Websites section.
Requests that don’t have a referer header might occur when users right-click and save the image or right-click to view the image in a separate tab in their browser. In those cases, the asset is not embedded on a web page, and the referer header won’t be sent.
Referrer data will also not be collected if your website has a Referrer-Policy header set to no-referrer or same-origin. More information regarding the Referrer-Policy header can be found here.
Some proxies remove the referer header for images. If you use a proxy or CDN in front of Bynder that doesn’t forward the referer header, we are unable to show website information. Please ensure that the referer header is passed along with the asset request if you like to see website views.
If you use Dynamic Asset Transformation, the top transformations for the assets will display. If multiple transformations are applied at the same time, each transformation is counted separately.
Whenever a DAT link is used, it is usually accompanied by query parameters that define the transformations that need to be applied. An example DAT link is:
In the example above, io=transform:fill,width:1200,height:1200&io=filter:grayscale defines the transformation. In this case, the transformations are a ‘fill’ and a ‘grayscale’ transformation. In the delivery metrics report, this will be counted as both a fill and grayscale transformation.
Delivery metrics will not work well in combination with a caching proxy or a custom
CDN. Requests that are served by a cache that is not the Bynder CDN will not be counted, as there is no request that reaches the Bynder platform. If a custom CDN or caching proxy is set up, only the requests that are forwarded to the Bynder platform will display in the delivery metrics report.
If you use DAT presets, the transformations used in that preset are not displayed in the transformations metrics. Currently, only DAT requests that use query parameters are displayed in the report.
- Delivery Metrics: Asset Level Report
- Dynamic Asset Transformations (DAT)
- View Statistics on Asset Detail Page
- Mark Assets as Public Links