Create or edit a master video tag manually

Output format of ad. Use output=vast for the VAST version (for example, VAST 4) you have enabled for your network. For specific ad tags or parts of your site, you can explicitly ask for VAST 3 with output=xml_vast3 or VMAP 1 with output=xml_vmap1.

Use output=vmap to return the default VMAP version (e.g., VMAP 1) you have enabled for your network.

Note: If your video player uses the IMA SDK, the output parameter for a video ad request will always be set to output=xml_vast4. This poses no reliability risk as the SDK is backwards compatible with all VAST versions that any third-party ad server may serve.

vast (for your network's default VAST setting)
xml_vast3 (for VAST 3)

vmap (for you network's default VMAP setting)
output=xml_vmap1 (for VMAP1)

/network_id/.../ad_unit

Size of master video ad slot. Multiple sizes should be separated by the pipe (|) character.

Do not include "v" after the size.

description_url

The value should describe the video playing on the page. Usually, it's the page that houses the video player, but could also be a page with text that describes the video.*

You must always url-encode description_url on web page video players.

You should send non-encoded description_url values from mobile in-app video players.

This field is required if you use Ad Exchange. Learn more

URL-encoded example:
https%3A%2F%2Fwww.sample.com%2Fgolf.html

Non-encoded example:
https://www.sample.com/golf.html

This is the full URL from which the ad request is being sent. On a web page, this is the URL of the page that displays the video player. In an app, this is the package name.

If you use the IMA SDK, it sets the URL value automatically. If your player sets this value, the IMA SDK overwrites it and set its own value.*

A random positive numerical value that is shared by multiple requests coming from the same page view.

The correlator is used to implement competitive exclusions, including those in cookieless environments.

If the IMA SDK is used, the correlator value is set automatically. If your player attempts to set this value, the IMA SDK overwrites it with its own random value.

If the IMA SDK is not used, ensure that you set this value to a truly random value that is not being reused by multiple page views.

Indicates whether to return a VAST creative or an ad rules response. If you are using ad rules, then ad_rule=1 should be used. Other requests should use ad_rule=0 (or simply exclude the parameter).

Learn more about ad rules.

Comma-separated list of companion sizes.

Pipe-separated (|) values indicate a multi-size ad slot.

Companion sizes:
728x90,300x250

Companion sizes with a multi-size slot:
728x90,300x200|300x250

cmsid
vid

In order to target ads to video content, your master video tag needs to include both cmsid and vid.  

The cmsid is a unique number for each content source. To locate this in Ad Manager, click Video  Content sources and then the name of the content source.

The vid is a string or number identifying a particular piece of video content. This ID is assigned by the CMS that hosts your content. To locate this in Ad Manager, click Video  Content and then the specific content from the list.

cmsid=[value]&vid=[value]

If you are building a tag for Dynamic Ad Insertion with video on demand, you should use the macros that will dynamically insert the correct cmsid and vid: &cmsid=%%CMS_ID%%&vid=%%VIDEO_ID%%

The language code used to request ads in that language.

This parameter is used for language of ad selection and video ad rendering in dynamic allocation to video in Ad Exchange or AdSense Video.

The language can be any ISO 639-1 (two-letter) or ISO 639-2 (three-letter) code. See a list of valid codes.

If omitted, it defaults to any language with ad targeting by language in Ad Exchange.

These two parameters should be applied to all requests sent from mobile app and connected TV devices. The msid parameter is the app ID and should be used in direct VAST calls to Google where the IMA SDK is not used. The an parameter is the app name.

Most programmatic video ads require the presence of both of these values on requests from mobile app or connected TV inventory.

Indicates whether your ad request should not return a playlist of "video fallback" ads.

Learn more about video fallback.

Control which creatives are eligible to serve based on the configuration set up in a video creative profile.

Learn more about video creative profiles.

With native applications (not on web or mobile web), the SDK passes resettable device identifiers for user targeting into your stream requests with the parameters for rdid, idtype, and is_lat. On SSB streams, you must pass these as explicit parameters, just as you would on a client-side Video Solutions ad request. Learn more

Nearly all programmatic video ads require the presence of these values.

Tags an ad request to
restrict data processing.

You must either specifically set rdp=1 or include simply rdp (without a set value) to restrict data processing. Ad requests either missing this parameter, or set to rdp=0, will not restrict, unless the Restrict Data Processing network setting is enabled.

Tags an ad request for child-directed treatment. 

Learn more about tfcd.

Tags an ad request as
non-personalized.

You must either specifically set npa=1 or include simply npa (without a set value) to tag the request as non-personalized. Ad requests either missing this parameter, or set to npa=0, default to personalized ads.

Learn more about ad personalization.

Indicates whether the player intends to continuously play the content videos one after another, similar to a TV broadcast.

Possible values are 2 if continuous play is ON, and 1 if OFF.

This parameter should be left unset if it is unknown.

Continuous play OFF:
vconp=1

Indicates whether the ad starts through autoplay or click.

Possible values are click if the page waits for a user action or auto if the video plays automatically.

This parameter should be left unset if it is unknown.

Click:
vpa=click

Indicates whether the ad playback starts while the video player is muted.

Possible values are 1 for muted, and 0 for unmuted.

This parameter should be left unset if it is unknown.

Unmuted:
vpmute=0

Comma-separated list of non-linear ad sizes that can be displayed in the video ad slot.

These sizes must be any of the those supported:

• 200x200
• 250x250
• 300x250
• 336x280
• 450x50
• 468x60
• 480x90
• 729x90

Note: When using the IMA SDK, this field will be overwritten, populated with all supported sizes that fall within the nonLinearAdSlotWidth and nonLinearAdSlotHeight.

All sizes are supported:
200x200,250x250,
300x250,336x280,
450x50,468x60,
480x90,728x90

Max width is e.g. 250:
200x200,250x250

Max height is e.g. 80:
450x50,468x60

Max width is e.g. 100:
//empty; no values supported

No, parameter can be left out or empty when no non-linear sizes are supported.

Represents position within a pod. Necessary for companion autofill. Pass &ppos=1 for the first position, &ppos=2 for the second position, and so on. Used for competitive exclusions, frequency capping, and related features.

This parameter is for standard pods only.

Needs to be added for a request from the last position in a pod.

This parameter is for standard pods only.