The Google Mobile Ads SDK now supports MRAID v2, enabling advertisers to serve MRAID v2 creatives to DoubleClick publishers. This guide clarifies the MRAID implementation details that were unclear and open to interpretation in the MRAID v2 spec, and its intended audience is MRAID v2 creative authors.
Publishers must be running:
- Google Play services 7.8 and higher
MRAID v2 implementation details
mraid.getVersion() does not return
2.0 until the creative has loaded. Do not
check the MRAID version while
mraid.resize() is called, the original banner is replaced with the
screenshot image of the banner. This will be noticeable if the resized ad
doesn't cover the original ad space.
Resized ads also do not follow the original banner frame. If a banner is placed in a scrolling view, the resized ad will not scroll with the banner.
mraid.resize() and other similar functions
won't have any effect until after the ad is clicked. This
prevents a malicious creative from automatically resizing and taking up the
All calls to
mraid.setResizeProperties() should contain a complete list of
required properties. If the resize properties are invalid, they will be set back
to their defaults, and all subsequent calls to
mraid.resize() will fail until
mraid.setResizeProperties() is called again with valid parameters.
mraid.getMaxSize() should only be used to determine the maximum size for resized
ads. To determine the size of an expandable ad, use
mraid.setOrientationProperties() with the
property set to
true, setting the
forceOrientation property won't do anything.
Creatives that want to force orientation should set
If a view covers an otherwise visible ad,
mraid.isViewable() will still return
true. App content should not cover visible ads.
While a two-piece expandable ad is in the expanded state, a call to
mraid.getCurrentPosition() on the first piece will return the size of the
mraid.storePicture()For an app to support
mraid.storePicture(), it needs to include the