The Podigee Podcast Player

Configuration

You can set up the player for your podcast under "Podcast -> Web-Player". 

Here you can adjust the colours and the configuration.

Embedding on external websites

You can either embed the player for the entire podcast (optional with a playlist with all episodes) or per episode.

You can find the embed code for the entire podcast under "Podcast -> Web player", and for individual episodes under "Episode -> Media files -> Embed web player".

Data Protection / GDPR

The Podigee player is 100% GDPR compliant and the used social media links are pure links and do not set cookies or communicate with external services without user interaction.

You may also deactivate the "Share" tab completely under Podcast -> Web Player -> Advanced Options -> Share.
In case you use the player externally on your own website, you can optionally include the following text in your privacy policy:

https://help.podigee.com/article/430-gdpr-data-protection-declaration-sample

Known Issues

Our player works well on most sites, with a few exceptions:
  • Wordpress.com (the cloud version of Wordpress, own installations work without any problems)
  • Wix.com - use the simple embed code for this
  • We recommend not to include more than 25 web players on a single HTML page. For security reasons, the number of accesses from a browser per second is limited. If more than 25 web players are included, this limit may be reached and some players may not be displayed correctly.
  • When using a script blocker on your own computer, it can happen that the player is not loaded. In this case, extending the list of permitted domain(s) in the script blocker to include the entries "*.podigee.io" and "*.podigee.com" will fix the situation and should ensure that the player is displayed correctly. 

If you want to use your own podcast player

Please consider following these technical specifications if you plan to use your own podcast web player with a podcast hosted on Podigee:
  1. the player should not implement any kind of autoplay
  2. make sure that the player does not pre-load any audio data unless the visitor clearly intended to play the podcast episode
  3. use the provided audio URL as is and do not manipulate or add any parameters
  4. do not to cache the audio content on your own servers
  5. ask for the entire file in one go, if you want to start a full download. For a progressive download, ask for the file in slices (byte range). This way a full download can be distinguished from a progressive download
  6. use the GUID - as opposed to episode URL, title, publication date, etc. - to identify new episodes in the RSS. The GUID is designed to be persistent through changes to hosting environment, titles, etc.
  7. employ an “automatic download unsubscribe” behavior (e.g. - stop auto downloads after 5 episodes of non-listens)
  8. do not automatically download all episodes (e.g. back catalog episodes) by default. This creates unnecessary drain on our servers and consumes users’ bandwidth