When implementing a Consent Management Platform (CMP) for audio streaming, it is important to understand where consent is actually collected and handled within the streaming chain.


SharpStream delivers the audio stream and associated request information downstream, but consent collection itself is typically handled:

  1. on your website by your CMP and compatible player;
  2. or externally by third-party listening platforms such as Radioplayer or TuneIn


This means:

  1. SharpStream does not generate consent strings
  2. SharpStream does not control listener consent choices
  3. SharpStream can only pass downstream the information already attached to the request


For website listening, the consent signal is usually collected by the CMP, retrieved by the web player, and then passed through the advertising chain to platforms such as AdsWizz.


For third-party listening platforms, the listener is not interacting with your website directly, so those platforms are responsible for collecting and passing consent themselves.


If consent information is missing, the issue is usually within:

  1. the CMP configuration
  2. the player integration
  3. or the third-party platform configuration

…rather than the stream delivery layer itself.