Skip to content
Podlink
Guide · Podcast analytics

Apple vs Spotify vs your host: why your podcast numbers never match

The short answer

They measure different things. Apple counts a play from more than zero seconds, Spotify counts a play at 30 seconds, and your host counts downloads — file requests, not listening. Each app also sees only its own users. Read them as three windows on one audience, and never add them together.

Published 2026-11-11 by Podlink. Every definition, threshold and refresh rate here is quoted from the platform’s own page, fetched on 2026-11-11, with the source named; the sources are listed at the end. Guidance we could not source is labelled “Our advice”.

Three dashboards, three different questions

The disagreement between your dashboards is not a bug in one of them. Apple Podcasts Analytics, Spotify for Creators and your hosting provider answer three different questions, each from the only data it can see. The IAB Tech Lab’s measurement guidelines — the definitions podcast advertising is priced against — explain the root of it: podcast episodes are downloaded for consumption, so measurement is based on server logs, unlike other digital media that keep an open connection to the device. In the IAB’s words, this nuance produces different metrics.

The three measurement surfaces as each one’s own documentation describes them, fetched 2026-11-11. Full citations are at the end of the page.
DashboardIts unitsWhat countsWho it can seeSource
Apple Podcasts AnalyticsPlays, Listeners, Engaged Listeners, FollowersA play where the duration is greater than zero seconds; a listener who played or watched more than zero seconds; an engaged listener at 20 minutes or 40% of an episode.Listening on Apple Podcasts (Apple devices plus some third-party integrations), aggregated from unique devices.Apple's Analytics and data-requirements pages
Spotify for CreatorsPlays, Audience, Followers, completion rates, impressionsA play when an episode is watched or listened to for at least 30 seconds on Spotify; audience as distinct people; completion at 95% of the way through.Listening on Spotify only. Its “Downloads” and “Plays & downloads” metrics exist only for shows hosted with Spotify for Creators.Spotify's analytics glossary
Your host / an analytics prefixDownloadsFile delivery from server logs. RSS.com's IAB-based example: at least 60 seconds of the file delivered, once per episode, per listener, per day.Every app that fetches audio from your RSS feed — minus plays Spotify serves from its own servers.IAB Tech Lab guidelines page; RSS.com help

So before comparing any two numbers, name their units. An Apple play, a Spotify play and a download are three different events with three different thresholds, counted among three different groups of people.

What Apple Podcasts Analytics counts

Apple’s own Analytics page says the quiet part in its first paragraph: while the key metric for understanding a podcast’s reach has traditionally been downloads, Apple Podcasts Connect Analytics focus on aggregated listening and viewing from unique devices. Apple is deliberately not a download counter — the same page notes that Apple doesn’t provide support for third-party podcast analytics and points you at your hosting provider for consumption metrics such as downloads. Its published definitions:

  • Listeners — the number of people that played or watched more than zero seconds of an episode.
  • Engaged Listeners — people who listened to or watched at least 20 minutes or 40% of an episode.
  • Plays — the total number of times people pressed play, counting plays where the duration is greater than zero seconds.
  • Followers — the total number of people following the show.
  • Top Countries/Regions and Top Cities — counted as unique devices, not people.

Three operational details from Apple’s pages decide what you will actually see. Data appears only once at least five unique listeners play content from the show in the selected time frame — below that, the dashboard says “Not Enough Data”. Data days run on UTC, and diagnostics and usage information might be delayed by up to 72 hours. And the data is aggregated with no personally identifiable listener information, gathered from Apple devices plus a short list of third-party integrations (Apple’s page names Alexa, Porsche and Tesla).

Our advice: The Apple metric worth watching is not Plays, which a download count will usually tell you more reliably across apps — it is Engaged Listeners and the Performance tab, which compares each episode’s first 7, 14, 30 or 60 days against your median, average or top episode. That consumption depth exists nowhere in a server log.

What Spotify for Creators counts

Spotify publishes its definitions in an analytics glossary, and the thresholds differ from Apple’s on the first line. A play, per the glossary, is counted when any episode of your show is watched or listened to for at least 30 seconds on Spotify — so an opening-seconds abandon that Apple counts as a play does not exist in Spotify’s plays at all. The glossary also defines:

  • Audience — the number of distinct people that played any episode on Spotify in the period, updating every 24 hours (plays update every 15 minutes).
  • Completion rates — the percentage of the audience that made it at least 95% of the way through an episode, averaged over recent episodes’ first 7 days.
  • Impressions — how many times your content was displayed on someone’s screen on Spotify, updating every 48 hours.
  • Plays & downloads / Downloads — these two metrics exist, per the glossary, only for creators who host with Spotify for Creators; for everyone else the dashboard describes Spotify listening only.

The scope line matters as much as the thresholds: every metric above is scoped “on Spotify”. A show with half its audience in Apple Podcasts will never see that half in this dashboard, and the reverse is equally true of Apple’s.

