Native Ad Integration Types Overview - MoPub-Solutions-Eng/mopub.wiki.android.native.betasite GitHub Wiki
MoPub provides the following three types of approaches to integrate native ads. They have different degrees of convenience and flexibility.
Ad Placer integration
This approach uses the MoPubStreamAdPlacer to facilitate loading native ads into an app's content stream (i.e. a scrolling list). The MoPub SDK provides a MoPubAdAdapter and a MoPubRecyclerAdapter that wrap your existing adapter subclasses to insert ads into a ListView and RecyclerView, respectively. This approach has the advantage of letting the MoPub SDK handle automatically requesting new ads when needed, inserting them into the stream of content, and handling impression tracking and clicks. By default, three native ads will be requested and cached initially, then the SDK will request one at a time as a user scrolls through the feed. Each ad's expiration time starts once the ad is loaded/cached, after 4 hours the SDK will mark these ads for clean up by the OS.
Manual integration
This approach is suitable for when the native ad placement is a single view, or in a content stream but when specific flexibility cannot be fulfilled by using the Ad Placer approach. With this method, you will use the MoPubNative class to request and load ads. The MoPub SDK provides an AdapterHelper that you can use to retrieve a pre-populated view containing the rendered ad content and required tracking events. That allows you to easily add the ad view into your parent view. However, publishers have to manually handle ad requests, ad expiration, and cases when there are no fills.
Custom Manual integration
The Custom Manual approach gives publishers the ability to extract ad assets and render them manually. This approach provides an additional degree of customization, and is useful for cases where more control over ad assets or ad view is needed. Same as the Manual approach, with this integration, publishers have to manually handle ad requests, ad expiring and cases where there is no fill.
As this is a customized approach, MoPub may not be able to provide technical support.