Where are downloads shown in Castos?

Log into Castos and click Analytics in the main navigation. The Listens tab holds the download and stream totals, and you can filter by podcast and by date range from any tab.

Does Castos separate downloads from streams?

No. Castos documents that a listen is recorded when the file has been requested by an app, browser or platform and has either been downloaded or streamed. Both events land in the same figure.

How do I export Castos analytics for a sponsor?

Open Analytics and then Download Reports. You can download Listens, Spotify Listens and Followers as CSV, or select Build Report to assemble a PDF with chosen sections, a custom front page and Castos branding removed.

Castos downloads: where to find them and export

Castos downloads are in the Analytics section of your dashboard. Log into Castos, click Analytics in the main navigation, and read the Listens tab for the totals. From any tab you can filter by podcast and by date range, and the Download Reports tab is where you export the figures for someone else to read.

Castos does not split downloads from streams, so settle that before you quote a number to anyone. Its analytics documentation states that a listen is recorded when "the file has been requested by a mobile app, web browser, or platform (like Apple Podcasts) and has either been downloaded or streamed." So if a sponsor asks how many people streamed rather than downloaded, the Castos dashboard cannot answer that question at all.

How to see Castos downloads

Log into your Castos account and click Analytics in the main navigation.
Stay on the Listens tab for the download and stream totals.
Set the podcast filter if you host more than one show, then set the date range.
Open Episodes to see which releases pulled the requests inside that window.
Open Platforms & Apps for the apps that requested the audio. This tab also filters by episode.
Open Geographic Stats for the countries and cities inferred from those requests.
Open Download Reports when you need the numbers outside the dashboard.

Those five tabs come from Castos's own analytics walkthrough, which also confirms every tab filters by podcast and by date range. Set both filters before you read anything. A total that quietly includes a second show is the most common way a Castos review goes wrong.

For the fuller reporting routine on this host, use our Castos analytics guide alongside how to track podcast analytics.

Exporting for a sponsor or a spreadsheet

The Download Reports tab handles both jobs, and the two formats serve different readers.

Export	What you get	Use it for
CSV	Listens, Spotify Listens and Followers as raw rows	Your own spreadsheet or dashboard
PDF	A built report with chosen sections	Sending to a sponsor or a co-host

Castos documents the report builder: set the date range and either one podcast or All Podcasts, then select Build Report to show or hide sections such as Listens, Spotify Listens, Followers, Top Platforms and Apps, and Top Countries and Cities. The same documentation notes you can customise a front page and remove Castos branding, and that report building sits on the Growth and Pro hosting plans.

Export before you need the history. A CSV saved monthly gives you a record that survives a plan change, a host migration, or a dashboard redesign.

What Castos already filters out

Castos states that it follows the IAB Podcast Measurement Guidelines and applies seven exclusions under them, covering preload requests, bot traffic, known data centres, VPN sources, duplicate Apple Watch requests, and listens under one minute.

That filtering is why a Castos number is usually lower than a raw server log, and it is also why the figure is defensible to a sponsor. A count that includes bots is bigger and worth less. If you want the standard itself explained, read IAB podcast measurement explained.

Why Castos and Spotify disagree

Castos addresses the gap directly, saying that analytics from an app like Apple Podcasts or Spotify "may differ from the counts Castos provide because they may count a listen/download differently than we do."

That is the whole explanation, and it means a mismatch is not a bug to chase. Keep the sources in separate columns:

Castos listens: requests for your audio file, filtered under Castos's IAB-aligned rules
Apple Podcasts and Spotify: plays, followers and engagement measured inside those apps
Prefix analytics: requests observed after a third-party prefix is installed

Compare episodes at the same age inside any one of those sources, and never add two of them together. For the vocabulary behind each one, read what is a podcast download? and podcast downloads vs listens.

Adding Podder alongside Castos reporting

Castos supports a tracking prefix in its own settings, so no support ticket is needed. Open Settings for the podcast, go to Distribution and then Advanced, enter the prefix, and save. Our Castos prefix installation guide walks the same path with the Podder-specific values.

The prefix observes requests from the moment it is live, and it cannot recreate what Castos already recorded. Note the installation date, compare only the overlapping period, and keep the earlier Castos history as its own baseline.

Castos's media file prefix documentation gives that settings path and warns that adding a prefix modifies your RSS feed directly. It recommends testing episodes on Apple Podcasts and Spotify afterwards, allowing a couple of hours for directories to pick up the change. Check that a real episode still plays before you go back to reading charts.

Start tracking your show with Podder to see cross-app request data next to your Castos reports.