Podcast listener churn benchmarks you can defend

Podcast listener churn benchmarks are useful only when they compare like with like. There is no published industry percentage you can safely apply to every show, because podcasting does not have one audience database that follows the same listener across every app. The useful alternative is a small internal benchmark built from the signals each platform can actually observe.

That is less flashy than a universal churn number. It is also far more useful when you need to decide whether a show is losing its regular audience or simply had one quiet release.

The podcast listener churn benchmarks that exist

The table is deliberately not a table of percentages. The platforms disclose the signals, but they do not publish a common churn distribution that lets one show compare its follower loss with another show’s download decay. Treat a vendor page that promises a single industry churn rate with caution unless it names the source population, identity method, period, and formula.

The IAB Podcast Measurement Technical Guidelines explain why delivery data has a boundary. A podcast download is a filtered request for media, not proof that a known person listened, finished, or returned for a later episode. That makes downloads excellent for an episode delivery trend and insufficient for literal person-level churn.

Why a universal percentage would be misleading

A listener can hear your show in Apple Podcasts, Spotify, a web player, and another app in the same month. Each platform sees only part of that activity. Apple can report activity that happens in Apple Podcasts. Spotify can report activity inside Spotify. A hosting log sees eligible audio requests, but it cannot reliably convert those requests into one enduring person across apps and months.

Period choice creates another problem. A weekly interview show and a seasonal documentary can have the same underlying loyalty but very different month-to-month return patterns. A show that releases weekly should not compare a thirty-day pattern with a show that releases once a month. Likewise, an episode that is three days old should not be held against an episode with a full month of delivery.

This is why the closest defensible benchmark is operational, not universal. Fix the reporting boundary, preserve it, and compare each new observation with your own recent history.

Build a baseline from three partial views

Start with the app metrics that identify an audience within their own walls. Apple Podcasts Connect documents show followers and net new followers. Its Analytics overview describes follower reporting and makes clear that the data belongs to Apple’s listening environment. Record the net figure by the same period every month. A declining net figure does not reveal every person who left, but it tells you that new follows are no longer offsetting unfollows in that environment.

Spotify for Creators presents listener and follower analytics for Spotify consumption. Its analytics documentation is the primary source for what those measures represent. If your view separates returning and first-time listeners, record the ratio, then use it as a direction signal. A growing first-time audience can be good acquisition, but it needs a later return signal before you call it durable growth.

Then add a delivery measure that spans your distribution. For each release, record downloads at one fixed age. Thirty days can work for a weekly show if it matches how you sell and review inventory, but the important part is consistency. Compare a new episode’s thirty-day delivery with the trailing median of comparable releases, not with the lifetime total of your biggest back-catalog episode.

A simple sheet needs columns for release date, format, platform, reporting window, net new followers, returning-listener share where available, and fixed-age downloads. Add a note when a major guest, paid campaign, holiday, hiatus, or format change occurred. Those notes keep you from calling a campaign bump a retention improvement.

Read the three signals together

One weak signal is not a churn verdict. The combination is what makes it useful.

If Apple net new followers turn negative while fixed-age downloads also trend down, investigate the publishing promise, release rhythm, and recent format changes. If fixed-age downloads decline but follower movement remains steady, inspect distribution, feed delivery, episode topics, and the age window before blaming listener loyalty.

If first-time listening rises but returning listening does not follow, acquisition may be working while the first episode experience is not. Review the opening, title-to-content match, and next-episode path. Our explainer on podcast listener retention helps separate within-episode attention from broader audience return.

If completion falls while follower movement is stable, the issue may be episode structure rather than the show’s core promise. Compare episodes by format and length before changing the entire program. Podcast completion rate is a related but distinct measure.

Set an alert rule you can explain

Do not create alerts from arbitrary percentages. Instead, define an action rule in plain language. For example: review the last six releases when fixed-age downloads fall below the trailing median for several comparable episodes and follower growth weakens in the same period. The rule is not a scientific diagnosis. It is a consistent prompt to look closer.

Make the comparison fair before interpreting it:

• Keep release cadence in the record.
• Compare the same episode age.
• Keep platforms separate rather than adding their people together.
• Label campaign-driven episodes.
• Separate a seasonal break from a normal weekly gap.
• Review median and range, not only a single average.

The median is especially helpful when one celebrity guest creates an outlier. It keeps one unusual release from becoming the baseline your regular episodes are judged against.

What to change when the baseline slips

Start with the listener promise. A familiar title format, clear episode descriptions, and a predictable subject area help a returning listener know why the next release belongs to them. Episode pacing can reveal whether the actual release rhythm differs from the rhythm you promise.

Next, inspect the first minutes of recent episodes. New listeners decide quickly whether the title delivered what it implied. Move context, housekeeping, and long preambles after the first useful beat. Then give a returning listener a reason to follow the feed, such as a clear next topic or continuing series.

Finally, review acquisition quality. A promotion that sends the wrong people may lift a short-term download count without producing return behavior. The goal is a repeatable path from discovery to a second listen, not the largest one-week spike.

Methodology note for sponsor conversations

Do not call an internal baseline an industry benchmark. Say exactly what it is: a show-level comparison based on a stated window, specific platforms, and a fixed episode age. That wording protects you and helps a sponsor understand the measurement boundary.

For delivery claims, use a consistent IAB-aligned definition and keep the window beside the number. What counts as a podcast download covers the distinction between delivery and listening. For a wider measurement system, podcast analytics shows how to connect audience, episode, and campaign questions without pretending they are one metric.

A churn benchmark earns trust when it is narrow enough to be true. Build it from the audience you can observe, preserve the method, and use it to decide what to test next.

Want a steadier record of episode delivery across apps? Start with Podder Analytics.