Megaphone prefix not working? Check these causes

If your Megaphone prefix is not working, confirm that the custom prefix is enabled and saved for the correct podcast before changing anything else. Then compare the exact URL with Podder, inspect a current RSS enclosure, test episode playback, and look for fresh activity after the installation time.

Megaphone provides a documented custom-prefix control. Use that control instead of hand-editing enclosure URLs or adding an undocumented redirect elsewhere.

Megaphone prefix not working: check these causes

Work through the checks in order and change one item at a time. Preserve the show name, feed URL, prefix, and test time so support can reproduce the same request.

1. The custom-prefix toggle is off or the change was not saved

Megaphone's official Custom Prefixes guide gives the current route: select the podcast from Podcasts, open the Settings icon, choose Megaphone Settings, and scroll to Feed Prefixes. Turn on Enable custom prefix for your feed URLs, place the prefix in the Prefixes box, and save at the top of the page.

Fix: open the intended podcast, enable the toggle, enter the prefix, and save. Follow the current Megaphone prefix installation guide beside Megaphone's own documentation.

2. The URL contains an extra character or belongs to another show

Megaphone says the prefix should be exactly what the third-party provider supplied, without extra spaces or characters. A copied placeholder, missing character, or URL from another show can leave playback intact while sending activity to the wrong place or nowhere useful.

Fix: copy the unique prefix again from the matching show in Podder. Compare it character by character with the value in Megaphone, then save. Do not repair it from memory.

If several people manage the feed, keep the show name and prefix together in the change record. What is a podcast prefix? explains where this URL sits in the media request path.

3. The feed does not contain the saved prefix

Megaphone says the saved custom prefix appears before each enclosure URL in the RSS feed. The dashboard setting is only one side of the verification. The public feed must publish the same value.

Fix: open the current public RSS feed and inspect a published episode's enclosure URL. Confirm that it begins with the assigned prefix and continues to the Megaphone-hosted media URL. If the value is absent after saving, capture the podcast name, feed URL, episode title, expected prefix, and a screenshot of the setting for Megaphone support.

Do not manually rewrite an episode enclosure. That can hide the actual configuration issue and create a second request path nobody owns.

4. The prefix appears, but episode audio fails

A working analytics setup must preserve delivery. Test a published episode through a normal public listening route. You are checking that the prefixed request resolves and the audio starts without an error.

Fix: if playback failed after the latest prefix change, preserve the failing episode URL and test time. Remove only the latest change through Megaphone's documented control if service restoration requires it, then contact Megaphone and Podder support with the saved evidence. The general Podder prefix installation guide explains why playback comes before dashboard interpretation.

5. Playback works, but Podder shows no earlier activity

A prefix begins observing requests after installation. It cannot recreate downloads that occurred before it was present. Megaphone's third-party data guidance says the first day can contain only partial data and older episodes can have a gap between release and prefix installation.

Fix: record the save time, play one published episode through a normal route, and check for new activity after normal processing. Keep Megaphone as the historical source and do not use old totals as the installation test.

The two dashboards may not match.

Different totals do not prove that the prefix is broken. Megaphone lists download windows, time zones, blocked IPs, user-agent treatment, and high-density IP rules among the reasons another provider may report a different value.

Fix: match the podcast, episode, dates, and post-installation period. Label each source and follow its trend. Use how to measure podcast downloads to avoid combining unlike delivery series.

How to verify the fix

1. Confirm the correct podcast is open in Megaphone.
2. Confirm the custom-prefix toggle is enabled and the exact Podder URL is saved.
3. Inspect one published episode enclosure in the public RSS feed.
4. Play that episode and confirm uninterrupted audio.
5. Record the test time and check for new Podder activity.
6. Compare only the overlapping reporting period.

If playback works but fresh activity remains absent, send support the podcast name, feed URL, tested episode, exact prefix, screenshot of Feed Prefixes, and test time. That is more actionable than a screenshot of two unmatched totals.

FAQ

Where is the custom prefix setting in Megaphone?

Select the podcast, open Settings, choose Megaphone Settings, and scroll to Feed Prefixes.

Should a new Megaphone prefix show old downloads?

No. Test activity after the installation time and retain Megaphone for earlier host history.

Why do Megaphone and Podder totals differ?

The providers can apply different windows and processing rules. Compare matched periods without requiring identical totals.

Ready to connect the correct Megaphone show after verification? Start with Podder Analytics.