AWS Elemental MediaTailor
User Guide

VPAID Handling

VPAID allows publishers to serve highly interactive video ads and to provide viewability metrics on their monetized streams. For information about VPAID, see the specification at

AWS Elemental MediaTailor supports a mix of server-side-stitched VAST MP4 linear ads and client-side-inserted VPAID interactive creatives in the same ad break and preserves the order in which they appear in the VAST response. AWS Elemental MediaTailor follows VPAID redirects through a maximum of three levels of wrappers. The client-side reporting response includes the unwrapped VPAID metadata.

Follow these guidelines to use VPAID:

  • Configure an MP4 slate for your VPAID creatives. AWS Elemental MediaTailor fills the VPAID ad slots with your configured slate, and provides VPAID ad metadata that is used on the client side to run the interactive ads. If you do not have a slate configured, when a VPAID ad appears, AWS Elemental MediaTailor logs an error in CloudWatch. It inserts MP4 ads normally no matter what. For more information, see Slate Management and Creating a Configuration.

  • Use client-side reporting. AWS Elemental MediaTailor supports VPAID through our client-side reporting API. For more information, see Client-side Reporting.

    It is theoretically possible to use the default server-side reporting mode with VPAID. However, if you use server-side reporting, you lose any information about the presence of the VPAID ad and the metadata surrounding it, because that is only available through the client-side API.

  • In live scenarios, make sure that your ad breaks, denoted by EXT-X-CUE-OUT: Duration, are large enough to accommodate any user interactivity on VPAID. For example, if the VAST XML specifies a VPAID ad that is 30 seconds long, implement your ad break to be more than 30 seconds, to accommodate the ad. If you don't do this, you lose the VPAID metadata, because the remaining duration in the ad break is not long enough to accommodate the VPAID ad.