Search
Clear search
Close search
Google apps
Main menu
true

Render an end cap for a mobile video ad

You can implement an optional mobile video "end cap" to render a static, clickable creative which appears on completion of your video ad. Mobile video creatives using an end cap are accepted on all mobile app interstitial video inventory.

Determine whether a bid request supports end caps via the EndCapSupport parameter under the video message:

enum EndCapSupport {
   END_CAP_NOT_ENABLED = 0; // Companion ad won't be rendered as end cap.
   END_CAP_OPTIONAL = 1; // Eligible companion banner may be rendered as end cap.    
}
optional EndCapSupport end_cap_support = 13 [default = END_CAP_NOT_ENABLED];
 

More information on mobile video inventory

All details, specifications, and certification requirements for mobile video inventory, including in-app and mobile web, apply to creatives using an end cap. At this time, only mobile app interstitial video supports end caps.

Learn more about mobile video inventory.

Implement an end cap on a mobile video creative

The VAST template provides an option to include one or multiple companion banners using the <Companion> node in the XML. Implementation of an end cap requires only that you traffic the companion asset with your video ad.

See a sample VAST response

<CompanionAds>
   <Companion width="1024" height="768">
      <StaticResource creativeType="image/jpeg">
         <![CDATA[ https://...your-1024x768-image.jpeg ]]>
      </StaticResource>
   <TrackingEvents>
      <Tracking event="creativeView">
         <![CDATA[ https://...your-tracking-url.com ]]>
      </Tracking>
   </TrackingEvents>
      <CompanionClickThrough>
         <![CDATA[ https://...your-clickthrough-url.com ]]>
      </CompanionClickThrough>
   </Companion>
   <Companion width="300" height="250">
      <StaticResource creativeType="image/jpeg">
         <![CDATA[ http://...your-300x250-image.jpeg ]]>
      </StaticResource>
   <TrackingEvents>
      <Tracking event="creativeView">
         <![CDATA[ https://...your-tracking-url.com ]]>
      </Tracking>
   </TrackingEvents>
      <CompanionClickThrough>
         <![CDATA[ https://...your-clickthrough-url.com ]]>
      </CompanionClickThrough>
   </Companion>
</CompanionAds>


Note that only the following resource types are allowed for the <Companion></Companion> node:

  • StaticResource: URI to a static file
  • IFrameResource: URI source for an iframe to display the companion element
  • HTMLResource

The end cap is a static creative, so only image resource types (static GIF, JPG, PNG) or HTML/iframes trigger the end cap functionality. As Flash is not available on mobile, video ads with companions using Flash (SWF) creatives use the default behavior for mobile video ads; no end cap is shown.

Bidders can choose to return one or more companions in all of their video bid responses; in the event that end caps are not supported, the video will still be shown, and the companion banner will simply be ignored.

Since mobile app interstitial video inventory on Ad Exchange accepts creatives using an end cap by default, you are not required to make any changes to your pretargeting configurations. Inventory forecasting is also unaffected.

End cap rendering and functionality

Clickthrough and impression tracking

Your end cap creative clicks through to the clickthrough URL defined in your VAST response. You can set a custom clickthrough URL for your companion creative using the CompanionClickThrough field of the companion node. You can also set a custom impression tracker for the companion using the <Tracking event="creativeView"> node.

While the size requirements for companion banners are the same as other interstitial display ads on Ad Exchange (must be at least 50% of screen width and 40% of screen height), the clickable area of the creative is limited to all but the outermost 40 pixels on phones, and all but the outermost 100 pixels on tablets, to prevent accidental clicks.

Creative rendering

End caps are centered in the viewable area of the video ad slot. If more than one eligible companion banner exists in your VAST response, the companion of the largest area that is smaller than the screen size will render. As a best practice, you may want to include multiple companion banners in your bid response to account for different possible screen sizes. Users retain the option to "skip" and exit the end cap without clicking through.

If the user skips the video ad during video play, Ad Exchange will not render an end cap.

 

Learn more about the requirements to serve video ad units (VAST).

Was this article helpful?
How can we improve it?