Mengintegrasikan Flurry dengan Mediasi
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Panduan ini ditujukan bagi penayang yang tertarik menggunakan mediasi Iklan Seluler Google dengan Flurry. Panduan ini menjelaskan penyiapan adaptor mediasi agar berfungsi dengan aplikasi Android Anda saat ini dan konfigurasi setelan tambahan.
Prasyarat
Panduan bermanfaat
Artikel Pusat Bantuan berikut memberikan informasi latar belakang tentang mediasi:
Menambahkan Flurry ke project Anda
Menyertakan adaptor jaringan dan SDK
Download SDK dan adaptor Flurry dari
link sebelumnya.
Di Android Studio, sertakan file adaptor dan SDK di folder libs
project Anda. Pastikan file Gradle level aplikasi Anda menyertakan kode berikut:
Kotlin
dependencies {
implementation(fileTree(mapOf("dir" to "libs", "include" to listOf("*.aar", "*.jar"))))
// ...
}
Groovy
dependencies {
implementation fileTree(dir: 'libs', include: ['*.aar', '*.jar'])
// ...
}
Ubah file AndroidManifest.xml Anda seperti yang diinstruksikan dalam
dokumentasi Flurry.
Aplikasi Anda tidak perlu memanggil Flurry
secara langsung—Google Mobile Ads SDK memanggil
adaptor Flurry untuk mengambil iklan atas nama Anda. Jika perlu, Anda dapat menentukan parameter permintaan tambahan.
Bagian selanjutnya dari halaman ini menjelaskan cara memberikan informasi selengkapnya kepada
Flurry.
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 memastikan pengalaman yang konsisten dengan jaringan iklan mediasi Anda.
Kecuali dinyatakan lain, konten di halaman ini dilisensikan berdasarkan Lisensi Creative Commons Attribution 4.0, sedangkan contoh kode dilisensikan berdasarkan Lisensi Apache 2.0. Untuk mengetahui informasi selengkapnya, lihat Kebijakan Situs Google Developers. Java adalah merek dagang terdaftar dari Oracle dan/atau afiliasinya.
Terakhir diperbarui pada 2025-08-31 UTC.
[null,null,["Terakhir diperbarui pada 2025-08-31 UTC."],[[["\u003cp\u003eThis guide explains how publishers can integrate Flurry ads into their Android apps using Google Mobile Ads mediation.\u003c/p\u003e\n"],["\u003cp\u003eYou'll need an Android app with the Google Mobile Ads SDK and an AdMob account with configured mediation line items to get started.\u003c/p\u003e\n"],["\u003cp\u003eThe guide provides steps to add the Flurry SDK and adapter to your project, configure your AndroidManifest.xml, and initialize your ad object with an Activity instance.\u003c/p\u003e\n"],["\u003cp\u003eThis integration allows the Google Mobile Ads SDK to automatically call the Flurry adapter to fetch ads for your app.\u003c/p\u003e\n"]]],["This guide details integrating Flurry with Google Mobile Ads mediation for Android apps. Key actions include: downloading the Flurry SDK and adapter, adding them to the project's `libs` folder, and modifying the `AndroidManifest.xml` file as per Flurry's documentation. Initializing ad objects with an `Activity` instance is recommended. The Google Mobile Ads SDK handles ad requests through the Flurry adapter. It provides links to Flurry resources and AdMob mediation guides.\n"],null,["# Integrate Flurry with Mediation\n\nThis guide is intended for publishers who are interested in using Google\nMobile Ads mediation with **Flurry**. It walks\nthrough the setup of a mediation adapter to work with your current Android app\nand the configuration of additional settings.\n\n| Flurry Resources |\n|------------------------------------------------------------------------|\n| [Documentation](http://www.flurry.com/) |\n| [SDK](http://dev.flurry.com/uploadVersionSelectProject.do) |\n| [Adapter](http://github.com/flurry/FlurryAdapterForDFPAndAdMobAndroid) |\n| [Customer support](mailto:support@flurry.com) |\n\nPrerequisites\n-------------\n\n- An Android app with\n\n Google Mobile Ads SDK\n\n integrated. (If you don't\n have one, see [Get Started](/admob/android/quick-start).)\n\n- An AdMob account and [an ad unit configured with mediation line\n items](//support.google.com/admob/answer/3124703).\n\nHelpful primers\n---------------\n\nThe following Help Center articles provide background information on mediation:\n\n- [About AdMob Mediation](//support.google.com/admob/answer/3063564)\n- [Set up AdMob Mediation](//support.google.com/admob/answer/3124703)\n- [Optimize AdMob Network](//support.google.com/admob/answer/3534471)\n\nAdd Flurry to your project\n--------------------------\n\n### Include network adapter and SDK\n\nDownload the Flurry SDK and adapter from the\n[previous links](#resources).\n\nIn Android Studio, include the adapter and SDK files in your project's `libs`\nfolder. Make sure that your app-level Gradle file includes the following: \n\n### Kotlin\n\n dependencies {\n implementation(fileTree(mapOf(\"dir\" to \"libs\", \"include\" to listOf(\"\\*.aar\", \"\\*.jar\"))))\n // ...\n }\n\n### Groovy\n\n dependencies {\n implementation fileTree(dir: 'libs', include: \\['\\*.aar', '\\*.jar'\\])\n // ...\n }\n\n### Configure the AndroidManifest.xml file\n\nModify your `AndroidManifest.xml` file as instructed in the\nFlurry documentation.\n\nYour app doesn't need to call Flurry\ndirectly---\n\nGoogle Mobile Ads SDK\n\ncalls the\nFlurry adapter to fetch ads on your behalf. If necessary, you can\nspecify any additional request parameters.\nThe rest of this page details how to provide more information to\nFlurry.\n\n### Initialize 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).\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)\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 ensure a consistent experience with your mediated ad networks."]]
