Banner & MREC ads
© 2025 AppLovin. All rights reserved.
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 points, with code like the following:
You may want to stop auto-refresh for an ad. You may want to do this, for instance, when you hide a banner ad or you want to manually refresh. Stop auto-refresh for a banner or MREC ad with the following code:
Start auto-refresh for a banner or MREC ad with the following call:
Manually refresh the contents with the following call.
You must stop auto-refresh before you call loadAd().
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, create a MAAdView object that corresponds to your ad unit and call its loadAd method.
To show that ad, add the MAAdView object as a subview of your view hierarchy.
Implement MAAdViewAdDelegate so that you are notified when your ad is ready.
This also notifies you of other ad-related events.
To load a banner, create a MAAdView object that corresponds to your ad unit and call its loadAd method.
To show that ad, add the MAAdView object as a subview of your view hierarchy.
Implement MAAdViewAdDelegate so that you are notified when your ad is ready.
This also notifies you of other ad-related events.
To load a banner, create a UIViewRepresentable object, a wrapper that lets you integrate MAAdView, a UIKit view type object, into your SwiftUI view hierarchy.
Also provide a custom Coordinator class for the wrapper object that conforms to MAAdViewAdDelegate.
This notifies you when your ad is ready, and notifies you of other ad-related events.
Inside the wrapper’s makeUIView method, create a MAAdView object that corresponds to your ad unit.
Call its loadAd method.
To show that ad, add the UIViewRepresentable wrapper object inside your SwiftUI view hierarchy.
You can find implementation examples in the AppLovin-MAX_SDK_iOS Github repository.
To load an MREC ad, create a MAAdView object corresponding to your ad unit and call its loadAd method.
To show the ad, add the MAAdView object as a subview of your view hierarchy.
Implement MAAdViewAdDelegate so that you are notified when your ad is ready.
This also notifes you of other ad-related events.
To load an MREC ad, create a MAAdView object corresponding to your ad unit and call its loadAd method.
To show the ad, add the MAAdView object as a subview of your view hierarchy.
Implement MAAdViewAdDelegate so that you are notified when your ad is ready.
This also notifies you of other ad-related events.
To load an MREC ad, first create a UIViewRepresentable object, a wrapper that lets you integrate MAAdView, a UIKit view type object, into your SwiftUI view hierarchy.
Also provde a custom Coordinator class for the wrapper object that conforms to MAAdViewAdDelegate.
This notifies you when your ad is ready, and notifies you of other ad-related events.
Inside the wrapper’s makeUIView method, create a MAAdView object that corresponds to your ad unit and call its loadAd method.
To show that ad, add the UIViewRepresentable wrapper object inside your SwiftUI view hierarchy.
You can find implementation examples in the AppLovin-MAX_SDK_iOS Github repository.
You may no longer need a MAAdView instance.
This may happen, for example, if the user purchases ad removal.
Deallocate such a MAAdView instance to free resources.
Do not deallocate the MAAdView instance 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 MAAdView with a MAAdViewConfiguration object for which you set an adaptiveType at build-time.
The following adapters support special adaptive banner features:
| Network | Adapter Versions | Special Feature |
|---|---|---|
| Google Ad Manager | 11.7.0.1+ | Inline adaptive banners |
| 11.13.0.1+ | Inline adaptive MRECs | |
| 10.2.0.1+ | Setting a custom width | |
| Google Bidding and Google AdMob | 11.7.0.1+ | Inline adaptive banners |
| 11.13.0.1+ | Inline adaptive MRECs | |
| 10.2.0.2+ | Setting a custom width | |
| Liftoff Monetize | 7.4.5.1+ | |
| Pangle | 7.1.0.8.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 MAAdView to the value returned by MAAdFormat.banner.adaptiveSize.height instead of using a constant value like 50 or 90.
For more specific integrations, you can configure a custom width in points by setting a MAAdViewConfiguration builder option.
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 MAAdViewConfiguration adaptive type to MAAdViewAdaptiveTypeInline as shown in the code below:
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 points, for your inline adaptive ad to ensure that the ad fits in the height of the MAAdView.
You can do this with code like the following, which uses a maximum height of 100 points 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 points. 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.
To enable inline adaptive MRECs, set the MAAdViewConfiguration adaptive type to MAAdViewAdaptiveTypeInline as shown in the code below:
“Why mobile banners ads persist in a video and playable world” from AppLovin’s Blog.
If your integration requires displaying MREC ads in a content feed, AppLovin recommends this technique:
loadAd (re-use the MAAdView instances).You can find an example implementation in the AppLovin demo app (Objective-C, Swift).
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.