What your host and an analytics prefix count: downloads

Your hosting provider sits in a different position: it serves the audio file, so it can see a request from every app that fetches from your RSS feed — Apple Podcasts, Overcast, Pocket Casts, a web player, all of them — but it sees file requests, not listening. The IAB’s guidelines exist to make those requests comparable across hosts: filter out bots and duplicate requests, and count what remains as downloads. RSS.com’s help page states its IAB-based version plainly: a download is counted when at least 60 seconds of the episode file is delivered to a device, once per episode, per listener, per day — and, in the same article, a download confirms delivery and not that the episode was heard.

An analytics prefix measures the same event from the same position — it is a measurement server the episode URL routes through on its way to your host — which is why a prefix-based count and a host count land close to each other and far from platform plays. The honest caveats:

  • Hosts do not define downloads identically. RSS.com’s page notes that filtering rules, deduplication windows and what counts as a valid request vary, so totals may look higher or lower after migrating hosts. Same audience, different filters.
  • Spotify is a boundary, not a gap. Spotify copies your episodes onto its own servers and plays them from there, so those plays never touch your feed or its prefix. Your host reports Spotify through a separate pipeline, as its own line.
  • A download is delivery. It cannot tell you whether anyone pressed play or how far they got — that is exactly what the platform dashboards add.

Why the numbers never match

Put the definitions side by side and the mismatch stops being mysterious. Four causes do nearly all of the work:

  • Different events. RSS.com’s help page compresses it into two sentences: Spotify counts a play at 30 seconds, close to the Alliance for Measurement in Podcasting (AMP) definition; Apple counts any play over 0 seconds. A download, meanwhile, is 60 seconds of file delivery. Three thresholds, three units — as RSS.com puts it, the numbers are not meant to line up.
  • Different populations. Each app reports only its own users. That is also why platforms can show demographics and a server log cannot: RSS.com’s page notes Spotify users are registered and verified, so Spotify can aggregate age and gender for its slice — and only its slice.
  • Different clocks. Apple’s data days run on UTC and can lag up to 72 hours. Spotify’s glossary lists a refresh rate per metric — plays every 15 minutes, audience every 24 hours, impressions every 48. Two dashboards read at the same moment are rarely describing the same window.
  • Different filters, even for the same unit. Two IAB-guideline download counters still apply their own bot filtering and deduplication. PodLink’s own download-analytics FAQ says it the way we mean it: two honest counters of the same audience will never agree perfectly; anyone who tells you otherwise is rounding something.

How to read the three side by side

Our advice: Treat each dashboard as a labelled window, and give each one the question it is built to answer. Downloads, from your host or a prefix: how much delivery happened, across every app, in a unit sponsors price against. Apple: how deeply Apple Podcasts listeners consume — Engaged Listeners, Average Consumption and the Performance tab’s since-release comparisons. Spotify: the same questions for Spotify listeners — completion rates, new vs returning audience, and whether impressions turn into plays.

Our advice: Compare each number only to itself over time. A 20% rise in downloads and a 20% rise in Spotify plays corroborate each other; the absolute figures will still disagree, and that is fine. Write the unit and window next to every number you keep (“downloads, first 7 days”, “Spotify plays, last 30 days”) — the discipline costs a few characters and prevents every bad comparison at once.

Our advice: Never sum across dashboards. The one join that is legitimate is the one your host already makes for you: Spotify’s plays sit beside feed downloads as two windows on non-overlapping audiences. Everything else overlaps in unknowable ways.

FAQ

Podcast analytics, questions answered

