Untuk mendiskusikan dan memberikan masukan tentang produk kami, bergabunglah ke channel Discord AdMob resmi di server Komunitas Iklan dan Pengukuran Google.
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Mediasi AdMob adalah fitur yang memungkinkan Anda menayangkan iklan ke aplikasi dari beberapa sumber, termasuk Jaringan AdMob dan sumber iklan pihak ketiga, di satu tempat. Mediasi AdMob membantu memaksimalkan rasio pengisian dan meningkatkan monetisasi dengan mengirimkan permintaan iklan ke beberapa jaringan untuk memastikan Anda menemukan jaringan terbaik yang tersedia untuk menayangkan iklan.
Studi kasus.
Prasyarat
Sebelum dapat mengintegrasikan mediasi untuk format iklan, Anda harus mengintegrasikan
format iklan tersebut ke dalam aplikasi:
Untuk bidding:
Google Mobile Ads SDK 18.3.0
atau yang lebih tinggi.
Menginisialisasi Google Mobile Ads SDK
Panduan memulai cepat ini menunjukkan cara menginisialisasi Google Mobile Ads SDK.
Selama panggilan inisialisasi tersebut, adaptor mediasi juga diinisialisasi. Penting untuk menunggu inisialisasi selesai sebelum
Anda memuat iklan untuk memverifikasi partisipasi penuh dari setiap jaringan iklan pada
permintaan iklan pertama.
Contoh kode berikut menunjukkan cara memeriksa status inisialisasi setiap adaptor sebelum membuat permintaan iklan.
Java
publicvoidinitialize(Contextcontext){newThread(()->
// Initialize the Google Mobile Ads SDK on a background thread.MobileAds.initialize(context,this::logAdapterStatus)).start();}privatevoidlogAdapterStatus(InitializationStatusinitializationStatus){// Check each adapter's initialization status.Map<String,AdapterStatus>statusMap=initializationStatus.getAdapterStatusMap();for(Map.Entry<String,AdapterStatus>entry:statusMap.entrySet()){StringadapterClass=entry.getKey();AdapterStatusstatus=entry.getValue();Log.d(TAG,String.format("Adapter name: %s, Description: %s, Latency: %d",adapterClass,status.getDescription(),status.getLatency()));}}
funinitialize(context:Context){CoroutineScope(Dispatchers.IO).launch{// Initialize the Google Mobile Ads SDK on a background thread.MobileAds.initialize(context,::logAdapterStatus)}}privatefunlogAdapterStatus(initializationStatus:InitializationStatus){// Check each adapter's initialization status.for((adapterClass,status)ininitializationStatus.adapterStatusMap){Log.d(TAG,"Adapter: $adapterClass, Status: ${status.description}, Latency: ${status.latency}ms",)}}
Periksa class adaptor jaringan iklan mana yang memuat iklan
Berikut adalah beberapa contoh kode yang mencatat nama class jaringan iklan untuk iklan banner:
Java
ResponseInforesponseInfo=ad.getResponseInfo();StringadapterClassName=null;if(responseInfo!=null){adapterClassName=responseInfo.getMediationAdapterClassName();}Log.d(TAG,"Adapter class name: "+adapterClassName);
Lihat dokumentasi ResponseInfo di getMediationAdapterClassName()
untuk mengetahui detail tentang metode ini.
Lakukan inisialisasi objek iklan Anda dengan instance Aktivitas
Di konstruktor untuk objek iklan baru (misalnya,
AdView),
Anda harus meneruskan objek jenis
Context.
Context ini diteruskan ke jaringan iklan lain saat menggunakan mediasi. Beberapa
jaringan iklan memerlukan Context yang lebih ketat dan berjenis
Activity
serta mungkin tidak dapat menayangkan iklan tanpa instance Activity. Oleh karena itu, sebaiknya teruskan instance Activity saat menginisialisasi objek iklan untuk memverifikasi pengalaman yang konsisten dengan jaringan iklan mediasi Anda.
Menggunakan iklan banner dengan Mediasi AdMob
Pastikan untuk menonaktifkan refresh di semua UI sumber iklan pihak ketiga untuk unit iklan banner yang digunakan dalam Mediasi AdMob. Hal ini mencegah refresh ganda karena
AdMob juga memicu refresh berdasarkan kecepatan refresh
unit iklan banner Anda.
Menggunakan iklan native dengan Mediasi AdMob
Berikut adalah beberapa praktik terbaik yang perlu dipertimbangkan saat menerapkan iklan native
di Mediasi AdMob.
Kebijakan presentasi iklan native
Setiap jaringan iklan memiliki kebijakannya sendiri. Saat menggunakan mediasi, penting untuk
mengingat bahwa aplikasi Anda tetap harus mematuhi kebijakan jaringan
termediasi yang menyediakan iklan.
Gunakan loadAd(), bukan loadAds()
Metode loadAds() hanya menayangkan iklan Google. Untuk iklan yang dimediasi, gunakan
loadAd().
Hukum privasi negara bagian Amerika Serikat dan GDPR
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Informasi yang saya butuhkan tidak ada","missingTheInformationINeed","thumb-down"],["Terlalu rumit/langkahnya terlalu banyak","tooComplicatedTooManySteps","thumb-down"],["Sudah usang","outOfDate","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Masalah kode / contoh","samplesCodeIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-06 UTC."],[[["\u003cp\u003eAdMob Mediation lets you maximize ad revenue by serving ads from multiple ad networks, including AdMob and third-party sources, all in one place.\u003c/p\u003e\n"],["\u003cp\u003eBefore integrating mediation, ensure you have the necessary account permissions and integrate the desired ad format (banner, interstitial, native, rewarded, or rewarded interstitial) into your app.\u003c/p\u003e\n"],["\u003cp\u003eIt is crucial to initialize the Mobile Ads SDK and wait for initialization to complete before loading ads to ensure all ad networks participate in the first ad request.\u003c/p\u003e\n"],["\u003cp\u003eWhen using AdMob Mediation, remember to disable refresh in third-party ad source UIs for banner ads to prevent double refreshing and adhere to each ad network's policies for native ad presentation.\u003c/p\u003e\n"],["\u003cp\u003eTo comply with privacy regulations like GDPR or US state privacy laws, add your mediation partners to the AdMob Privacy & Messaging settings to avoid ad serving disruptions.\u003c/p\u003e\n"]]],["AdMob Mediation serves ads from multiple sources, maximizing fill rates. Before configuring, verify account permissions and integrate desired ad formats (banner, interstitial, native, rewarded). Initialize the Mobile Ads SDK and wait for adapter initialization completion. Pass an `Activity` instance when creating ad objects. Disable refresh in third-party ad sources for banner units and utilize `loadAd()` for mediated native ads. Comply with U.S. states privacy laws and GDPR by adding mediation partners in AdMob's Privacy & messaging settings.\n"],null,["AdMob Mediation is a feature lets you serve ads to your apps from\nmultiple sources, including the AdMob Network and third-party ad sources, in\none place. AdMob Mediation helps maximize your fill rate and increase your\nmonetization by sending ad requests to multiple networks to verify you find the\nbest available network to serve ads.\n[Case study](//admob.google.com/home/resources/cookapps-grows-ad-revenue-86-times-with-admob-rewarded-ads-and-mediation/).\n\n\nPrerequisites **Important:** Verify that you have the necessary account permissions to complete the mediation configuration. These permissions include access to inventory management, app access, and privacy and messaging features. See [Manage user access to your\n| account](//support.google.com/admob/answer/2784628) for details.\n\nBefore you can integrate mediation for an ad format, you need to integrate that\nad format into your app:\n\n- [Banner Ads](/admob/android/banner)\n- [Interstitial Ads](/admob/android/interstitial)\n- [Native Ads](/admob/android/native)\n- [Rewarded Ads](/admob/android/rewarded)\n- [Rewarded Interstitial\n Ads](/admob/android/rewarded-interstitial)\n\nNew to mediation? Read\n\n[Overview of AdMob Mediation](//support.google.com/admob/answer/3063564).\n\nFor bidding:\n\nGoogle Mobile Ads SDK 18.3.0\nor higher.\n\nInitialize Google Mobile Ads SDK\n\nThe quick start guide shows you how to [initialize the Google Mobile Ads SDK](/admob/android/quick-start#initialize_the_mobile_ads_sdk).\nDuring that initialization call, mediation adapters also\nget initialized. It is important to wait for initialization to complete before\nyou load ads in order to verify full participation from every ad network on the\nfirst ad request.\n| **Important:** Bidding adapters require you to explicitly initialize Google Mobile Ads SDK.\n\nThe following sample code shows how you can check each adapter's initialization\nstatus prior to making an ad request. \n\nJava \n\n public void initialize(Context context) {\n new Thread(\n () -\u003e\n // Initialize the Google Mobile Ads SDK on a background thread.\n MobileAds.initialize(context, this::logAdapterStatus))\n .start();\n }\n\n private void logAdapterStatus(InitializationStatus initializationStatus) {\n // Check each adapter's initialization status.\n Map\u003cString, AdapterStatus\u003e statusMap = initializationStatus.getAdapterStatusMap();\n for (Map.Entry\u003cString, AdapterStatus\u003e entry : statusMap.entrySet()) {\n String adapterClass = entry.getKey();\n AdapterStatus status = entry.getValue();\n Log.d(\n TAG,\n String.format(\n \"Adapter name: %s, Description: %s, Latency: %d\",\n adapterClass, status.getDescription(), status.getLatency()));\n }\n } \n https://github.com/googleads/googleads-mobile-android-examples/blob/ccc290a583d7f552bdcf81ea76adc05beaa43f0b/java/advanced/APIDemo/app/src/main/java/com/google/android/gms/snippets/MediationSnippets.java#L30-L50\n\nKotlin \n\n fun initialize(context: Context) {\n CoroutineScope(Dispatchers.IO).launch {\n // Initialize the Google Mobile Ads SDK on a background thread.\n MobileAds.initialize(context, ::logAdapterStatus)\n }\n }\n\n private fun logAdapterStatus(initializationStatus: InitializationStatus) {\n // Check each adapter's initialization status.\n for ((adapterClass, status) in initializationStatus.adapterStatusMap) {\n Log.d(\n TAG,\n \"Adapter: $adapterClass, Status: ${status.description}, Latency: ${status.latency}ms\",\n )\n }\n } \n https://github.com/googleads/googleads-mobile-android-examples/blob/ccc290a583d7f552bdcf81ea76adc05beaa43f0b/kotlin/advanced/APIDemo/app/src/main/java/com/google/android/gms/snippets/MediationSnippets.kt#L25-L41\n\nCheck which ad network adapter class loaded the ad\n\nHere is some sample code that logs the ad network class name for a banner ad: \n\nJava \n\n ResponseInfo responseInfo = ad.getResponseInfo();\n String adapterClassName = null;\n if (responseInfo != null) {\n adapterClassName = responseInfo.getMediationAdapterClassName();\n }\n Log.d(TAG, \"Adapter class name: \" + adapterClassName); \n https://github.com/googleads/googleads-mobile-android-examples/blob/ccc290a583d7f552bdcf81ea76adc05beaa43f0b/java/advanced/APIDemo/app/src/main/java/com/google/android/gms/snippets/ResponseInfoSnippets.java#L46-L51\n\nKotlin \n\n Log.d(TAG, \"Adapter class name:\" + ad.responseInfo?.mediationAdapterClassName) \n https://github.com/googleads/googleads-mobile-android-examples/blob/ccc290a583d7f552bdcf81ea76adc05beaa43f0b/kotlin/advanced/APIDemo/app/src/main/java/com/google/android/gms/snippets/ResponseInfoSnippets.kt#L42-L42\n\nRefer to the `ResponseInfo` documentation on `getMediationAdapterClassName()`\nfor details about this method.\n\nInitialize your ad object with an Activity instance\n\nIn the constructor for a new ad object (for example,\n\n[`AdView`](/admob/android/reference/com/google/android/gms/ads/AdView)),\n\nyou must pass in an object of type\n[`Context`](//developer.android.com/reference/android/content/Context.html).\nThis `Context` is passed on to other ad networks when using mediation. Some\nad networks require a more restrictive `Context` that is of type\n[`Activity`](//developer.android.com/reference/android/app/Activity.html)\nand may not be able to serve ads without an `Activity` instance. Therefore,\nwe recommend passing in an `Activity` instance when initializing ad objects\nto verify a consistent experience with your mediated ad networks.\n\n\u003cbr /\u003e\n\nUse banner ads with AdMob Mediation\n\nMake sure to disable refresh in all third-party ad source UIs for banner ad\nunits used in AdMob Mediation. This prevents a double refresh since\nAdMob also triggers a refresh based on your banner ad unit's\nrefresh rate.\n\nUse native ads with AdMob Mediation\n\nThe following are some best practices to consider when implementing native ads\nin AdMob Mediation.\n\nNative ad presentation policy\n: Each ad network has its own policies. When using mediation, it's important to\n remember that your app still needs to abide by the policies of the mediated\n network that provided the ad.\n\nUse `loadAd()` instead of `loadAds()`\n: The `loadAds()` method serves only Google ads. For mediated ads, use\n `loadAd()` instead.\n\nUS states privacy laws and GDPR\n\nIf you need to comply with the [U.S. states privacy\nlaws](//support.google.com/admob/answer/9561022) or [General Data Protection\nRegulation (GDPR)](//support.google.com/admob/answer/7666366), follow the\nsteps in [US state regulations\nsettings](//support.google.com/admob/answer/10860309) or [GDPR\nsettings](//support.google.com/admob/answer/10113004#adding_ad_partners_to_published_gdpr_messages) to add your\nmediation partners in AdMob Privacy \\& messaging's\nUS states or GDPR ad partners list. Failure to do so can lead to partners\nfailing to serve ads on your app.\n\nLearn more about enabling [restricted data processing\n(RDP)](/admob/android/privacy/us-states) and obtaining GDPR consent with the\n[Google User Messaging Platform (UMP) SDK](/admob/android/privacy)."]]