Video RTB+ parameters

Goals

With video RTB+ parameters, you can enrich video bid requests in order to serve appropriate video ads. For instance, you can tell DSPs to return video ads with a specific minimum and a specific maximum duration.

This serves two goals:

  • boosting monetization: DSPs who receive bid requests with exact parameters will be willing to buy more at higher prices
  • eliminating technical issues: DSPs receive exact information about your technical video environment and will serve video ads which match your technical needs

Parameter processing

You can set parameters on two levels:

  • In the Video Ad Call
  • In the [RTB+ VIDEO] VAST 3.0 / [RTB+ VIDEO] VAST 2.0 script templates

Your parameters will be included in bid requests (sent to DSPs).

Rules:

  • Parameters defined in the Video Ad Call always override (i. e. have priority over) parameters in the [RTB+ VIDEO] VAST 3.0 / [RTB+ VIDEO] VAST 2.0 script templates
  • If a parameter is missing in both Video ad Call and [RTB+ VIDEO] VAST 3.0 / [RTB+ VIDEO] VAST 2.0 script templates, a default value will be used in bid request

Smart AdServer's Video RTB+ bid requests follow the Open RTB Specification (see page 13: "3.2.4. Object: Video").

Parameters in Video Ad Call

You can generate Video Ad Calls in Smart AdServer's User interface as described here.

Example of a Video Ad Call:

http://diff.smartadserver.com/ac?siteid=20697&pgid=415762&fmtid=27153&ab=1&tgt=&oc=1&out=vast4&ps=1&pb=0&visit=S&vcn=s&tmstp=[timestamp]

Add parameters anywhere after the question mark ("?"). Separate parameters by an ampersand ("&")

Example of a Video Ad Call with parameters (&vpaid=flash&vpaidv=2)

http://diff.smartadserver.com/ac?siteid=20697&pgid=415762&fmtid=27153&ab=1&tgt=&oc=1&out=vast4&ps=1&pb=0&visit=S&vcn=s&tmstp=[timestamp]&vpaid=flash&vpaidv=2

 

Parameters defined in the Video Ad Call always override parameters in the RTB+ Video script template.

Parameters in script templates

The script templates [RTB+ VIDEO] VAST 3.0 / [RTB+ VIDEO] VAST 2.0 provide the parameters shown in the screenshot above. For more details, see table below (column "Name in script template").

Parameters defined in the Video Ad Call always override parameters in the Video RTB+ script template.

Parameters in apps

For RTB+ standalone in apps (Android, iOS) , the parameters buid, appname, uid. are available. For more details see the end of the table below (List of Parameters).

List of parameters

The following table includes:

  • The parameter's Name in Video Ad Call
  • The Parameter value(s) in the Video Ad Call
  • A Description
  • The Default value used in bid requests in case the parameter is missing in both Video Ad Call and script template
  • The parameter's Name in Script templates ([RTB+ VIDEO] VAST 3.0 / [RTB+ VIDEO] VAST 2.0 script templates)

 

Name in
Video Ad Call
Parameter
value(s)
 Description
Default
value
Name in
script template
out vast2
vast3
vast4
out=vast2 => requests a VAST ad with version 2.0
out=vast3 =>  requests a VAST ad with version 3.0 or lower
out=vast4 => requests a VAST ad with version 4.0 or lower
is mandatory, no default value
is mandatory, no field in script template
vaf
0
1
Specifies if flash video ads are accepted
vaf=0 => no flash video ads accepted
vaf=1 => flash video ads accepted
1 Accept FLV videos
vpaidt
flash
js
Specifies the VPAID type; to pass both values in a single call, separate them by a comma: &vpaidt=flash,js
flash
js
VPAID creative types
vpaidv
0
1
2
Specifies the VPAID version;
to pass both values in a single call, separate them by a comma: &vpaidv=1,2

Important note: If VPAID is not supported at all, you must pass vpaidv=0; else, the default values (VPAID versions 1 and 2) would be used
1
2
VPAID version

Important note: If VPAID is not supported at all, you must select version 0; else, the default values (VPAID versions 1 and 2) would be used
vdmin
integer
Specifies the video ad's minimum duration in seconds
1 Minimum duration
vdmax
integer
Specifies the video ad's maximum duration in seconds
60
Maximum duration
ab 1
2
3
Specifies the Ad Break
ab=1 => preroll
ab=2 => midroll
ab=3 => postroll
1 Type of ad break
vbrmin
integer
Specifies the minimum bit rate in Kbps
no default value
Minimum bitrate
vbrmax
integer
Specifies the maximum bit rate in Kbps
no default value
Maximum bitrate
vpmt
1
2
3
4
Specifies the Playback method
vpmt=1 => auto-play, sound on
vpmt=2 => auto-play, sound off
vpmt=3 => click-to-play
vpmt=4 => play on mouse-over
no default value
Playback method
vph
integer
Specifies the player height in pixels
height of format will be used (as defined in UI)
n/a
vpw
integer
Specifies the player width in pixels
width of format will be used (as defined in UI)
n/a
pgdomain
url-encoded string
Specifies the page domain, where the video ad call is integrated
no default value
n/a
n/a
n/a Custom impressions (multiple URLs separated by "||")
n/a Custom impressions
n/a
n/a
Custom tracking URL fired when a click occurs on the main creative (linear) (multiple URLs separated by "||") n/a Custom click-tracking for main creative (linear)
n/a
n/a
If enabled, uses the skip policy defined in publisher's settings
true Use publisher's skipoffset
n/a
n/a
If enabled, overrides the skipoffset of the wrapped VAST document through the next field
false Set skipoffset
n/a
n/a
If the previous checkbox is enabled, this value overrides the skip offset that is defined (or not) in the wrapped VAST document.
Available formats: "HH:MM:SS" / "HH:MM:SS.mmm" / "n%".
Then, underlying linear ads will not be skippable if this field remains empty
n/a Skipoffset
n/a
n/a
Changes the ad order
any Rank in ad pod
n/a
n/a
Optional Error URL n/a Error URL
n/a
n/a
Enables all the custom VAST Tracking URLs
false Use custom VAST metrics
n/a
n/a
Custom reporting URL for each VAST metric (multiple URLs separated by "||")
n/a Custom VAST Tracking for [name of VAST quartile or event]
buid  string Bundle ID; mandatory in case of in-app RTB+ standalone n/a n/a
appname string App Name; mandatory in case of in-app RTB+ standalone
n/a n/a
uid string IDFA or Advertising ID; mandatory in case of in-app RTB+ standalone n/a n/a
Was this article helpful?
2 out of 2 found this helpful
Powered by Zendesk