A specialist is distributing a VAST tag to a publisher who uses a legacy video player that doesn’t support JavaScript-based VPAID wrappers. The publisher reports that the tag is failing to initialize. To resolve this compatibility issue while maintaining the video delivery, what change must be made in the placement settings?
- Change the placement compatibility to display to force the video to serve as a standard banner.
- Increase the ad priority to 16 to make sure the server ignores the VPAID requirement.
- Enable companion banners to allow the legacy player to bypass the primary video asset.
- Disable Active View for the specific site or placement to remove the VPAID wrapper from the VAST tag.
Explanation
Active View measurement for in-stream video can add a VPAID measurement adapter into the VAST tag. A legacy publisher player that is not VPAID compliant may fail when that wrapper is present. Turning off the measurement adapter at the site or placement level removes the incompatible layer while keeping the video tag usable for standard in-stream delivery. The delivery issue is caused by player compatibility, not by creative priority or display tag behavior.
Why the other options are incorrect
Companion banners control secondary creative assets and do not bypass the primary video ad.
Ad priority affects serving order and does not remove a VPAID wrapper.
Display compatibility changes the placement format and does not preserve standard in-stream video delivery.
Source for verification
https://support.google.com/campaignmanager/answer/7173678?hl=en
https://support.google.com/campaignmanager/answer/3311603?hl=en