ART19 can support any 3rd party player. These players can use the MP3 enclosure URL from an RSS feed or leverage our Content API. To learn more about our Content API, check out:
For customers using their own players, we strongly advise against using auto-play and pre-loading. Doing so would be a violation of the IABv2.1 measurement guidelines. Additionally, please follow this guidance as well:
File request - For a full download, ask for the entire file in one go. For a progressive download, ask for the file in slices (byte range). This way a full download can be distinguished from a progressive download. |
Do not modify the enclosure URL when requesting media, don’t add extra parameters. |
Do not cache podcast episodes on your servers. Always download the latest episode from the enclosure URL for every app user wanting to listen. |
Use a descriptive user-agent. We recommend using of the following pattern for the user-agent which requests the MP3 enclosure URL, in order to appear in ART19 analytics and to provide a consistent structure for all parties who consume the details: |
Use the GUID -- as opposed to episode URL, title, publication date, etc. -- to identify new episodes in the RSS feed that should be automatically downloaded to a user’s device. The GUID is designed to be persistent through changes to hosting environment, titles, etc. |
Employ an “automatic download unsubscribe” behavior (e.g. - stop auto downloads after 5 episodes of non-listens). |
Do not automatically download all episodes (e.g. back catalog episodes) by default. This creates unnecessary drain on the publishers’ servers and consumes users’ bandwidth. |