VMAP-1.0-error-tracking-macro
VMAP-1.0-error-tracking-macro
VMAP error tracking URI should include the `[ERROR_CODE]` macro
InfoVMAPIAB VMAP 1.0.1 §2.5VMAP 1.0 (all VMAP documents)
Short answer
VMAP error tracking URIs should include the [ERROR_CODE] macro so the player can substitute the actual error code when firing the beacon. Without it, error diagnostics carry no machine-readable code.
Why this matters in production
This rule is advisory rather than fatal, but it still matters for portability, debugging speed, and keeping tags predictable across different buyers and playback stacks. VMAP rules validate the ad break schedule envelope. Malformed break timing, wrong namespace declarations, or invalid AdSource content prevent players from resolving any of the ads in the playlist. Affected scope: VMAP 1.0 (all VMAP documents).
Check your VAST tag for
VMAP-1.0-error-tracking-macro and other issues instantly.Open the VAST tag validator →Other VMAP rules
VMAP-1.0-root-versionRoot `<VMAP>` element must have a version attributeVMAP-1.0-root-version-value`<VMAP>` version attribute should be `"1.0"` — the only published VMAP versionVMAP-1.0-root-namespace`<VMAP>` should declare the VMAP namespace URI http://www.iab.net/videosuite/vmapVMAP-1.0-root-unknown-child`<VMAP>` may only contain `<AdBreak>` and `<Extensions>` elementsVMAP-1.0-adbreak-timeoffset`<AdBreak>` must have a timeOffset attributeVMAP-1.0-adbreak-timeoffset-format`<AdBreak>` timeOffset must be hh:mm:ss[.mmm], n%, `"start"`, `"end"`, or #mVMAP-1.0-adbreak-breaktype`<AdBreak>` must have a breakType attributeVMAP-1.0-adbreak-breaktype-value`<AdBreak>` breakType must be a comma-separated list of `"linear"`, `"nonlinear"`, or `"display"`