VASTlint
Validate
VAST-4.4-qrcode-position-attrs

VAST-4.4-qrcode-position-attrs

<QrCodePosition> requires both xPosition and yPosition

ErrorCTV Ad PortfolioIAB vast_4.4.xsd vastQrCodePosition_typeAll VAST versions

Short answer

<QrCodePosition> carries no text content; its two required attributes are the whole element. Omitting either leaves the platform without a coordinate to place the code.

Why this matters in production

This rule is usually a delivery blocker. Many players, SDKs, and ad servers will discard the response or skip the affected creative once this condition is hit. 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.

Check your VAST tag for VAST-4.4-qrcode-position-attrs and other issues instantly.Open the VAST tag validator →

Other CTV Ad Portfolio rules

VAST-4.4-version-attributeDocument declares VAST 4.4, a working-group draft rather than a published specVAST-4.4-nonlinear-no-renderable-asset<NonLinear> has a SIMID interactive file but no renderable fallback assetVAST-4.4-nonlinear-mediafiles-empty<NonLinear> <MediaFiles> contains no renderable or interactive assetVAST-4.4-nonlinear-simid-iframe<IFrameResource apiFramework="SIMID"> is superseded by <InteractiveCreativeFile> in NonLinearVAST-4.4-nonlinear-video-no-duration<NonLinear> delivers video but has no <Duration>: quartile tracking cannot fireVAST-4.4-adcom-extension-unknown-signal<Extension ext="adcom"> type is not plcmt, pos, playbackmethod or attrVAST-4.4-adcom-extension-type-mismatch<Extension> type attribute and AdCOM payload element name disagreeVAST-4.4-adcom-signal-not-integerAdCOM signal payload in <Extension> is not an integer