Dynamic Ad Insertion with Benecaster

Dynamic ad insertion (DAI) lets you swap ads in and out of your episodes without re-uploading audio — listeners in different regions hear different ads, expired campaigns are replaced automatically, and you can sell ad inventory against your back catalog. Benecaster works well with one category of DAI implementation and has significant limitations with another. This guide covers both so you can set things up correctly.

---

How Benecaster fits into ad delivery

Benecaster controls the RSS feed each subscriber receives. When a subscriber’s podcast app downloads an episode, it reads their private feed URL, finds the episode’s audio URL, and fetches that audio. Benecaster sets what appears in the feed — including the audio URL — but your server never serves the audio file itself.

That single fact determines whether a DAI implementation works with Benecaster.

---

Option 1: Redirect-prefix tracking (recommended)

Services like Podtrac, Chartable, and the Spotify Podcast Prefix work by wrapping your episode’s audio URL in a short redirect. Instead of pointing directly to your audio file, the URL in the feed points to their server first. Their server logs the download (noting the listener’s IP, time, and podcast app), then immediately redirects the app to your actual audio file.

This works transparently with Benecaster. Because Benecaster uses the audio URL you enter in the episode editor exactly as-is, you only need to wrap your audio file URL with the prefix before entering it:

Setup steps

1. Get your prefix URL from your tracking service. In Podtrac, for example, this looks like https://pdst.fm/e/. In Chartable it looks like https://chtbl.com/track/YOURCODE/.

2. Wrap your audio URL. Take your episode’s audio URL — wherever your file is hosted — and prepend the prefix:

   Before: https://cdn.yourpodcast.com/episode-100.mp3
   After:  https://pdst.fm/e/cdn.yourpodcast.com/episode-100.mp3
   

   Note that most prefix services drop the https:// from the wrapped URL — check your provider’s documentation for the exact format.

3. Enter the wrapped URL in the episode editor. In the Benecaster episode editor, go to the Media tab and paste the wrapped URL into the Audio File field. Benecaster includes this URL in every subscriber’s private feed — no further configuration needed.

4. Verify the redirect chain. After saving, copy your public feed URL and open it in a feed reader or paste it into Podcast Feed Validator. Find the episode’s <enclosure> tag and confirm it contains the prefix-wrapped URL, not the original. You can also paste the prefix URL directly into a browser — you should be redirected to your audio file within a fraction of a second.

Multiple prefix services

You can chain multiple prefix services by wrapping each URL inside the next:

https://pdst.fm/e/chtbl.com/track/YOURCODE/cdn.yourpodcast.com/episode-100.mp3

The first service in the chain logs the request and redirects to the second, which logs and redirects to the audio. Each service sees the listener’s real IP. Keep the chain short — each hop adds a small amount of latency, and some podcast apps have short timeout windows.

Adding subscriber-level download attribution

Prefix tracking tells you how many times an episode was downloaded and approximately where those listeners are. It doesn’t tell you which of your subscribers downloaded which episode. For that, enable the Download Proxy in Benecaster settings.

With the download proxy on, the episode’s URL in each subscriber’s feed points to your WordPress site first, not directly to the prefix service. When a subscriber downloads an episode:

1. Their app hits the download proxy URL on your site.
2. Benecaster logs the download: which subscriber, which episode, which podcast app, timestamp, and location.
3. Benecaster immediately issues a 302 redirect to the prefix-wrapped audio URL.
4. The prefix service logs its count and redirects to the actual audio file.

From a single download, you get two separate datasets: the prefix service’s IAB-certified public download count (for your media kit and ad reporting), and Benecaster’s per-subscriber episode attribution (for your own audience intelligence). They measure complementary things and don’t interfere with each other.

The only cost is one additional redirect hop. The download proxy is an opt-in setting — go to Benecaster → Settings → Analytics and enable the Download Proxy toggle.

---

Option 2: Platform-level audio stitching

Some podcast hosting platforms — Megaphone, Acast, Omny Studio, and similar — offer DAI by stitching ads directly into the audio at download time. The episode’s URL in the feed points to the platform’s ad server, which assembles the audio (your content plus the current ad inventory) on the fly and streams it to the listener’s app.

This category of DAI has significant limitations when used with Benecaster, because it depends on the platform serving the podcast feed — and Benecaster serves the subscriber feeds instead.

What works

Audio delivery itself works. The audio URL in each subscriber’s private feed points to the platform’s ad-serving endpoint, just as it would in any other feed. Subscribers’ apps hit the platform server, which stitches and delivers the audio. Ads are inserted and listeners hear them.

What doesn’t work

The platform’s subscriber-level analytics, frequency capping, and per-listener targeting depend on the platform serving the feed and knowing which listener is which. Because Benecaster serves the feeds, the platform has no visibility into your individual subscribers. Specifically:

• Per-listener frequency capping — the platform can’t prevent a single subscriber from seeing the same ad too many times across episodes, because it has no concept of your subscribers.
• Subscriber-level engagement data — download counts in the platform’s dashboard represent audio requests from all your subscribers combined, with no subscriber attribution.
• Targeting granularity — geo-targeting based on listener IP still works (because it’s a redirect chain and subscribers’ apps hit the platform directly), but any targeting that depends on listener identity or history doesn’t.
• Download reconciliation — your Benecaster subscriber count and the platform’s audio request count are separate figures with no automatic cross-referencing.

When platform-level DAI makes sense anyway

If you’re running a large show with a direct advertising relationship that requires a specific platform, you may need this setup despite the limitations. The audio delivery side works; you’re primarily giving up subscriber-level reporting in the platform’s dashboard. If that’s acceptable for your workflow, reach out to support@benecaster.com before configuring it — the specifics depend on how your hosting provider handles audio delivery and whether any of the limitations above are blockers for your ad partners.

---

Choosing the right approach

For most shows running paid subscriber models, prefix tracking is the right tool. It’s simple, works without any special Benecaster configuration, and when combined with the Download Proxy gives you both IAB-certified download data for sponsors and per-subscriber attribution for yourself.

Platform-level stitching is worth evaluating only if you’re on a hosting platform where it’s the primary or required DAI mechanism — and even then, confirm with your ad operations contact that the subscriber-attribution limitations are acceptable.