A publisher notifies a brand that their video player environment is strictly non-VPAID compliant and will reject any tags containing JavaScript wrappers. To make sure the VAST XML remains clean and successfully delivers the video, what action must the brand take regarding Active View?
- Switch the placement compatibility to Display to allow the VPAID asset to serve as a standard out-stream banner.
- Increase the ad priority to 1 to make sure the VPAID wrapper is prioritized by the publisher’s player.
- Toggle the VPAID-only creative setting within the advertiser’s global properties to force a VAST fallback.
- Turn off the setting at the site or placement level to remove the VPAID-dependent measurement wrapper.
Explanation
Active View for in-stream video can add a VPAID measurement adapter to the VAST tag. A non-VPAID publisher player may reject the tag when that JavaScript wrapper is included. Setting the adapter to off at the site or placement level removes the VPAID wrapper from the exported tag. This preserves standard VAST video delivery while avoiding an unsupported measurement layer.
Why the other options are incorrect
Display compatibility changes the placement type and does not solve in-stream VPAID wrapper rejection.
VPAID-only creative setting does not force a clean VAST fallback for a non-VPAID player.
Ad priority affects serving order and cannot remove a VPAID measurement wrapper.
Source for verification
https://support.google.com/campaignmanager/answer/7173678?hl=en
https://support.google.com/campaignmanager/answer/3311603?hl=en