Anchor prefix not working? It is not supported

If your Anchor prefix is not working, stop looking for a formatting mistake. Anchor is now part of Spotify for Creators, and Spotify-hosted shows do not allow third-party analytics prefixes. Podder cannot be installed on that feed through a hidden setting, a manual enclosure edit, or a support-only field.

Use Spotify for Creators for native reporting while the show remains hosted there. Consider another host only if independent prefix measurement is a firm requirement and the wider hosting trade-offs justify a move.

Anchor prefix not working: confirm the hosting boundary

Podder's current hosting-provider directory labels Anchor NO PREFIX SUPPORT. The dedicated Anchor installation page is equally direct: Anchor does not support prefix URLs.

This rule applies to an Anchor-hosted feed now managed in Spotify for Creators. It does not mean every show available on Spotify has the same restriction. A show hosted elsewhere may still use Spotify for Creators for Spotify-specific reporting, while prefix support depends on the actual host.

1. Confirm who hosts the RSS feed

Anchor's name still appears in old bookmarks, tutorials, and account records. The current creator dashboard is Spotify for Creators. Before closing the issue, verify whether Spotify hosts the feed or merely receives it from another provider.

Find the system where you upload episodes and control the RSS feed. If that is Spotify for Creators, third-party prefix setup is unavailable. If another provider hosts the feed, check that provider's current prefix policy instead.

Anchor analytics explains where the old product's reports moved and how to find them now.

2. Stop searching for a prepend field

A compatible host normally exposes a field for a tracking or media prefix. Spotify for Creators does not expose a supported third-party analytics-prefix field for its hosted feeds. Browser changes, account roles, and retyping the URL will not create one.

Record the host-policy result and stop setup attempts. This is a compatibility decision, not a delayed installation.

3. Remove unsupported feed changes

Do not paste a Podder URL into a field meant for a website, RSS redirect, or another service. Do not rewrite media enclosures, create a second modified feed, or place an unapproved redirect in front of the audio.

Return the show to the Spotify-managed feed path. Play a public episode through a normal podcast app and confirm audio delivery. Keep a copy of the original feed URL and enclosure before reversing any manual change.

The general Podder prefix guide explains how a prefix works on compatible hosts. It does not override Spotify's hosting limitation.

Use Spotify for Creators Downloads instead

Spotify's official Overview analytics documentation gives the current path:

1. Log in to Spotify for Creators at creators.spotify.com.
2. Open Analytics from the selected show's dashboard.
3. Select Overview for the show-level metrics.
4. Choose the reporting date range you need.

Spotify defines Downloads there as downloads through the show's RSS feed on podcast platforms. That metric appears only when the show is hosted with Spotify for Creators. Spotify Plays are separate and count episodes watched or listened to on Spotify under Spotify's current play definition.

Keep those rows separate:

Do not add the figures together unless the interface presents a specific combined metric under its own definition. Label the source and selected range whenever you share a screenshot.

If you need the data outside the dashboard, Spotify's analytics export guide says web users can open Analytics, choose a chart and date range, then select Export for a CSV file.

Decide whether prefix analytics justify moving hosts

A host move affects the feed, media files, redirects, publishing access, distribution, monetization, and historical reporting. Treat it as an operating decision rather than a quick fix for one missing field.

Write down the unanswered requirement first. If Spotify for Creators Downloads, Plays, audience data, and exports support the decisions you make, native reporting may be enough. If your team requires an independent prefix for a recurring sponsor or network workflow, compare supported hosts against every publishing requirement before moving.

How to track podcast analytics can help assign each metric to the system that observed it before you change the setup.

After any move, verify the new feed and permanent redirect before adding a prefix through the new host's documented control. Record the completed feed-move date. A newly installed prefix observes future requests and does not import historical Anchor or Spotify reporting.

Close the Anchor prefix troubleshooting ticket

Use this checklist:

1. Confirm whether Spotify for Creators hosts the feed.
2. Record that Anchor and Spotify hosting do not allow third-party analytics prefixes.
3. Remove any unsupported manual redirect or enclosure change.
4. Confirm a public episode still plays.
5. Use Analytics and Overview for native Downloads and Plays.
6. Review hosting separately if independent prefix measurement remains mandatory.

If a supported host later becomes the right fit, start with Podder Analytics only after the feed move and redirect have been verified.