DoubleVerify VAST validator guide
Short answer: DoubleVerify's Video OmniTag is itself a VAST wrapper on vast.doubleverify.com. It extends the advertiser's origin tag. Validate the wrapper URL and the inline it resolves to. A monitoring pixel on tps.doubleverify.com is a different tag and does not replace that wrapper.
Need a DoubleVerify VAST validator?
Paste the OmniTag URL. Inspect the extra hop, then validate the creative XML behind it.
Quick reference
| Role | Verification wrapper around an origin VAST tag |
| OmniTag host | vast.doubleverify.com |
| Monitoring host | tps.doubleverify.com |
| Origin macro | ${DC_VAST_URL} on the wrapped URL in Display & Video 360 |
| Wrapped URL length | 1,024 characters in Display & Video 360 |
The OmniTag extends the origin tag
Display & Video 360's verification help says a video creative has no display tag to wrap. You request a verification-wrapped VAST URL from DoubleVerify that includes the ${DC_VAST_URL} macro, and the platform replaces that macro with the origin VAST URL at serve time. The same page lists DoubleVerify and Integral Ad Science as the approved video verification providers, and it rejects a wrapper from an unapproved provider. Wrapped URLs longer than 1,024 characters error on save.
Google's bulk-wrapping example uses a vast.doubleverify.com/v3/vast URL whose _vast parameter holds ${DC_VAST_URL}. A DoubleVerify implementation note describes that Video OmniTag as a VAST tag which extends the client's origin tag, implemented the same way as any other third-party VAST tag, and which can measure viewability where the environment supports it. A tag whose URL contains tps.doubleverify.com is the monitoring pixel for a corresponding VAST implementation, not that OmniTag.
What the player has to support
FreeWheel Buyer Cloud's video viewability note offers a DoubleVerify wrapper add-on on both a VAST 2.0 inline template and a VAST 2.0 wrapper template. It describes web measurement on VPAID, and in-app measurement on apps that have OMID. A wrapper that is valid XML can still return no viewability if the player cannot run the measurement path DoubleVerify expected. Read the wrapper chain guide when the OmniTag adds a hop the publisher already counts against its depth limit.
Pre-flight checklist
- The trafficked URL is the vast.doubleverify.com OmniTag when viewability is required.
- The origin macro is still present, or already substituted with a fetchable VAST URL.
- The wrapped URL is within the buyer platform's length limit.
- The inspector shows the extra hop and an inline creative with a playable media file.
- The resolved XML passes the validator.