Understand the two DAI models: client-side insertion (the podcast app fetches ad audio separately and stitches it in the player) and server-side insertion (the hosting platform or ad server stitches the ad audio into the episode file at download time before sending it to the listener) — server-side is more common in podcasting because it works in any app without special player support
Mark ad break positions in your audio file when uploading to a DAI-capable hosting platform — ad markers define pre-roll, mid-roll (by time offset), and post-roll positions; the hosting platform's ad server fills these slots at request time based on listener signals
Integrate with a VAST-compatible ad server: VAST (Video Ad Serving Template) is the IAB standard used to describe ad content and delivery — podcast ad servers accept VAST tag URLs from advertisers and use them to fetch and stitch audio ad creatives into the episode at the marked positions
At request time, the hosting platform's ad server receives listener context (IP address, user agent, episode ID) and makes a real-time ad decision, selecting an ad creative from the configured VAST tags and stitching the audio into the response before delivery
Implement frequency capping and targeting at the ad server level — most enterprise DAI platforms allow targeting by geographic region, device type, and episode topic, and cap how many times a listener hears the same ad across a configurable time window
Measure downloads according to IAB Podcast Measurement guidelines to ensure ad impression counts are auditable — a download is counted only after a qualifying threshold of data transfer, not on the initial request
Known gotchas
Server-side DAI makes the episode URL dynamic — each listener request generates a unique stitched audio file, which prevents direct sharing of episode URLs and can complicate download analytics if not handled correctly by the platform
VAST tags in podcasting are adapted from video ad standards — not all VAST features are applicable to audio-only delivery; work with your ad server vendor to confirm which VAST elements are parsed and which are ignored
Ad stitching introduces latency at download time — the hosting platform must fetch and transcode ad audio before delivering the episode; choose a DAI provider with edge infrastructure to keep this latency acceptable for listeners
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp