Is your enhancement related to a problem? Please describe.
As noted by @bacoords:
Problem: There is currently no built-in solution for tracking basic download metrics (e.g., raw downloads per episode) for self-hosted podcasts, especially those using services like Amazon S3 to serve MP3 files. This has led some podcasters to question whether the lack of such analytics is a reason why people opt for paid hosting services that offer built-in analytics (over otherwise free, open source options like Simple Podcasting).
Proposed Feature: Implement a simple tracking mechanism to gather and display download metrics for self-hosted podcast episodes. The basic metrics to track should include:
- Total downloads per episode.
- Optionally, referrer data (e.g., where the downloads are coming from).
Benefit: This would provide self-hosted podcasters with a way to track how many times each episode is downloaded, helping them better understand audience engagement without relying on third-party hosting services.
Designs
No response
Describe alternatives you've considered
No response
Code of Conduct
Is your enhancement related to a problem? Please describe.
As noted by @bacoords:
Problem: There is currently no built-in solution for tracking basic download metrics (e.g., raw downloads per episode) for self-hosted podcasts, especially those using services like Amazon S3 to serve MP3 files. This has led some podcasters to question whether the lack of such analytics is a reason why people opt for paid hosting services that offer built-in analytics (over otherwise free, open source options like Simple Podcasting).
Proposed Feature: Implement a simple tracking mechanism to gather and display download metrics for self-hosted podcast episodes. The basic metrics to track should include:
Benefit: This would provide self-hosted podcasters with a way to track how many times each episode is downloaded, helping them better understand audience engagement without relying on third-party hosting services.
Designs
No response
Describe alternatives you've considered
No response
Code of Conduct