How do I validate an RTB House VAST tag?

Validate the creative the bid returns. If that payload is a live VAST URL or a wrapper, fetch it in the tester or inspector first, then validate the resolved XML.

Does RTB House publish VAST version or wrapper limits?

Not in the public sources used for this guide. RTB House documents video as a Prebid media type and has published a CTV and OTT campaign case, and it does not publish a VAST version matrix, wrapper-depth cap, or VPAID policy.

Does the RTB House Prebid adapter accept video?

Yes. RTB House's publisher integration guide lists banner, native, or video as the mediaTypes value for a placement, alongside a publisher ID and region assigned by RTB House.

RTB House VAST validator guide

Short answer: RTB House is a demand-side platform. Public material shows that it buys video, including connected TV and OTT, and that its Prebid adapter accepts a video media type. It does not publish a VAST version matrix or a wrapper-depth cap. Validate the creative the bid actually returns.

Need an RTB House VAST validator?

Use the validator when you already have the XML. Use the tester when the bid returned a live URL or a wrapper.

Validate the bid creative →Test a live tag URL →

Quick reference

Role	Demand-side platform
Public video evidence	Prebid media type includes video. A published CTV and OTT case used 15 to 30 second streaming video.
Prebid parameters	publisherId and region are required. bidfloor is optional.
Public VAST version matrix	Not published in the sources for this guide

Video in the Prebid adapter

RTB House's publisher integration guide tells the page to declare mediaTypes as banner, native, or video, then pass the publisher ID and region that RTB House assigns. Video on that list means a placement can request a video bid. It does not document which VAST version the bid markup will use, or whether the markup is inline XML or a wrapper URL.

When a video bid comes back, treat adm as the creative under test. If it is XML, paste it into the validator. If it is a URL, fetch it with the tester and validate the resolved response. Publisher players still apply their own media, HTTPS, and wrapper rules after RTB House has bought the impression.

CTV in the public record

RTB House's Audi San Francisco case describes a geo-targeted CTV and OTT campaign that ran 15 to 30 second streaming video ads, with QR codes in the creative. That is one campaign write-up, and it is evidence that RTB House traffics streaming video. It is not a creative specification for every RTB House video bid.

Duration, codec, and VPAID policy for a given impression still belong to the publisher and the player. If the buy is CTV, check the resolved tag against the player guide for that device, such as Roku or Fire TV, after the XML itself validates.

Pre-flight checklist

The placement requests video when the expected creative is VAST.
The returned adm is either valid VAST XML or a URL that resolves to it.
The resolved XML passes the validator.
Media and tracking URLs use HTTPS.
CTV buys are checked against the target player, not against the Audi case study durations.

What this guide does not assume

RTB House does not publish, in the sources used here, a required VAST version, a wrapper hop limit, a codec ladder, or a VPAID ban. Do not copy another platform's video spec onto an RTB House bid. Validate the creative that bid returned.