Audio impressions are the only billable events, so if a companion banner cannot be displayed by your site/app, it can simply be ignored. The audio plays, and the impression is tracked on the audio asset. However, we strongly suggest you configure your site/app to enable as many banner sizes as possible, paying particular attention to the most common ones. This will help ensure a better user experience and engagement from your listeners (including click-throughs) and better value for your inventory on the programmatic marketplace.
Players are responsible for selecting the appropriate companion banners for display based on, for example, the reserved areas and their sizes (i.e., a Web page containing placeholders for IAB Leaderboards and Big Boxes, or a mobile player with space for a phone-sized banner).
The player must iterate over the companion banners, selecting banners by size (i.e., width/height). It should select the banners for the sizes it is able to display, and ignore banners it is incapable of displaying. Once banners are selected by size, the player should then select the most appropriate resource type (static/HTML/IFrame) for rendering (depending on the player's platform and capabilities).
The player should avoid scaling the banner up or down, as this usually leads to bad image quality. In the event that the player must scale the image, the scaling must be applied such that it maintains the image’s original aspect ratio.
Companion banners can be offered in three renderings: IFrame, HTML, or Static Resource. Depending on the player's implementation and runtime platform, one of these renderings should be the most appropriate for display.
The player should call the various tracking URLs for displayed banners. It MUST NOT, however, call the tracking URLs for companion banners that are not displayed. The player MUST ONLY call the tracking URLs for the rendering format used (e.g., the Static Resource's tracking URLs should not be called if the player uses the IFrame rendering), as every rendering already provides the elements necessary to perform its own tracking (e.g., transparent pixels embedded in IFrame/HTML renderings). Players should follow HTTP redirections when calling tracking URLs.
If an error occurs while retrieving a companion banner's rendering or resources (e.g., for URL-based resources, such as IFrame or Static Resource), and the player is thus unable to display the companion banner, the tracking URLs MUST NOT be called (as the banner was never actually displayed to the listener).