VAST-4.4-qrcode-missing-scan-url
QR code geometry declared without a <QrCodeScanUrl> destination
Short answer
The <CreativeExtension> says where to draw the QR code and how big to make it, but never says where scanning it should lead. Either add <QrCodeScanUrl> or drop the geometry and let the creative's own baked-in QR image speak for itself.
Why this matters in production
This rule is a strong risk signal. Tags with this issue often still parse, but they become brittle across SDKs, SSAI resolvers, and CTV environments. The CTV Ad Portfolio standardises Pause, Screensaver, Overlay, Squeezeback and In-Scene ads, which ran for years on bespoke per-publisher integrations. These rules cover the VAST side of that contract: the NonLinear MediaFiles delivery model, the AdCOM signals round-tripped into Extensions so stitchers can validate the experience without the bid object, and the QR code block. The signaling guidance is final; the VAST 4.4 schema that accompanies it is still a working-group draft, so anything sourced only from the schema is reported as a warning or a note. Affected scope: All VAST versions.
Valid
<CreativeExtension type="tl_qrcode">
<QrCodeScanUrl><![CDATA[https://brand.example.com/qr]]></QrCodeScanUrl>
<QrCodePosition xPosition="10%" yPosition="70%"/>
<QrCodeSize size="15%"/>
</CreativeExtension>VAST-4.4-qrcode-missing-scan-url and other issues instantly.Open the VAST tag validator →