IAB rejects a new video podcast measurement framework

At the IAB Podcast Upfront in New York on September 17, 2026, IAB Tech Lab's Jason Adamski told the room that video podcast measurement does not need a new standard built from scratch. Two IAB standards already exist, and the actual problem is knowing which one applies to which part of a video podcast buy.

That matters for any show now shipping an episode as audio in an RSS feed and as video on YouTube. Pick the wrong standard for a line item and the numbers you send a sponsor will not reconcile with the numbers the sponsor's own verification vendor reports.

Which standard covers which part of a video podcast

The IAB's position is that the delivery environment decides the standard, not the format of the file.

The IAB Podcast Measurement Technical Guidelines v2.2 governs download counting, unique listener methodology, bot filtering, and dynamically inserted ad impression counting. It applies to open RSS distribution and to any audio-first consumption context. The guide is explicit that this includes Apple Podcasts' video support, where download-based measurement governs impressions whether the episode is watched or listened to.

The IAB Tech Lab and MRC Digital Video Served Impression Measurement Guidelines govern viewability, audibility, VAST-compliant ad delivery confirmation, and served impression counting. The viewability threshold is at least 50% of pixels in view for at least two continuous seconds. This standard applies where the visual surface is the primary delivery mechanism.

The video-capable podcatchers the guide names for RSS video delivery are TrueFans, Fountain, Overcast and Pocket Casts. If you want the mechanics of shipping video through the feed itself, we covered HLS video support in podcast hosting when the Podcast Standards Project published its support list.

The invalid traffic gap nobody mentions

The two standards do not treat invalid traffic the same way, and this is the detail most likely to burn a seller.

Version 2.2 bakes bot filtering and invalid traffic exclusion into the download methodology itself. A download that clears v2.2 has already been filtered. That is the same discipline behind what IAB podcast measurement actually counts on the audio side.

Under the Digital Video Served Impression Guidelines, invalid traffic detection depends on the measurement vendor and the environment. The guide states plainly that it is not guaranteed by the served-impression count alone. So a served video impression and an IAB-certified download are not the same quality of number, even when both look like clean integers in a spreadsheet.

What the IAB wants sellers to disclose

The guide sets out three principles: applying the existing standards by environment, disclosing across multiple platforms, and disclosing downloaded and time-shifted consumption.

For sellers, the concrete asks are:

1. Specify at the deal level which standard applies in each environment, and whether the platform can actually tell audio and video consumption apart.
2. Disclose how each platform defines its primary impression signal.
3. Identify where third-party verification exists and where reporting is platform-native only.
4. Report independently verified and platform-self-reported metrics separately. The guide says never aggregate them into a single undifferentiated summary.
5. Count download events as delivery confirmation under v2.2, and report them distinctly from playback-verified impressions.
6. Disclose the share of the audience consuming offline or time-shifted, so buyers can plan around delivery timing.

Buyers get their own list, and one item is worth reading as a seller. The IAB tells buyers to ask which standard governs each environment before trafficking, not after results come in, because measurement terms are negotiable before an insertion order is signed and effectively fixed once delivery begins.

Why this matters now

YouTube changed what a public view means in August 2026, and Podtrac's analysis found a large gap between counted views and engaged views on podcast content. A seller who adds a YouTube view count to a download total is now combining a platform-native number with no independent verification and a filtered number that has been through bot exclusion.

The guide also concedes what it does not fix. Recognizing the same listener across surfaces, and reporting deduplicated reach for a campaign that runs across them, stays an open problem. No framework stitches those touchpoints together yet. It cites eMarketer from February 2026 for the point that the U.S. podcast listening audience still exceeds the video-watching audience, so audio-mode measurement is not a legacy concern.

Podnews, which reported the talk, noted that the IAB put its guide and press release behind an email registration form, which is an odd choice for a document whose purpose is shared language.

What to do this week

Open your current sponsor reporting and split it by delivery environment before anything else. Anything arriving through the RSS feed sits under v2.2. Anything arriving through YouTube, Spotify Video or a CTV app sits under the video served impression standard.

Then check whether your report adds those two groups into one headline number. If it does, separate them and label the verification method for each. That single change is what the IAB is asking for, and it costs you nothing but a row in a table.

If you are not sure what your host is counting as a download in the first place, start with what a unique download actually measures and how an ad impression is counted. Getting those two definitions straight is the prerequisite for any of this.

Podder reports your prefix downloads against the IAB v2.2 methodology, so the audio half of that split is already filtered and ready to hand a sponsor. Start with the Analytics plan and put a defensible number on the line item you control.

Sources: Podnews, September 17, 2026 and the IAB guide Podcasts Continue to Evolve: When Listeners Become Viewers.