How to Read Podcast Analytics in Apple Podcasts and Spotify: Plays, Engaged Listeners, Downloads and Why the Numbers Differ

What Are Podcast Analytics?

Podcast analytics are the performance reports a show gets from the apps people listen in, such as Apple Podcasts and Spotify, and from the hosting provider that serves the audio file. Each source counts a different event, for a different set of listeners, over its own time window.

This guide is for a company that runs its own podcast, or an executive and their team checking how a guest appearance performed. It is about reading the dashboards. Why a download is a weak proxy for listening is covered in how big a podcast audience is and why download numbers mislead, and the September 2026 rule changes in what changed in the podcast download rules. Completion data is discussed in what share of podcast listeners finish an episode.

How to Read Podcast Analytics at a Glance

Time: about an hour per episode once you have access (our estimate). Tools: Apple Podcasts Connect, Spotify for Creators, the hosting provider's dashboard, a spreadsheet. Cost: none; the dashboards are free to the show. Skill level: beginner.

What You Need Before Starting

• The episode title, its publish date and its duration. Duration matters for Apple's engaged-listener rule.
• Access to the show's Apple Podcasts Connect and Spotify for Creators accounts, or a host willing to send screenshots or exports. Apple says to make sure you are signed in with an Apple Account “that has access to the show” (Apple).
• The name of the hosting provider and, if it claims IAB certification, which version of the guidelines.
• For a guest appearance: tagged links in the show notes, so site visits can be separated from listening. See how to track press and podcast links with UTM parameters.
• The figures for the show's last few episodes, to use as a baseline.

Step 1: Write Down the Question and the Date Range

Decide what you are trying to learn before you open a dashboard. “Did people hear our chief executive's segment?” needs consumption data. “How many times was the episode fetched?” needs downloads. “Did listeners visit our site?” needs web analytics, not podcast analytics.

Process: pick one episode and a fixed window, for example the first 7 or 30 days after release, and use the same window in every tool. Expected result: one sentence naming the question, episode and dates. Verify: everyone receiving the report would read the question the same way. Common mistake: comparing an episode's first week with another episode's lifetime total.

Step 2: Get the Three Reports, After the Delay

Apple Podcasts Connect, Spotify for Creators and the hosting provider each see a different slice of the audience. Apple's figures cover Apple's apps and devices; Apple lists iOS, iPadOS, macOS, watchOS, tvOS, HomePod, iTunes and some third-party devices such as Alexa, Porsche and Tesla as data sources (Apple). Spotify's engagement analytics “only show people who engage and listen to or watch your show on Spotify” (Spotify). The host sees file requests from every app that fetches the audio from it.

Process: wait before pulling numbers. Apple says its data “begins at 12:00 a.m. and ends at 11:59 p.m. (UTC)” and “might be delayed by up to 72 hours” (Apple). Spotify says most analytics update every 15 minutes, but some metrics take up to 48 hours (Spotify). Expected result: three reports for identical dates. Verify: the last day in your window is at least three days old. Common mistake: reporting day-one Apple figures as final.

Step 3: Read Apple Podcasts Connect

Apple says its analytics “focus on providing aggregated listening and viewing completion rates from unique devices for each episode”, and that downloads may be available from your hosting provider instead (Apple). Its episode-level definitions, from the same page:

• Listeners: “The number of people that played or watched more than zero seconds of the episode.”
• Engaged Listeners: “Total number of listeners who heard or watched at least 20 minutes or 40% of an episode.”
• Plays: “Total number of plays for an episode where the duration is greater than zero seconds.”
• Average Consumption: “A percent average indicating how much of the episode users played per device”. Above 100% means someone listened more than once.
• Followers: “The total number of people following your show”, a show-level figure, not an episode one.

Process: open the Episodes tab and record Listeners, Engaged Listeners, Plays and Average Consumption for the episode and window. Then divide Engaged Listeners by Listeners to get the share who stayed for 20 minutes or 40%; that ratio is our calculation, not an Apple metric. Expected result: four numbers and one ratio. Verify: the date control matches Step 1; Apple shows the last 60 days by default (Apple). Common mistake: treating “Not Enough Data” as zero. Apple shows nothing until “at least five unique users” have played the show in the selected time frame (Apple).

The 20-minute-or-40% rule depends on length. On a 30-minute episode, 40% is 12 minutes, so that test is met first; on any episode of 50 minutes or more, 20 minutes is met first. That arithmetic is ours.

Step 4: Read Spotify for Creators

Spotify's analytics glossary defines a Play as “the number of times any episode of your show was watched or listened to for at least 30 seconds on Spotify during the selected time period” (Spotify). Other glossary terms that matter for one episode:

• Spotify Audience: distinct people who played any episode on Spotify in the period. Audience numbers update every 24 hours.
• Completion rate: “The percentage of your audience that made it at least 95% of the way through an episode on Spotify during its first 7 days after publish.” Quartiles show the share reaching 25%, 50% and 75%.
• Consumption time and average consumption time: time spent watching or listening on Spotify.
• Followers: people who “started following your show on Spotify during the selected time period”, a different definition from Apple's total.
• Impressions: times content was displayed on screen. Spotify says the count “does not reflect whether or not people engaged with the content.”

