Banner & MREC ads
© 2025 AppLovin. All rights reserved.
The default maximum height for an inline adaptive ad is the entire height of the device screen.
You may want to set a maximum height, in dp, for your inline adaptive ad to ensure that the ad fits in the height of the MaxAdView.
You can do this with code like the following, which uses a maximum height of 100 dp as an example:
Inline adaptive MRECs span the full width of the application window by default, but you may optionally specify a custom width in dp. The height is variable and can extend beyond standard MREC dimensions up to the full height of the device screen if you do not specify a maximum height.
Configure an inline adaptive MREC with the adaptive type set to MaxAdViewConfiguration.AdaptiveType.INLINE as shown in the following example:
The adaptive ad you load could be smaller than the dimensions you requested. You may wish to configure your UI in a way that can adapt based on the size of the adaptive ad served. If so, you can retrieve the width and height of the loaded ad, in dp, with code like the following:
You may want to stop auto-refresh for an ad. This may be the case when you hide an ad or when you want to manually refresh. Stop auto-refresh with the following code:
Start auto-refresh for an ad with the following code:
Manually refresh the ad contents by calling loadAd().
You can do this only if you first stop auto-refresh.
Banner and MREC ads are rectangular ad formats that occupy part of an app’s layout—often at the top or bottom of the screen or inline in scrollable content. They remain visible as users interact with the app, which allows uninterrupted gameplay or use, and can refresh automatically after a set period.
The following sections show you how to load, show, and hide a banner or MREC ad.
To load a banner or MREC, create a MaxAdView object that corresponds to your ad unit.
Then call that object’s loadAd() method.
To show that ad, add the MaxAdView object as a subview of your view hierarchy.
Implement MaxAdViewAdListener so that you are notified when your ad is ready (you will also be notified of other ad-related events).
If your integration requires displaying MREC ads in a content feed, AppLovin recommends the following:
loadAd() (re-use the MaxAdView instances).You can find an example implementation in the AppLovin demo app (Java, Kotlin).
You can also add MAX banners or MRECs to your view layout XML.
Ensure that your ads are fully functional by setting a background or background color (android:background).
For banners, stretch the width (android:layout_width) to the width of the screen.
For MRECs, set android:adFormat accordingly:
Declare the base banner height of 50 dp in res/values/attrs.xml:
Declare the tablet banner height of 90 dp in res/values-sw600dp/attrs.xml:
You still must call loadAd() on the MaxAdView you create in this way:
If you no longer need a MaxAdView instance, call its destroy() method to free resources.
This may be the case, for example, if the user purchases ad removal.
Do not call the destroy() method if you use multiple instances with the same Ad Unit ID.
Adaptive banners are responsive ads that dynamically adjust their dimensions based on device type and available width. Adaptive banners can be either anchored or inline, with each type serving specific integration needs.
Starting in MAX SDK version 13.2.0, you can integrate adaptive banners by initializing your MaxAdView with a MaxAdViewConfiguration object for which you set an adaptive type at build-time.
The following adapters support special adaptive banner features:
| Network | Adapter Versions | Special Feature |
|---|---|---|
| Google Ad Manager | 23.2.0.1+ | Inline adaptive banners |
| 23.6.0.3+ | Inline adaptive MRECs | |
| 21.5.0.2+ | Setting a custom width | |
| Google Bidding and Google AdMob | 23.2.0.1+ | Inline adaptive banners |
| 23.6.0.3+ | Inline adaptive MRECs | |
| 21.5.0.3+ | Setting a custom width | |
| Liftoff Monetize | 7.4.3.2+ | |
| Pangle | 7.1.0.4.0+ | |
| Yandex | 7.12.2.1+ |
Anchored adaptive banners are those you anchor at the top or bottom of the screen. They dynamically adjust their height based on the device type and the banner width.
You must set the height of the MaxAdView to the value returned by MaxAdFormat.BANNER.getAdaptiveSize( Context ).getHeight() instead of using a constant value like 50 or 90.
For more specific integrations, you can configure a custom width in dp by calling a MaxAdViewConfiguration builder method.
To fetch the appropriate height for your custom anchored adaptive ad, call the adaptive size API.
Adaptive banners are anchored by default. You can also enable inline adaptive banners, which you can place in scrollable content. Inline adaptive banners are typically larger than anchored adaptive banners. They have variable heights that can extend to the full height of the device screen.
To enable inline adaptive banners, set the MaxAdViewConfiguration adaptive type to MaxAdViewConfiguration.AdaptiveType.INLINE as shown in the code below:
“Why mobile banners ads persist in a video and playable world” from AppLovin’s Blog.
Google bidding and Google AdMob, Google Ad Manager, Liftoff Monetize, Pangle, and Yandex support adaptive banners. MAX sizes banners from other networks in the non-adaptive way.
Google recommends that developers include a 50 px padding between the banner placement and the app content. This makes it less likely that users accidentally click the banner. Refer to Google’s “About Confirmed Click” policy for more information and best practices.