Configuration Requirements for Podcast Metrics
Below are the configuration requirements when using Podcast Metrics for measurement.
It is the responsibility of the Client to ensure that the Service Provider measures all of the podcasts that we should measure. Therefore, the Client shall inform the Service Provider, in writing, when podcasts need to be added or removed from the measurement service.
To produce metrics per episode and podcast (show), episodes must be identified from the HTTP URL or other field in the logs (for example, by using an ID). Podcast title, episode title, and episode publication date must be provided to the Service Provider separately from the logs. This should be done by providing a list of RSS feeds containing all the appropriate information for podcasts and episodes. This is required in order to associate a line in the access log file to a podcast (show) and an episode. More information about RSS feeds can be found in the Measurement Guide for Podcast Metrics.
Log Collection
Unless the Client uses the Service Provider’s Streaming and Delivery Services, the Client shall allow the Service Provider to collect logs directly from the Client's streaming servers or content delivery network. The Service Provider needs a daily log file dump to S3 or SFTP, directly from the Content Delivery Network (CDN) or from the podcast Content Management System (CMS). The log files must be in a format approved by the Service Provider, such as the format described in the Measurement Guide for Podcast Metrics.
The Client's log files should be made available after a delay of no more than three days.