the supported IAB API frameworks for the given impression:

• 1 - VPAID 1.0
• 2 - VPAID 2.0
• 3 - MRAID-1
• 4 - ORMMA
• 5 - MRAID-2
• 6 - MRAID-3
• 7 - OMSDK

separate multiple values by a comma (e. g. iabframeworks=1,2,7)

• m - master request; indicates that the request should be counted as a page impression; use m only for the first request from a given page; all subsequent requests from the same page should use s
• s - slave request; indicates that the request should be counted as a regular ad impression; do not use s for the first request from a given page;
• parameter is optional; if absent, the default value is used: m (master) in case of Onecall or s (slave) in case of standard call

used in Generic POST requests only; requests a specific type of response; values can be either literal (e. g. js) or value (e. g. 1) :

• Javascript: js or 1
• Nonrich: nonrich or 2
• Iframe: iframe or 4
• XML: xml or 8
• JSON: json or 16
• VAST: vast or 32 (calls a VAST ad with version 4.0 or lower; read about calling specific VAST ad versions below)

Calling specific VAST ad versions:

• vast4.2 - calls a VAST ad with version 4.2 or lower
• vast4.1 - calls a VAST ad with version 4.1 or lower
• vast4 or vast or 32 - calls a VAST ad with version 4.0 or lower
• vast3 - calls a VAST ad with version 3.0 or lower
• vast2 - calls a VAST ad with version 2.0

the ad break; possible values:

• 0 - default
• 1 - preroll
• 2 - midroll
• 3 - postroll
• Not set for overlays

default value: 1

the ad rule id (VideoAdRuleId); logs the application of server side ad rules when Equativ returned the video ad; possible values:

• VideoAdRuleId=-1 means that a client side ad rule was applied; i. e. the video ad was served without any involvement of server side ad rules
• VideoAdRuleId=0 means that server side ad rules were applied but none of them was matching
• VideoAdRuleId=[Id] indicates that a server side ad rule was matching and was applied; [Id] represents the Id of the actual ad rule that was applied (as set up in Monetization)

determines which video ad rules should be applied;

• ssar=0 deactivates server side ad rules and activates client side ad rules
• ssar=1 activates server side ad rules and deactivates client side ad rules

a boolean indicating if noad is counted client-side or server-side; noad occurs when more ads are requested than available on the placement;  noad counting is done for reporting and forecasting purposes;

• s for server-side counting (default)
• c for client-side counting; used in case of Equativ's video plugin or Embedded Ad Manager; in case of client side counting using standalone VAST requests, noad should be counted as described in chapter “Counting empty inventory” in Supply in-stream video inventory: get started.

The server side counting method (vcn=s) means that Equativ counts empty (unmonetized) inventory server side. Empty inventory occurs when the number of ads returned by Equativ is less than the number of ads requested by the pod size (ps=) parameter or by the maximum ad break duration (mabd=) parameter in the VAST request. Empty inventory is counted with the report metric "No ad". Keep in mind: In case of client side counting, missing ads should be counted on the client side as described in “Counting empty inventory in case of standalone VAST requests” below.

the video client technology Id passed by Equativ's video plugin; possible values:

• 1 - Flash (deprecated)
• 2 - javascript

the video integration type passed by Equativ’s video plugin; possible values:

• 1 - Instream Plugins
• 2 - Instream Embedded Ad Manager
• 3 - Outstream synchronous formats (obsolete)
• 4 - Outstream asynchronous formats
• 5 - Server side ad insertion (SSAI)

the VPAID version;

• 0 - VPAID not supported (mandatory if VPAID is not supported at all)
• 1 - VPAID version 1
• 2 - VPAID version 2
• 1,2 - both VPAID versions in a single request

the video placement type in accordance with updated IAB Digital Video Guidelines; replaces vpt parameter; definitions below are shortened - for full definitions, see List: Plcmt Subtypes - Video 

• 1 - Instream; pre-roll, mid-roll and post-roll ads played before, during or after the streaming video content requested by user; must be sound-on by default at player start
• 2 -  Accompanying Content; pre-roll, mid-roll and post-roll ads played before, during, or after streaming video content; video player loads and plays before, between, or after paragraphs of text or graphical content and starts playing only when it enters the viewport.
• 3 - Interstitial; video ads played without video content; must be primary focus of the page and take up the majority of the viewport; cannot be scrolled out of view; can be placements like in-app video or slideshows.
• 4 - No Content/Standalone; video ads played without streaming video content; can be placements like slideshows, native feeds, in-content or sticky/floating

the video playback method; set to -1 by default (feature disabled):

• -1: Default value, disables the feature
• 1: Initiates on Page Load with Sound On
• 2: Initiates on Page Load with Sound Off by Default
• 3: Initiates on Click with Sound On
• 4: Initiates on Mouse-Over with Sound On
• 5: Initiates on Entering Viewport with Sound On
• 6: Initiates on Entering Viewport with Sound Off by Default

the video placement type; deprecated as of open RTB 2.6-202303 release; for the latest types of video placements in accordance with updated IAB Digital Video Guidelines, see vplcmt parameter above

• 1 - In-Stream; played before, during or after the streaming video content;
• 2 - In-Banner; exists within a web banner that leverages the banner space to deliver a video experience as opposed to another static or rich media format; the format relies on the existence of display ad inventory on the page for its delivery;
• 3 - In-Article; loads and plays dynamically between paragraphs of editorial content;
• 4 - In-Feed; in content, social or product feeds;
• 5 - Interstitial / Slider / Floating; covers the entire or a portion of the screen area, but is always on screen while displayed (i.e. cannot be scrolled out of view).

the agent type the ID is coming from:

• 1 - Web; an ID which is tied to a specific browser or device; cookie-based, probabilistic,or other;
• 2 - IDFA
• 3 - AAID
• 4 - Windows Mobile Advertising ID
• 5 - Other Mobile ID

the indication of whether transparency data are to be sent. Independent of the pubrender parameter, the publisher may need the transparency data for audit purposes.

• 0 - do not send transparency data
• 1 - optional to send transparency data
• 2 - send transparency data

a flag to indicate if DSA information should be made available. This will signal if the bid request belongs to an Online Platform/VLOP, such that a buyer should respond with DSA Transparency information based on the pubrender value.

• 0 - Not required
• 1 - Supported, bid responses with or without DSA object will be accepted
• 2 - Required, bid responses without DSA object will not be accepted
• 3 - Required, bid responses without DSA object will not be accepted, Publisher is an Online Platform

a flag to indicate if the publisher will render the DSA Transparency info. This will signal if the publisher is able to and intends to render an icon or other appropriate user-facing symbol and display the DSA transparency info to the end user.

• 0 - Publisher can't render
• 1 - Publisher could render depending on adrender
• 2 - Publisher will render