Castos prefix not working? Work through these causes
Open a source-aware analysis with this article as the primary source.
Add us to your Preferred Sources.
If your Castos prefix is not working, start by opening Settings for the correct podcast, then Distribution, then Advanced, and compare the saved value character by character with the one your analytics provider issued. Most failures are one of four things: the prefix sits on a different show, the URL is malformed, directories have not refreshed yet, or you are looking for activity that predates the install.
Change one thing at a time and re-test. Pasting the prefix again and refreshing the dashboard tells you nothing about which step broke.
Castos prefix not working: the causes in order
Castos's media file prefix documentation gives the current settings path: "In your Castos dashboard, click Settings for the podcast you would like to update," then "Click Distribution → Advanced," then "Enter the tracking prefix and click Save." Use that control rather than editing episode media URLs by hand.
1. The prefix is on the wrong podcast
The field lives inside one podcast's settings. On a multi-show account, saving it while the wrong show is selected produces exactly what you are seeing: a valid prefix, saved successfully, observing nothing for the show you care about.
Fix: open Settings for the show you actually want to measure, check Distribution and then Advanced, and confirm the prefix is present there. Add it separately to every show you want tracked.
2. The URL is malformed
Castos's documentation tells you to copy the entire prefix including the forward slash that appears at the end. A missing trailing slash joins the prefix directly to your media URL and creates a path that resolves to nothing.
Fix: copy the value straight from your Podder account rather than retyping it. Check the protocol, the domain, your unique identifier, and the final slash. Never paste a sample ID from a help article, including ours. Our Castos prefix installation guide has the exact path and format.
3. The feed changed but the directories have not caught up
Castos warns that adding the media file prefix modifies your RSS feed directly, and recommends testing on Apple Podcasts, Spotify and other platforms afterwards, noting that "RSS updates can take several hours depending on the directory, so wait a couple of hours before testing."
Fix: wait, then check your public RSS feed first. If the enclosure URLs in the feed carry the prefix, Castos has done its part and the remaining delay belongs to the directory.
4. A real episode does not play
A prefix sits in front of your audio file, so a broken value breaks playback as well as measurement. That is the fastest test you have.
Fix: open a published episode in a podcast app and play it. If playback fails, remove the prefix, save, confirm the episode plays again, and only then re-enter a freshly copied value.
5. You are looking at activity from before installation
A prefix can only observe requests that pass through it. It does not reconstruct the requests your host already recorded, so an empty dashboard on day one is the expected result rather than a fault.
Fix: note the installation date, publish or wait for new activity, and check again after a full day of normal delivery. Then compare only the period both sources cover.
A test order that isolates the problem
| Step | What you check | What a failure tells you |
|---|---|---|
| 1 | Prefix present under Settings, Distribution, Advanced for the right show | Wrong show or never saved |
| 2 | Enclosure URLs in the public RSS feed carry the prefix | Castos has not applied it |
| 3 | A published episode plays in a real app | The prefix value is malformed |
| 4 | New activity appears after a day of delivery | Nothing wrong, the window was too short |
Work down the list and stop at the first failure. Steps two and three catch most cases, and they take about five minutes between them.
What to expect once it works
Your Castos figures and your prefix figures will not match exactly, and that is normal. Castos applies its own filtering under the IAB Podcast Measurement Guidelines, and a prefix provider applies its own rules at a different point in the request path.
Keep them on separate lines:
- Castos listens: requests measured by your host, after Castos's exclusions
- Prefix analytics: requests observed by the prefix from its install date onward
- Apple Podcasts and Spotify: plays and engagement measured inside those apps
For what each figure counts, read what is a podcast download? and IAB podcast measurement explained. For the ongoing reporting routine, use our Castos analytics guide and how to track podcast analytics.
Six months later, the dated install note is what stops somebody reading the start of a new data series as a collapse in delivery. Put it in the same place you keep sponsor reports, not in a message thread.
Install the Podder prefix on your Castos show and keep your host figures and prefix figures on separate lines from the start.
FAQ
Where is the prefix field in Castos?
Open Settings for the podcast you want to change, then Distribution, then Advanced. Enter the tracking prefix there and save. The field is per podcast, so a multi-show account needs the prefix added to each show separately.
Does the Castos prefix need a trailing slash?
Copy the prefix exactly as your analytics provider gives it, including the forward slash at the end. Castos's own documentation tells you to copy the entire prefix including that trailing slash, and a missing one produces a malformed media URL.
Will installing a prefix in Castos import my old downloads?
No. A prefix can only observe requests that pass through it after it goes live. Keep the earlier Castos history as its own baseline and compare only the overlapping period.
See who's actually listening.
Podder gives you audience demographics, per-episode analytics, and chart tracking. The Chartable alternative that goes deeper.
Start free