Acast prefix not working? Acast does not support it

Q: Can I add the prefix manually to Acast episode URLs?

No supported manual workaround exists. Acast says prefixes place an intermediary between its hosting system and podcast apps, which prevents Acast from standing behind feed-delivery troubleshooting.

Q: Can I still see downloads without a prefix?

Yes. Use the Overview tab in Acast Insights for the host's native download totals, current-day estimates, episode filters, and CSV exports.

If your Acast prefix is not working, the issue is compatibility, not a missing setup step. Acast says it does not support RSS feed prefixes, so a third-party analytics prefix, including Podder, cannot be installed on an Acast-hosted show. Do not edit enclosure URLs or look for an undocumented prefix field.

Use Acast's native Insights dashboard for download reporting while your show remains there. If third-party prefix analytics is a firm requirement, treat hosting as a separate decision and assess the operational cost before moving anything.

Acast prefix not working: this is an unsupported setup

A podcast analytics prefix sits before the media URL in an episode's RSS enclosure. When a podcast app requests the audio, that request passes through the analytics service before reaching the host.

Acast's official article on stats services and intermediaries states directly that Acast does not support prefixes. Its broader feed intermediaries documentation explains why: an intermediary introduces another point where feed or media delivery can fail, and Acast cannot troubleshoot the full delivery path when another service sits between Acast and the podcast app.

That policy applies to the mechanism, not only to one vendor. Podder uses an analytics prefix, so there is no supported Podder installation route for Acast. Our explanation of what a podcast prefix is shows where this redirect normally sits in a supported feed.

Do not try these workarounds

An unsupported integration is not fixed by making the feed harder to inspect. Avoid these changes:

Do not paste a prefix into an unrelated Acast field.
Do not manually rewrite episode enclosure URLs.
Do not submit a second, modified feed to podcast directories as a shortcut.
Do not chain another feed intermediary in front of Acast.
Do not treat one successful playback test as proof that the setup is approved or durable.

A manual redirect can add the same delivery risk behind Acast's policy. It also leaves you with a request path that neither provider has agreed to support. If playback later breaks, the extra layer makes it harder to locate the failure.

If you already made one of these changes, preserve the original Acast feed URL and a copy of the current feed before undoing it. Then return to the host-supported configuration and test a published episode through a normal podcast app.

Use Acast Insights instead

Acast provides native host analytics in Insights > Overview. Its Overview tab documentation describes recent and all-time totals, a separate current-day estimate, custom periods, episode selection, daily, weekly, or monthly grouping, and CSV export.

Use that report for delivery of the audio hosted by Acast. Keep the selected period, episode filters, time zone, and export date with your notes. Acast displays the dashboard in your local time zone but exports CSV data in UTC, so daily figures can differ around the boundary.

Our Acast analytics guide gives you a repeatable native reporting routine. For broader measurement, how to measure podcast downloads explains how to keep host delivery separate from engagement inside Apple Podcasts, Spotify, and other listening apps.

A tracking pixel is not an analytics prefix

Acast's intermediary documentation distinguishes a tracking pixel used for a particular advertising campaign from a prefix applied to the show's media enclosures. These tools answer different questions and use different implementation paths.

Acast's willingness to discuss an advertiser's tracking pixel does not mean the host supports a show-level Podder prefix. If an advertiser asks for campaign tracking, take the exact requirement to Acast's team. Do not translate that request into a permanent analytics redirect yourself.

Decide whether the missing prefix is a real constraint

Before considering a host move, name the reporting gap. Acast Insights may already answer questions about download delivery, episodes, periods, and trends. Listening platforms can supply their own retention, completion, follower, and audience signals.

If your requirement is specifically independent prefix-based measurement across podcast apps, Acast's policy is a genuine constraint. Compare supported hosts on more than prefix access, including feed ownership, redirect process, monetization, dynamic ad behavior, team workflow, analytics history, and support. A move starts a new measurement boundary and should not be presented as a quick troubleshooting trick.

Do not expect a future prefix to recreate earlier Acast requests. Earlier host analytics stay in Acast, while a supported prefix can observe only new requests after installation. Keep exports from the old and new systems as separate series rather than merging them into a false continuous total.

Use our podcast analytics guide to decide which questions belong to the host, the listening app, or an independent measurement layer.

How to close the troubleshooting ticket

Document the outcome clearly so nobody repeats the same setup attempt:

Record that Acast does not support RSS analytics prefixes.
Remove any unsupported manual feed or enclosure change.
Confirm that the public episode plays from the normal Acast feed.
Use Acast Insights as the host download source.
Record any unmet independent-measurement requirement for a later hosting review.

This is a product-policy limitation, not a Podder account error. There is no activation delay to wait out and no prefix syntax change that will make the integration supported.

FAQ

These answers summarize the supported path: use Acast's native reporting, avoid manual feed changes, and review hosting only if independent measurement is required.

Does Acast support the Podder analytics prefix?

No. Acast does not support third-party RSS analytics prefixes, so Podder cannot be installed on an Acast-hosted show.

Can I add the prefix manually to Acast episode URLs?

No supported workaround exists. Manual changes add an intermediary that Acast says it cannot troubleshoot across the full delivery path.

Can I still see downloads without a prefix?

Yes. Use Insights > Overview for Acast's native host download reporting, and use each listening platform for engagement visible only inside that app.

Staying on Acast? Start with the native workflow in our Acast analytics guide and keep unsupported prefix changes out of the feed.