VASTlint
VAST-4.4-adcom-signal-not-integer

VAST-4.4-adcom-signal-not-integer

AdCOM signal payload in <Extension> is not an integer

ErrorCTV Ad PortfolioIAB AdCOM 1.0 enumerated listsAll VAST versions

Short answer

Every AdCOM enumeration is numeric. A payload like <playbackmethod>two</playbackmethod> cannot be parsed by any consumer regardless of which VAST version the tag declares, so this is an error rather than an advisory.

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.

Invalid

<Extension type="playbackmethod" ext="adcom">
  <playbackmethod>two</playbackmethod>
</Extension>

Valid

<Extension type="playbackmethod" ext="adcom">
  <playbackmethod>2</playbackmethod>
</Extension>
Check your VAST tag for VAST-4.4-adcom-signal-not-integer and other issues instantly.Open the VAST tag validator →