The Podigee Podcast Player

Set up the player

Open Web Player in the podcast settings. Set the player options for the podcast and its episodes. Your contract sets the available design options.

Add the player to a website

• For the full podcast, copy the embed code from Web Player in the podcast settings.
• For one episode, open the episode. Copy its embed code from Media File.

Put the code in a website area that can use this HTML or script code. Check the published page on a desktop and a mobile device.

Sharing and privacy

You can set the Share option separately for the Podigee blog and embedded players. In Web Player, open On the website or Embedded. Change the Share option.

Check privacy for your website and its configuration. Additional scripts, analytics tools and external content can change data transfers and cookies. Use of the player alone does not give a general privacy guarantee for the website.

Include the player in your privacy notice. Also check other services and whether consent is necessary. Podigee does not offer a privacy policy template. For information about data use by Podigee, see the Podigee privacy notice.

Compatibility and loading problems

• WordPress.com: Available script functions are different for different plans and settings. See the WordPress.com code instructions. Themes, plugins and security settings can also affect a WordPress site that you host.
• Wix: Use an HTML or website embed with HTTPS. Follow the Wix instructions. Check the size of the embed area. Test the player on the published page.
• Many players: As a practical limit, use no more than 25 players on one page. This is not a fixed browser limit. Check the actual loading time. One podcast player with a playlist can be sufficient.
• Blocked content: Check the embed code, script-blocker messages and failed network requests. A fixed domain list can miss necessary content.

If the player still does not work, send support the page address, embed code and error message. First, remove access credentials and personal feed tokens.

If you develop your own player

• Start audio only after an action by the listener. Do not load audio automatically in advance.
• Use the supplied audio URL. You can change the documented source parameter. Do not change other parameters without instructions for that change.
• Send requests directly to the supplied audio URL. Copies on your own server can miss updates and cause missing Podigee analytics.
• Use HTTP range requests for partial transfers and changes in playback position. Avoid unnecessary or overlapping requests. A full or partial transfer does not show actual listening or whether the file was saved.
• Use the GUID in the RSS feed to identify an episode. Keep it during updates.
• Do not download the full archive by default. Limit automatic downloads, for example with a pause after five unplayed episodes.
• Use a clear user agent with the app name and version, if your platform allows this.
• If you only need a title or cover, use feed metadata. Do not download the full audio file for this.

Example user agent:

AppName/1.2.3 DeviceBrand DeviceModel OSName/1.2.3 LibName/1.2.3

The download and stream explanation gives the measurement limits.