This exact problem applies to podcast analytics. "Downloads" is only a proxy for "listens" / ad impressions.
It seems to me like there needs to be a standard pingback endpoint (either in /.well-known or, better, right in the podcast/rss XML) that your client pings when it seems like you've consumed the content (scrolled through most of a web page, listened to 80+% of a podcast), but only if you've opted in to that.
It seems to me like there needs to be a standard pingback endpoint (either in /.well-known or, better, right in the podcast/rss XML) that your client pings when it seems like you've consumed the content (scrolled through most of a web page, listened to 80+% of a podcast), but only if you've opted in to that.