What is ad pod podcast delivery?

What is ad pod podcast delivery? An ad pod is an ordered group of ads intended to run inside one advertising break. A pod may contain a first, second, and later spot, while the break describes the place in the episode where that group can appear.

What is ad pod podcast delivery?

The clearest standard definition comes from the IAB Tech Lab VAST 4.3 specification, which covers in-stream video and audio advertising. VAST says multiple ads form a pod when their separate <Ad> elements use unique sequence values. A player that supports ad pods plays those sequenced ads in numerical order and should play as many as it can.

That definition is narrower than casual uses of "pod" for any cluster of sponsor messages. VAST also allows non-sequenced stand-alone ads in a response. Those ads belong to an "ad buffet" from which a player may choose, while sequence values create the ordered pod.

VAST applies to compatible streaming audio and video systems. The IAB Podcast Technical Measurement Guidelines v2.3 do not define "ad pod" as a core podcast measurement term. For downloadable podcast inventory, use the label only when the host or ad platform documents how it groups and orders multiple ads in one break.

How a pod fits inside a podcast break

A publisher first creates or marks a break, such as a pre-roll before the main content or a mid-roll at a planned transition. The delivery system can then fill that break with one ad or several ads.

A three-ad pod might contain:

1. the first sold campaign;
2. a second campaign that passes category and eligibility rules;
3. a house ad or another eligible campaign.

Order can affect the agreement. "First in pod" is a more precise placement than "mid-roll" because one mid-roll break can hold several spots. Record the break position, pod position, maximum ad count, creative duration, and competitive exclusions before launch.

The pre-roll, mid-roll, and post-roll guide covers break positions. Our dynamic ad insertion guide explains campaign selection and pacing around those positions.

Filling a pod requires explicit rules

An ordered response does not guarantee that every ad will play. VAST 4.3 allows a player to truncate ads at the end when the full pod cannot fit into a time-limited break or violates limits supplied by the player. It also describes substitution with an available stand-alone ad when one pod entry fails.

Podcast delivery introduces another boundary. Open-RSS episodes are often downloaded or progressively downloaded, and many apps do not return detailed client-side playback events. The podcast measurement guideline says dynamically inserted ad content must be fully downloaded before it can count as "Ad Delivered." Each ad therefore needs its own delivery evidence.

Do not multiply episode downloads by the planned number of ads. A request may fail to reach a later break, a campaign may leave one position empty, or only part of a pod may be delivered. The podcast ad impression glossary shows how to label server-side delivery and client-confirmed play separately.

What to put in the campaign record

For every podded placement, retain:

• show, episode pool, and break position;
• maximum pod length in ads and seconds;
• the purchased sequence position, if guaranteed;
• campaign priority and eligibility rules;
• category or competitor exclusions;
• creative ID and duration for each ad;
• fallback behavior for an empty or failed position;
• delivery source and counted event for each creative.

Listen to a real served episode before launch. Check the transition into the break, the gap between ads, loudness, disclosures, and the return to editorial audio. Repeat the check after changing creative or pod rules.

The order should also appear in the final report. "Mid-roll ad" leaves out whether a sponsor ran first or fourth in a crowded break. Pair each creative with its sequence, delivered count, playback metric when available, and any underdelivery or substitution.

Keep pod, slot, and impression separate

A break is the interruption in the program. A slot is one available placement within or at that break. A pod is the ordered set of ads selected for the break. An impression is the measured delivery or playback event attached to one ad under a stated method.

Those fields solve different audit questions. Feed or platform metadata can declare inventory without proving that it was sold or filled, as the Libsyn RSS ad slot metadata review demonstrates. Delivery records then show what the system sent, and advertiser-side evidence covers response.

Start with Podder Analytics for episode delivery context, then reconcile each pod position against the ad server's creative-level report.