Ad Format Unification FAQ
In September 2019, MoPub released features that increase flexibility in creative sizes, enabling more DSPs to bid on an impression. This release includes improvements to video orientation, support for the format array extension, and addition of creative ad sizes, providing you with the flexibility to access a wider variety of ad sizes on MoPub Marketplace.
The format array will support the following additional ad sizes and will be added in the
imp.banner.ext.format field of the bid request. Note: this change affects display formats only; native and rewarded video bid requests remain unchanged.
New sizes for Banners: 300x50, 468x60, 970x90, 970x250 (existing: 320x50, 728x90)
New sizes for Medium Rectangles: 336x280 (existing: 300x250)
New sizes for Fullscreen: 320x568, 300x600, 360x640, 300x1050, 568x320, 640x360 (existing: 320x480, 480x320, 768x1024, 1024x768)
Video Orientation FAQ
1: What do the video orientation changes mean for a DSP?
As of June 2019, VAST videos will automatically render in the same orientation as a user’s mobile device (i.e. portrait or landscape).
2: Can the DSP remove the MoPubForceOrientation VAST extension from their creatives?
The MoPubForceOrientation VAST extension has been deprecated. DSP’s can safely remove this extention from their VAST ad markup. Note - Android SDKs up to v5.7.1 will continue to respect MoPubForceOrientation Portrait and Landscape flags.
3: Does this mean that any bid response containing the MoPubForceOrientation VAST extension will become invalid and won’t serve the ad at all?
No. If a bid response contains the MoPub Force Orientation VAST extension, MoPub will just ignore it, and the bid won’t be invalidated. Note: Android SDKs up to v5.7.1 will continue to respect
MoPubForceOrientation Portrait and Landscape flags (if they exist).
4: Is it now required for DSP’s to provide both orientations for each creative?
DSP’s are not required to send both portrait and landscape media files. If a DSP can send both, that would be ideal for the best user experience since the MoPub SDK will pick the one that correlates with the orientation of the user. However, if only one orientation is sent, then it will be played in the orientation of the user.
5: Is this change dependent on a specific version of the MoPub SDK, or is it a server-side change?
This is not an SDK dependent feature, and all videos will play in the orientation of the device as of June 2019.
6: How can a DSP test what this looks like?
This new functionality can be tested through the Mopub Sample App.
7: If a DSP serves a landscape video while the user device is in portrait orientation, will the user see that video in the middle of vertical screen, with no need to re-orient device to landscape mode? And vice versa?
Yes. If a DSP sends a landscape video, and the user is in portrait orientation, the video will play in the middle with blackboxing above and below it. If a DSP sends a portrait video and the user is in landscape mode, then the video will play in the middle with blackboxing on the right and left sides.
8: What happens if user rotates the device during video playback?
The video will change orientation dynamically.
9: What is the recommended aspect ratio for videos?
All video aspect ratio sizes are supported, including 16:9, 4:3, 3:2, 16:10 and 1:1 (including the inverse ratios for vertical video, e.g. 9:16). Per the IAB Digital Video Ad Format Guidelines, 16:9 (landscape) or 9:16 (portrait) is the recommended aspect ratio.
Format Array FAQ
10: Why would a DSP want additional creative ad sizes?
Enabling additional creative sizes for ad formats positions MoPub to meet demand from DSP’s and advertisers to serve more creative sizes than we have in the past. Bid requests now contain all acceptable creative sizes for the ad unit, and DSP’s can respond with any one of the sizes listed, including the newly added sizes.
11: How can a DSP receive new ad sizes?
The format array will be added in the
imp.banner.ext.format field of the bid request. Note: this change affects display formats only; native and rewarded video bid requests remain unchanged. In the MoPub Demand Platform, you can now customize your segments with more of the ad sizes that matter to advertisers; you can also generate some bid request examples in the Testing tab of the MoPub Demand Platform.
12: Why is the format array added as an extension?
MoPub added at the format array as extension to respect the current OpenRTB 2.3 spec that MoPub is on.
13: What can a DSP respond back with?
As per the IAB spec, and the MoPub OpenRTB guidelines, our partners are expected to respond back with a creative height and width that is requested in the bid request (either in
imp.banner.w or in the
imp.banner.ext.format array). Height and width values must be in density-independent pixels.
14: Is there an example of what a bid request with the format array extension looks like?
Yes, see here.
Leaderboard (728x90) Impact FAQ’s
15: Why is 728x90 available now via the format array extension?
A leaderboard ad is essentially a larger version of a 320x50 banner. In an effort to consolidate ad sizes and reduce publisher setup complexity, banners in the MoPub Publisher UI are now size-agnostic (they were previously represented as 320x50 banners) and we now only send one size (320x50) in the banner object height x width fields if the publisher has consolidated their ad units.
16: Will DSP’s lose access to 728x90 inventory?
If you support the format array, there is no impact. As publishers consolidate ad units, DSP’s will start seeing 728x90 in the format array when that size is applicable. If you do not support the format array, as publishers consolidate ad units, the requests you previously saw as 728x90 will be sent as 320x50.
Last updated May 18, 2020
TWITTER, MOPUB, and the Bird logo are trademarks of Twitter, Inc. or its affiliates. All third party logos and trademarks included are the property of their respective owners.
© 2020 MoPub (a division of Twitter, Inc.)