OpenWrap simplifies the process of creating video ads by letting you define your ads using parameters added to your ad tag instead of creating a large block of HTML code. The data-flow for video ads in OpenWrap is nearly identical to that of standard ads, but has the addition of a cache server:
The process of defining a video ad in OpenWrap is to generate an ad tag as you normally would in DFP, and then append video-specific parameters to the tag. Your result might be similar to this:
OpenWrap Video API
The sections below provide details about the parameters and usage notes for building OpenWrap video ad tags in DFP AdServer.
DFP vs. OpenWrap Query Parameters
You will find that the table below also contains oRTB Video parameters for use in the DFP parameter list. You can send OpenWrap parameters to override the DFP value. For example, if you include only
sz=300x250 in the DFP URL, that size populates the W and H parameters in the oRTB Video request. But if you also include
pwtsz=<some other size>, then OpenWrap uses the size value from
|oRTB Video Request parameter||DFP parameter||OpenWrap Parameter||Parameter Type||Notes|
|W and H would be provided in pwtvsz or sz in the format: WxH|
List of Integers; for example,
Possible Integer values for pwtmime and their corresponding meaning:
|sz||W and H would be provided in |
You can also send macros for DFP parameters as query parameters to the video endpoint. For example, sending pwtm_description_url=www.test.com would replace the description_url value in the DFP url, then use the same in constructing the oRTB Video object, and also update the DFP redirect URL with these values.
To send a macro for a given DFP parameter, use query parameter key, pwtm_<exact DFP parameter name>. For example,
When a request is made to OpenWrap Video endpoint, it responds with a 302 redirect to the DFP URL. But sometimes, you may want to debug a particular request. You may enable debugging for an OpenWrap video request which would return a JSON response containing debug information. However, an important point to note here is: when debugging is enabled, the usual flow of redirection to DFP URL would NOT work and creative would not be rendered.
To enable debugging, you may follow these steps:
1. Use macro to set pwtm_url query parameter in the Video endpoint dynamically.
2. Add logic to always set page URL in pwtm_url macro before making a call to Video endpoint. This way any query parameters added to the page URL would be set in pwtm_url value.
3. When you want to enable debugging, add query parameter pwtvc=1 in the page URL. This would be replaced in the pwtm_url macro with the above logic and Video endpoint would respond with debug response.
Sample Video endpoint call with pwtm_url macro along with macros for a few other DFP parameters like sz, vpos, vtype:
Here is a sample code snippet that replaces pwtm_url macro dynamically with the page URL.
OpenWrap for Video Ads does not currently support Companion Ads.