Georgia Public Broadcasting Partners with StreamGuys

RADIO ONLINE | Monday, February 1, 2021 | 8:40am CT

With 18 radio stations, nine television stations and a multi-faceted website, Georgia Public Broadcasting (GPB) has partnered with StreamGuys and recently leveraged SGrecast's new development API for seamless integration with GPB's website content management system (CMS). The result has unified GPB's audio publishing, storage, and delivery processes while further simplifying operations at a time when its digital media properties are seeing their highest traffic ever. GPB was already using the versatile SGrecast SaaS platform from StreamGuys to efficiently manage their podcast publishing workflows.

Prior to the new integration, GPB used two distinct workflows for different types of audio content. SGrecast was used only for pre-produced podcast episodes, which operators uploaded directly into SGrecast along with corresponding metadata for automated publishing and distribution. Non-podcast audio clips such as sound bites and story reads, which accompany articles on GPB's news website, were handled separately. When the broadcaster merged its dedicated news portal into the main GPB.org site last year, the team took the opportunity to combine its behind-the-scenes audio processes.

"Our main GPB.org site wasn't set up to serve audio files, so we needed a good place to host its new audio content," said Carl Zornes, director of digital media, GPB. "We were already using SGrecast very successfully to host our podcasts, so we decided to expand its use to both content types. Bringing our podcasts and news audio clips together in our website CMS would also remove some manual steps for our podcast producers."

GPB and its website developers, Lullabot, used StreamGuys' just-released API to let producers and news reporters submit both podcasts and general audio content to SGrecast through the same CMS interface.

"Uploading audio clips to SGrecast is now fully automated through the CMS," explained Zornes. "When creating an article, a user clicks to add audio just as if they were uploading an image to the website. If it's only intended for the website, the user doesn't need to go through any podcast-related steps - the audio is automatically sent to SGrecast for storage and hosting, and it will be rendered within the article on our site. However, if the user checks the option in the CMS to make the audio part of a podcast, they can also get a list of all the podcasts available in SGrecast. They select which podcast to attach the audio to, and once the content is approved by an editor and published in the CMS, an automated API call triggers SGrecast to add the content to the podcast feed and distribute it to our target outlets. The only time a podcast producer now goes manually into SGrecast is to insert ad markers."

In addition to the time savings afforded by the new API integration, Zornes praises the rich metrics provided by StreamGuys' software suite and the overall publishing efficiency of SGrecast. "I love the analytics we get from SGrecast and SGreports," he elaborated. "I like to slice and dice our metrics to understand our audience better, and the data we get from StreamGuys is phenomenal. I also appreciate that we can build one podcast feed and identify all the different providers we want to send it to. We only have to do that once, and we're covered everywhere, whether it's five places or two dozen."