Amazon Ad Server will be sunset in Q4 2024, please visit this page (AAS offboarding information) for offboarding support resources and sunset FAQs. Details shared on that page represent the most up to date information in the Help Center, if you find disparate information in other resources please default to the information in the AAS offboarding information page accordingly.

Please note that on October 1, 2024, the ability to create new campaigns, placements, and tag managers will be disabled.



Amazon Ad Server (AAS) supports the following file types for video assets:

  • MP4 (H.264): This is the most universally-supported video file format across browsers, and the recommended format.

  • MOV

  • WebM

  • HLS Packages

  • OGV (OGG video)

  • OGG (OGG audio)


Note: You should treat .oga files as .ogg files.

Setting up a single ad

Setting up your ad requires that you start by uploading your video file to the assets library. Then, set up your ad based on the video file that you uploaded.

Upload your ad

  1. Select Creative > Assets Library.

  2. Click New Folder to create a folder into which you will upload your video file.

  3. Click Upload.

  4. Perform one of the following actions:

    • Drag your video file in the new window.

    • Click Browse Files to locate the video file.

  5. Click Done.

Set up your ad

  1. Select Creative > Ads.

  2. Click New Ad > Blank Ad.

  3. Give your ad a meaningful name.

  4. In the Ad Format list, selectIn-Stream Video.

  5. In the Creative Assets > Linear tab:

    1. Click Add.

    2. Select the folder and navigate to an uploaded video file.

    3. Under Settings, confirm that the linear duration matches the specifications you received from the publisher.

  6. Click Save.

Setting up multiple ads

You can upload and set up multiple ads in a single process using the Ad Creation Wizard. For more information, see Set up multiple ads using Ad Creation Wizard.

Previewing and testing

After you finish creating your ad, make sure that you preview and test it. For more information, see Preview Your Ads and Test your ads.


Note: Not all file formats are supported on all browsers and devices. You should always build In-Stream ads with the specs required by the publisher, but in some cases some of the assets may not be previewed properly in your browser.

Adding variants

If your publisher requires multiple videos for a single VAST ad (multiple dimensions (for example,720p and 1080p) or multiple file formats (for example .mp4 and .webm), click Add Variant and navigate to other video files.


Note: When using variants, make sure the content of your video is the same across files. They should also share the same duration. If you have different contents and/or durations, you should build multiple VAST ads, and not a single one with multiple videos.


Note: When variants are added, the original file is ignored and will need to be added again as a variant if it is needed.

Adding a companion

The companion element is an optional asset that appears alongside the video player on the same page, such as a .jpg image. The ad typically starts with the linear element (in case of multiple linear elements, then with the one that starts first) and can either remain on the page throughout the entire video play, change at some point with another creative, or disappear.

There are two types of companions:

  • Static Resource Companion: This companion is also known as a Static Resource Type. For example, a single asset, like an image (.jpg, .png, or .gif).

  • Advanced Companion: This companion will be selected from available display ads that are assigned to the same campaign and have the status published. This selection can be made from the In-Stream ad's settings at the placement ad level.

Settings tab

Change duration

You can voluntarily chose to adjust the linear duration. This will override the duration of your file, and the VAST will stop at the duration you manually defined in this field.

Linear click-through

You can add a URL in this field to test your ad.

Activate auto transcoding

AAS includes a video engine that will automatically transcode your video files at the placement level according to publisher’s specifications. You should select this option if you plan to use auto-trancsoding.

If you want to make sure that your publisher specifications are on file in AAS, check with your creative contact at Amazon Ad Server.

We recommend these specifications when working with auto-transcode:

  • File type: MP4

  • Video codec: H.264

  • Audio codec: AAC

  • Dimensions: 1920x1080

  • Ratio: 16:9

  • Bitrate: 15 Mpbs+

For more information, see Work with Video Auto-Transcoding .

Activate viewability and verification

Select this option to automatically convert the ad to VPAID. Before activating this option, confirm with your publisher that the video player supports VPAID.

For more information, see About Verification.


Note: Activating viewability and verification will automatically disable the Add Skip Button function. AAS will still allow you to activate it but it will not be executed.

Scale options

You should select Scale video to the video player size to make your VAST ad scalable according to the size of the video player on the publisher’s page. It is selected by default.

The Maintain aspect ratio option is also selected by default; this option confirms that the video is scaled homothetically. This option is only available if the Scale option is also selected.

Delivery type

This option determines how the video is delivered:

  • Progressive: Buffers the video content prior to playing the ad. This is the default and recommended option.

  • Streaming: Plays the ad in real-time using the streaming technology.


Note: When the delivery type is Streaming, the RTMP protocol is used to serve the media file. You should confirm that the publisher's player supports streaming media through this protocol. In addition, external restrictions such as corporate firewalls and network restrictions may prevent media from playing.

Add a skip button (VAST 3 and later)

If the specifications from the publisher require that a skip button appears sometime in the video, select Skip ad unit after, and define a duration after which the button will display. This is limited to video players that supports VAST 3.0 and up.


Note: Activating Viewability and Verification will automatically disable the Add Skip Button function. AAS will still allow you to activate it but it will not be executed.

Settings for VAST 4 and later

Adding a universal ad ID and ID registry applies VAST 4.1 tags to all VAST, VPAID, and enhanced (VAST or VPAID) ad formats.

  • Universal Ad ID: Allows you to use a unique string to identify your ad (for example, CNPA0484000H). This ID is based on the content, and can apply to multiple ads or placements. Default value if the field is left empty: Unknown.


    Note: The advertiser/agency usually provides the Universal Ad ID and the ID Registry if needed.

  • ID Registry: A string that identifies the ID registry’s website where the ID is cataloged (for example, Default value if the field is left empty: Unknown.


Note: It is recommended to create duplicate master ads if there is a need to serve across placements requiring different VAST versions.


All values to be provided by the third-party vendor whose tag is being used, and follows IAB spec for VAST 4 VAST verification.

If not using a third-party verification tag, all fields can be left blank. To use a third-party verification tag, you must provide the vendor, as well as either the JS resource/browser, optional/API framework, or the executable resource/type/API framework. You may also fill out the fields for both. Verification not executed and verification parameters are optional.




Vendor's identifier, which is typically in the form of a domain and the framework used, such as

JS Resource

URL for the JS script if using a JS resource.

Browser optional

  • Selected: Script can run in non-browser environments.

  • Cleared: Only for in-browser use.

API framework for Executable resource

Framework the tag uses, such as omid.

Executable resource

URL or package/path of the executable if using an executable resource.


Type of executable provided. This will be specified by the vendor.

API framework for Script resource

Framework that the tag uses, such as omid.

Verification Not Executed tracker

Optional tracker that can be added so that players can fire the tracker for situations in which the verification script cannot be loaded.

Verification Parameters

Metadata string that the 3rd party vendor may provide that needs to be included with the tag. Formatting and content may vary by vendor.

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request