What Is a Podcast Analytics Prefix?
A podcast analytics prefix is a web address added in front of each episode’s audio file URL in a podcast’s RSS feed, so that every download request passes through a measurement service, which logs it and then redirects the listener’s app to the real file. beehiiv’s help center puts it this way: “Think of a podcast prefix like a tracking pixel for your audio files” (beehiiv Support). The free Open Podcast Prefix Project (OP3), for example, asks podcasters to add https://op3.dev/e/ to the front of each episode URL (OP3).
Prefixes are how ad-attribution firms, sponsorship marketplaces and ranking services see a show’s downloads without hosting it. They are also a dependency: if the company behind a prefix shuts down, every episode URL in the feed points first at a server that may no longer answer. Our report on what changed in the podcast download rules explains how prefix measurement fits into the IAB Tech Lab’s counting guidelines.
Why Does This Matter Now?
Because Podcorn’s prefix stops working when Audacy closes the service on November 1, 2026, and thousands of shows still use it. Podcorn launched in 2019 and was “acquired by Audacy for $22.5mn in 2021,” later becoming Audacy Creator Lab; Podnews reported on August 28, 2026 that “Audacy is to close its podcast hosting and monetisation service, Audacy Creator Lab, on Nov 1” (Podnews). On October 28, Podnews said “There are 13,362 shows with the Podcorn URL still in them” and published a spreadsheet of them sorted by host (Podnews; Podnews spreadsheet).
The same steps apply to any prefix you no longer use, from a past sponsor’s attribution tool to a ranking service you have stopped paying for. Transistor’s support page lists “Chartable, Podcorn, Podkite, Backtracks and Voxalyze” as services that “are no longer available” (Transistor Support).
How Do You Remove a Prefix at a Glance?
You find the prefix in your live feed, remove it in your host’s settings, and confirm the feed has changed. The table summarizes the steps.
| Step | Action | Expected result |
|---|---|---|
| 1 | Open your public RSS feed and search it for the prefix domain (for Podcorn, pdcn.co) | You know whether, and where, the prefix appears |
| 2 | List every prefix in the chain and decide which to keep | A short list of live services you still use |
| 3 | Find your host’s prefix or third-party tracking setting | The field or toggle that controls the prefix |
| 4 | Delete or switch off the dead prefix and save | The host stops adding it to new and old episodes |
| 5 | If the host has no setting, ask its support team | The host removes it for you |
| 6 | Reload the feed and test an episode download | Enclosure URLs start with a live address and play |
| 7 | Note the date in your analytics records | Any download blip can be explained later |
Time: 10 to 20 minutes, plus up to a day for apps to refresh (our estimate; beehiiv cites up to 24 hours). Tools: host admin login, a web browser. Cost: free. Skill level: beginner.
What Do You Need Before Starting?
You need admin access to the podcast’s hosting account and the address of its public RSS feed. Specifically:
- Host login with settings rights. On most platforms, only an owner or admin can change feed settings.
- Your RSS feed URL. It is shown in the host dashboard, usually under distribution or settings.
- A list of the measurement services you use. Sponsors sometimes ask for an attribution prefix during a campaign; check with whoever booked your ads before deleting anything still in contract.
- A note of your current download numbers. A baseline makes it easier to spot and explain any change afterward.
Step 1: Check Your Live Feed for the Prefix
Open the RSS feed in a browser and search the page for the prefix’s domain. In each episode’s <enclosure> tag, the url attribute is the audio address apps download. A prefixed URL starts with the measurement service’s address and ends with your host’s address, for example https://pdcn.co/e/ followed by the original file location (the prefix form is from Audacy Creator Lab Help). Use your browser’s find function for pdcn.co, or for any other prefix domain you are checking. You can also look up your show in the Podnews spreadsheet, which lists Podcorn-prefixed shows by host.
Step 2: Map Every Prefix in the Chain
Write down every prefix in the enclosure URL, in order, because several can be chained. beehiiv says that when several prefixes are enabled “they chain together: each provider captures data and passes the request to the next one in sequence,” and allows “up to five prefixes to a single show” (beehiiv Support). OP3 says existing prefixes do not need removing to add it, and “there can be more than one” (OP3). A single dead link anywhere in the chain is enough to break it, on our reading of how redirects work, so remove only the dead one and keep the live services you still need.
Step 3: Find Your Host’s Prefix Setting
Look for a setting called analytics prefixes, third-party tracking or similar; its location varies by host. The hosts whose documentation we read put it in these places:
| Host | Where the prefix setting is | How to remove | Source |
|---|---|---|---|
| Transistor | Podcast Settings page, “Analytics Prefixes” header menu | Untick the box and save (our inference from the enable steps). Transistor says it has already removed Podcorn’s prefix. | Transistor |
| beehiiv | Podcasts, your show, Distribution tab | Toggle the prefix off; “takes effect immediately” | beehiiv |
| Fireside | Dashboard, Settings, Advanced, “Third-Party Tracking Prefix” section | Help page covers adding only; clear the field or contact support | Fireside |
| Other hosts | Audacy says “Most podcast hosting platforms support analytics prefixes,” usually via “a specific field for the prefix” in your podcast’s settings | Clear the field, or ask support | Audacy Creator Lab Help |
Some hosts add prefixes only on request. If you cannot find a field, search your host’s help center for “prefix” before contacting support.
Step 4: Remove the Prefix and Save
Delete the dead prefix’s text or switch off its toggle, then save. On hosts that store the prefix once and apply it to every episode, a single change updates the whole back catalog. If you pasted a prefix into individual episode URLs by hand, or your host builds the enclosure from a custom field, you will need to edit each one. Leave other prefixes exactly as they were, including their order, unless a live provider tells you otherwise.
Step 5: Ask Your Host If There Is No Setting
If your host has no self-serve control, open a support request and ask it to remove the prefix from all enclosure URLs. Give the show name, the feed URL and the exact prefix text (for Podcorn, https://pdcn.co/e/), and mention the November 1, 2026 closure so the request is prioritized. Some hosts are acting without being asked: Transistor says it “has removed the Podcorn analytics prefix from user feeds before the closure” (Transistor Support). Check your own feed rather than assuming your host has done the same.
Step 6: Note the Change in Your Records
Record the date you removed the prefix, because changing enclosure URLs can move your download numbers. Transistor warns that removing Podcorn’s prefix “may result in a temporary spike in Spotify downloads.” Our report on the podcast download rules explains why: the IAB Tech Lab’s guidelines note that changing an episode’s enclosure URL, for example by adding a tracking prefix, can make apps download it again, and removing a prefix changes the URL too. Tell sponsors and anyone who reads your stats, and see our guide to reading Apple and Spotify podcast analytics for where to look.
Why Does a Dead Prefix Matter?
Because a prefix sits in the path of every download: if its server stops redirecting, apps cannot reach the audio, and the show stops working for new downloads. That is Podnews’s warning for Podcorn: “If you’re still using the analytics prefix then your show will stop working on November 1” (Podnews). The counts below show how far the prefix spread beyond Audacy’s own platform.
Number of podcasts, as counted by Podnews
Source: Podnews, daily updates of August 28 and October 28, 2026. Read October 28, 2026.
The two counts measure different things: the first is shows whose feeds still contain the Podcorn prefix, wherever they are hosted; the second is shows hosted on Audacy’s own platform. Both are Podnews’s analysis of Podcast Index data.
The chart shows that the prefix spread about 31 times further than Audacy’s own hosting platform, by our arithmetic: 13,362 prefixed shows against 426 hosted shows, so most of the affected podcasts are hosted elsewhere and depend on their own host to fix it.
A dead prefix also leaves a measurement gap. Audacy’s help page says “Audacy Creator Lab can only track downloads and listens from the moment the analytics prefix is set up for your show” (Audacy Creator Lab Help), so its data never covered your full history. Our recommendation: export any reports held only by a closing service before it goes, and keep your host’s own statistics as the record.
How Do You Verify It Worked?
Reload the public feed and confirm the prefix domain no longer appears in any enclosure URL, then play an episode. Search the feed again for the domain; the result should be zero. Copy one enclosure URL into a browser and check that the audio file loads. Within a day, open the show in Apple Podcasts or Spotify and play a recent and an old episode. Apple requires that each episode’s GUID “never changes” (Apple Podcasts for Creators); removing a prefix changes the URL, not the GUID, so episodes should not duplicate.
Common Problems and Fixes
| Problem | Likely cause | Fix |
|---|---|---|
| Prefix still in the feed after saving | Feed caching at the host or a CDN | Wait an hour, reload with a cache-busting query string, then contact support |
| Prefix gone in the dashboard but still on some episodes | Prefix was pasted into individual episode URLs | Edit those episodes, or ask the host to rewrite them |
| Apps still show the old URL | Apps refresh feeds on their own schedule | Allow up to 24 hours (beehiiv’s figure) |
| Downloads jump in one app | Changed enclosure URLs can trigger re-downloads | Note the date; Transistor says a spike may be temporary |
| Episodes appear twice in a directory | GUIDs changed during the edit | Restore the original GUIDs; Apple says they must never change |
| A sponsor’s report goes blank | You removed a live attribution prefix by mistake | Re-add it exactly as before |
What Not to Do
Do not remove every prefix to be safe. Consequence: sponsors lose attribution data and ranking services stop counting you. Correction: remove only the prefixes for services that have closed or that you no longer use.
Do not change episode GUIDs while editing. Consequence: apps may treat old episodes as new and duplicate them. Correction: change only the enclosure URL, which is what a prefix setting does.
Do not wait until the closure date. Consequence: if the prefix server stops redirecting, new downloads may fail from November 1. Correction: remove it now and check the feed the same day.
Do not assume your host has done it. Consequence: a show can break while you believe it is fixed. Correction: search your own feed for the domain.
Frequently Asked Questions
What is a podcast analytics prefix?
It is an address added in front of each episode’s audio URL in a podcast’s RSS feed, so download requests pass through a measurement service before reaching the file. beehiiv compares it to “a tracking pixel for your audio files.”
What happens if I leave the Podcorn prefix in my feed?
Podnews warns that a show still using the Podcorn analytics prefix “will stop working on November 1,” 2026, when Audacy closes the service. Remove it in your host’s prefix settings before then.
How many shows still use the Podcorn prefix?
Podnews said on October 28, 2026 that “There are 13,362 shows with the Podcorn URL still in them,” and published a spreadsheet sorted by podcast host.
Will removing a prefix change my download numbers?
It can. Transistor warns that removing Podcorn’s prefix “may result in a temporary spike in Spotify downloads,” because changing an episode’s enclosure URL can make apps download it again.
How long does it take for apps to see the change?
beehiiv says turning a prefix off takes effect immediately in the feed, but podcast apps may take up to 24 hours to refresh their cached copy.
Can a podcast use more than one prefix?
Yes. Prefixes can be chained, with each service passing the request to the next; beehiiv allows up to five per show, and OP3 says “there can be more than one.”
Sources and Methodology
This guide is built from Podnews’s reporting on the Podcorn and Audacy Creator Lab closure and the hosts’ and services’ own help pages, all read on October 28, 2026. The step order, time estimate, troubleshooting table and the advice to export data and keep live prefixes are our recommendations, not any host’s rules. We did not test removing a prefix on any host, and the hosts’ pages we read do not all describe removal.
- trade press Podnews, daily update, October 28, 2026. 13,362 shows; “will stop working on November 1”; spreadsheet. Read October 28, 2026.
- trade press Podnews, update of August 28, 2026. Audacy Creator Lab closure on November 1; Podcorn history; 426 hosted shows. Read October 28, 2026.
- trade press Podnews, spreadsheet of shows with the Podcorn URL. Lookup by host. Read October 28, 2026.
- platform documentation Audacy Creator Lab Help, “What is the Audacy Creator Lab analytics prefix”. Prefix form https://pdcn.co/e/; prefix field. Read October 28, 2026.
- platform documentation Transistor Support, “Which podcast prefixes does Transistor support?”. Settings location; closed services; Podcorn removal and Spotify spike. Read October 28, 2026.
- platform documentation beehiiv Support, “Using third-party podcast analytics prefixes”. Definition, chaining, five-prefix limit, removal and 24-hour refresh. Read October 28, 2026.
- platform documentation Fireside Help, “How do I add my Podcorn Analytics Prefix?”. Settings location. Read October 28, 2026.
- vendor OP3, Open Podcast Prefix Project. Prefix format; multiple prefixes. Read October 28, 2026.
- platform documentation Apple Podcasts for Creators, Podcast requirements. GUID “never changes”. Read October 28, 2026.