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.
| Dashboard | Its units | What counts | Who it can see | Source |
|---|---|---|---|---|
| Apple Podcasts Analytics | Plays, Listeners, Engaged Listeners, Followers | A 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 Creators | Plays, Audience, Followers, completion rates, impressions | A 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 prefix | Downloads | File 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.
The number you can hand a sponsor
A sponsor conversation eventually lands on one question: how do you know? A screenshot of any dashboard — Apple’s, Spotify’s or your host’s — answers it with “trust me”. A download count from an independent, publicly checkable counter answers it with a link.
That is how PodLink’s analytics are built: your downloads are measured by an open, independently run prefix — not a counter we operate — and PodLink reads them back and charts them: downloads by day with publish days marked, per-episode downloads for the first seven days and all-time with the pacing curve since publish, and splits by listening app, country and US state. Measurement starts the day you add the prefix and older episodes count from that day forward, never before — the dashboard says so with a “measuring since” date. The same numbers can live at a public Show Report link with a verify link to the source, so the person you are asking for money can check the count without you in the room. It is on the free plan, no card.
What a sponsor expects around that number — audience description, placements, pricing — is the podcast media kit guide; how the pitch itself works is how to get podcast sponsors. Bring Apple’s engagement depth and Spotify’s completion rates as supporting evidence; bring downloads as the number.