Process: record Plays, Spotify Audience, completion rate, quartiles and average consumption time for the episode. Expected result: a Spotify-only picture of reach and depth. Verify: if a Downloads or All Platform Audience figure appears, the show is hosted with Spotify for Creators; the glossary says those metrics are available to such shows only (Spotify). Common mistake: reading Spotify's completion rate (95% of the episode) as the same thing as Apple's engaged listener (20 minutes or 40%).

Step 5: Read the Hosting Provider's Downloads

The host's download count is the only one of the three that covers every app. IAB Tech Lab's Podcast Technical Measurement Guidelines v2.3 say that “to count as a valid download, the header information plus enough of the podcast content to play for 1 minute should have been downloaded”, after filtering bots, pre-loads and duplicates (IAB Tech Lab). Unique “podcast consumers” are estimated from IP address plus user agent within a stated time frame.

Process: record downloads for the episode and window, and write down the provider's certification claim. Buzzsprout, for example, says its statistics are “IAB 2.2 Certified” and that it counts a download “when someone streams or downloads at least 60 seconds of an episode” (Buzzsprout). IAB Tech Lab runs a separate compliance program for companies measured against the guidelines (IAB Tech Lab). Expected result: one download figure, labelled with provider and certification. Verify: ask which de-duplication window the provider uses; v2.3 describes three in use. Common mistake: reading downloads as listeners. A download records a file request, not a play.

Step 6: Put the Figures on One Sheet, Without Adding Them

The three sources overlap. An Apple listener may also be counted as a download at the host, because the Apple app requested the file. Adding Apple listeners, Spotify plays and host downloads double-counts some people and mixes different events.

Process: build a table with one row per metric and columns for source, what it counts, the unit, the dates and the figure. Expected result: a sheet in which no two figures are added together. Verify: every number has its unit beside it. Common mistake: a single “total reach” figure built from all three sources.

Step 7: Compare With the Show's Own Baseline

A number on its own says little. The useful question is whether this episode did better or worse than the show's usual episode over the same days since release.

Apple's Performance tab compares episodes by days since release: choose the last 50, 100 or up to 200 episodes, a window of 7, 14, 30 or 60 days, and a baseline of median, average or top episode (Apple). Spotify shows episode benchmarks once a show has at least 10 published episodes, and not on publication day (Spotify). For downloads, IAB Tech Lab says differences between certified vendors “within ±5%” are generally acceptable (IAB Tech Lab), so treat small gaps as noise. Expected result: a sentence such as “engaged listeners in the first 7 days were above the show's median”. Common mistake: comparing a guest episode with a different show's numbers, which the IAB guidelines do not make comparable.

How to Verify It Worked

• Dates: all three reports cover the same days, and the last day is at least 72 hours old.
• Units: every figure is labelled as listeners, plays, engaged listeners, audience or downloads.
• No sums: the report never adds figures from different sources.
• Baseline: the episode is compared with the same show's earlier episodes over the same days since release.
• Outcome: if the goal was business results, the report also shows tagged-link visits or other outcomes, as discussed in how a company should measure whether placement worked.

Which Number Answers Which Question

Common Problems and Fixes

What Not to Do

• Do not add the three sources together. Consequence: an inflated figure nobody has defined. Correction: report each with its unit.
• Do not call downloads listeners. Consequence: an overstated audience. Correction: say “downloads” and name the provider.
• Do not judge an episode on day one. Consequence: understated Apple figures. Correction: wait at least 72 hours.
• Do not compare shows on raw numbers. Consequence: unfair comparisons between different audiences and providers. Correction: compare each episode with its own show's baseline.
• Do not publish a host's private figures without permission. Consequence: a damaged relationship. Correction: agree in advance what the guest's team may share.

Frequently Asked Questions

Sources and Methodology

This guide is built from Apple's and Spotify's help pages, IAB Tech Lab's measurement guidelines and one hosting provider's product page, all read on October 11, 2026. We did not have access to a show's dashboards for this guide, so the steps follow the documentation, not a test account. The engaged-listener ratio, the 50-minute break-even point and the chart's minute values for Spotify are our arithmetic from published definitions. The time estimate is ours. Platform help pages change without notice, and Spotify's older regional help pages use earlier terms such as starts and streams that do not appear in its current US glossary; we relied on the current glossary.

1. official Apple, Analytics, Apple Podcasts for Creators. Definitions of Listeners, Engaged Listeners, Plays, Average Consumption and Followers; five-listener threshold; 60-day default; Performance tab. Read October 11, 2026.
2. official Apple, Data requirements and troubleshooting, Apple Podcasts for Creators. Devices, UTC day, up to 72-hour delay, minimum threshold. Read October 11, 2026.
3. official Spotify, Analytics glossary, Spotify for Creators. Plays at 30 seconds, audience, followers, completion, impressions and refresh rates. Read October 11, 2026.
4. official Spotify, Overview analytics and Understanding Engagement analytics, Spotify for Creators. Refresh delays, benchmarks, Spotify-only scope. Read October 11, 2026.
5. standards IAB Tech Lab, Podcast Technical Measurement Guidelines, Version 2.3, GitHub, September 2026. One-minute download rule, podcast consumer definition, ±5% vendor tolerance. Read October 11, 2026.
6. standards IAB Tech Lab, Compliance programs. Read October 11, 2026.
7. vendor Buzzsprout, Podcast Statistics. Certification claim and download definition, as a hosting-provider example. Read October 11, 2026.