Two people playing the same podcast episode frequently hear different advertisements. The audio is assembled at the moment of download rather than existing as one fixed file on a server.
Baked-in ads could not be changed
Early podcast advertising was recorded into the episode by the host, so the file contained the spot permanently and every listener heard the same read forever.
That worked while podcasts were small, but it meant an advertiser paid for a fixed audience at one moment while continuing to receive downloads long afterward.
It also meant an expired campaign kept running. Back catalogs accumulated advertisements for offers that had ended, occupying inventory that could have been resold.
Insertion happens at the request
Dynamic insertion stores the episode with marked slots at defined positions. When a player requests the file, a server assembles the program audio and the current advertisements together.
Because assembly happens per request, the response can vary with what the request reveals: approximate location from the network address, device type, and time of day.
The listener receives a single continuous audio file, so the experience is unchanged even though no two files delivered need be identical.
It makes the back catalog sellable
Older episodes continue to be downloaded for years. With insertion, those downloads carry current campaigns rather than expired ones, converting an archive into ongoing inventory.
Advertisers can also buy by audience volume rather than by episode, purchasing a number of impressions distributed across a show or a network of shows.
Campaigns can start, stop and change mid-flight, which is what regular advertising buyers expect and what baked-in reads could never provide.
Measurement follows the download, not the listen
Podcast delivery uses a simple file request, so the medium counts downloads. Whether the file was played, and how far, is not visible to the host by default.
Industry technical guidelines define what may be counted, filtering automated requests and partial fetches so different publishers report on a comparable basis.
Attribution products attempt to connect exposure to later action, and prefix redirect services track downloads before the file reaches the listener's application.
Host reads survive inside the mechanism
Advertisers still value a host's voice, so many spots are recorded by the host and then inserted dynamically rather than edited permanently into the episode.
This preserves the endorsement quality while keeping the flexibility, which is why a familiar voice can be heard reading for a sponsor the show no longer works with.
The tradeoff is coherence. A spot recorded separately cannot reference the episode around it, so the tightest integrations are still produced the old way.