Why don't my Apple Podcasts numbers match Spotify's?
Because the two platforms count different events among different people. Apple's analytics page defines a play as one where the duration is greater than zero seconds, and a listener as someone who played or watched more than zero seconds of an episode; Spotify's analytics glossary counts a play when an episode is watched or listened to for at least 30 seconds on Spotify. Each platform also only sees its own users: as RSS.com's help page puts it, apps like Spotify or Apple Podcasts only track data from their users, giving a partial picture. Two different thresholds applied to two different slices of your audience will not produce the same number.
Is a Spotify play the same as a download?
No. Spotify's glossary counts a play when someone watches or listens for at least 30 seconds on Spotify — a consumption event. A download, in the IAB's framework, is a server-side delivery event: RSS.com's help page, describing its IAB-based counting, says a download is counted when at least 60 seconds of the episode file is delivered to a device, once per episode, per listener, per day, and notes that a download confirms delivery and not that the episode was heard. One measures listening on one app; the other measures file delivery across every app that fetches from your feed.
Why doesn't Spotify show up in my host's or prefix's app split?
Spotify copies your episodes onto its own servers and plays them from there, so those plays never touch your feed's analytics prefix — no prefix-based measurement can see them, PodLink's included. Spotify reports those plays in Spotify for Creators, whichever host you use, and in Megaphone when that is the host. They are not a line a hosting dashboard is generally expected to show. When you put two windows side by side you're adding them together, not catching an error.
Why does Apple Podcasts Analytics say “Not Enough Data”?
Apple's data-requirements page says that at least five unique users must play content from your show within the selected time frame for the metric you selected; below that threshold the dashboard shows “Not Enough Data” instead. Apple also notes that diagnostics and usage information might be delayed by up to 72 hours, so a quiet new episode can take a few days to appear.
Should I add my Apple, Spotify and host numbers together?
Our advice: no. Apple plays, Spotify plays and downloads are different units, so a sum of all three is not a real quantity. Spotify serves plays from its own servers and reports them in Spotify for Creators, whichever host you use, and in Megaphone when that is the host. That count and a download count from the feed are non-overlapping audiences. Keep every number in its own labelled window, and do not add them.
Which number do I give a sponsor?
Downloads, with the method named. The IAB Tech Lab's measurement guidelines are the definitions podcast advertising is priced against, and marketplaces ask for downloads rather than platform plays — what they expect to see in a kit is covered in the podcast media kit guide. Our advice: give the sponsor a number they can check at the source rather than a screenshot, and label its time window. Platform dashboards are useful supporting evidence for engagement — Apple's engaged listeners and Spotify's completion rates say things a download count cannot — but the bookable unit is the download.
Where do PodLink's download numbers come from?
From OP3, the Open Podcast Prefix Project, which describes itself as a free and open-source podcast prefix analytics service and says every show it measures automatically receives a free, public stats page with industry-standard podcast download metrics. You add the prefix once in your host's settings, downloads are measured there, and PodLink reads them back and charts them — by day, per episode, by app, country and US state, with a “measuring since” date so numbers from before the prefix aren't mistaken for a drop. Because the counter is independent and public, a sponsor can check the same counts without you.

Sources

  • Apple Podcasts for Creators — Analytics (metric definitions: Followers; Listeners = played or watched more than zero seconds; Engaged Listeners = at least 20 minutes or 40% of an episode; Plays = duration greater than zero seconds; Top Countries/Regions and Top Cities = unique devices; data appears only once at least five unique listeners play content; default range 60 days; Performance tab compares 7/14/30/60 days after release against median, average or top episode; Apple does not provide third-party analytics support and points to your hosting provider for downloads; undated, footer © 2026; accessed 2026-11-11)
  • Apple Podcasts for Creators — Data requirements and troubleshooting (data is aggregated with no personally identifiable listener information, gathered from Apple devices plus 3rd party (Alexa, Porsche, Tesla); at least five unique users must play content in the time frame; data days run 12:00 a.m. to 11:59 p.m. UTC and may be delayed by up to 72 hours; undated, footer © 2026; accessed 2026-11-11)
  • Spotify for Creators — Analytics glossary (Plays = any episode watched or listened to for at least 30 seconds on Spotify, updates every 15 minutes; Audience = distinct people who played, updates every 24 hours; “Plays & downloads” and “Downloads” metrics are available only for creators who host with Spotify for Creators; episode completion = at least 95% of the way through; impressions update every 48 hours; undated; accessed 2026-11-11)
  • Spotify for Creators — Introducing plays on Spotify (plays are reported in Spotify for Creators whichever host the show uses, and exact play counts stay visible in Spotify for Creators and Megaphone; not a generic hosting-dashboard figure; published 2025-05-06, updates through 2025-10-06, accessed 2026-11-12)
  • RSS.com Help — Why are there differences between RSS.com analytics numbers and numbers from Spotify/Apple Podcasts? (a hosting provider's own explanation: following IAB guidelines it counts a download when at least 60 seconds of the episode file is delivered to a device, once per episode, per listener, per day (IAB v2.2 certified); “Spotify counts a play at 30 seconds, close to the Alliance for Measurement in Podcasting (AMP) definition. Apple counts any play over 0 seconds”; a download confirms delivery, not that the episode was heard; apps only track their own registered users, which is why they can show demographics and hosts cannot; hosts do not define downloads identically, so totals may look higher or lower after migrating; undated; accessed 2026-11-11)
  • IAB Tech Lab — Podcast Measurement Technical Guidelines (the standards page for the guidelines podcast advertising is priced against (Version 2.3 in GitHub): podcast measurement is based on server logs because, unlike other digital media, there is no open connection between the consumer's device and the content server, and “this nuance produces different metrics”; page last updated September 29, 2026; accessed 2026-11-11)
  • OP3 — the Open Podcast Prefix Project (describes itself as a free and open-source podcast prefix analytics service; every show measured automatically receives a free, public stats page with industry-standard podcast download metrics and data exports; codebase auditable on GitHub; an independent project; undated; accessed 2026-11-11)
  • PodLink facts are PodLink’s own published copy; see download analytics and pricing.

One number a sponsor can check

Keep reading Apple and Spotify for depth. For the number you put in front of other people, connect the feed your host gives you and your downloads are measured independently, per episode, on the free plan with no card.