Integrate Leadbolt with mediation
Stay organized with collections
Save and categorize content based on your preferences.
This guide is intended for publishers who are interested in using Google
Mobile Ads mediation with Leadbolt. It walks
through the setup of a mediation adapter to work with your current Android app
and the configuration of additional settings.
Prerequisites
Helpful primers
The following Help Center articles provide background information on mediation:
Add Leadbolt to your project
Include network adapter and SDK
Download the Leadbolt SDK and adapter from the
previous links.
In Android Studio, include the adapter and SDK files in your project's libs
folder. Make sure that your app-level Gradle file includes the following:
Kotlin
dependencies {
implementation(fileTree(mapOf("dir" to "libs", "include" to listOf("*.aar", "*.jar"))))
// ...
}
Groovy
dependencies {
implementation fileTree(dir: 'libs', include: ['*.aar', '*.jar'])
// ...
}
Modify your AndroidManifest.xml file as instructed in the
Leadbolt documentation.
Your app doesn't need to call Leadbolt
directly—
Next Gen Mobile Ads SDK
calls the
Leadbolt adapter to fetch ads on your behalf. If necessary, you can
specify any additional request parameters.
The rest of this page details how to provide more information to
Leadbolt.
Initialize your ad object with an Activity instance
In the constructor for a new ad object (for example,
AdView),
you must pass in an object of type
Context.
This Context is passed on to other ad networks when using mediation. Some
ad networks require a more restrictive Context that is of type
Activity
and may not be able to serve ads without an Activity instance. Therefore,
we recommend passing in an Activity instance when initializing ad objects
to ensure a consistent experience with your mediated ad networks.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-08-22 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-22 UTC."],[[["\u003cp\u003eThis guide explains how to integrate Leadbolt ads into your Android app using Google Mobile Ads Mediation.\u003c/p\u003e\n"],["\u003cp\u003ePublishers need an existing Android app with Google Mobile Ads SDK and an AdMob account with ad units configured for mediation.\u003c/p\u003e\n"],["\u003cp\u003eThe integration process involves adding the Leadbolt SDK and adapter to your project and configuring the AndroidManifest.xml file as per Leadbolt's instructions.\u003c/p\u003e\n"],["\u003cp\u003eInitialization of ad objects is recommended with an Activity instance for better compatibility with mediated ad networks like Leadbolt.\u003c/p\u003e\n"]]],["This guide details integrating Leadbolt with Google Mobile Ads mediation for Android apps. Key actions include: downloading the Leadbolt SDK and adapter, adding them to the project's `libs` folder, and modifying the `AndroidManifest.xml` file as per Leadbolt's instructions. The guide emphasizes that the Google Mobile Ads SDK handles ad fetching, not the app directly. It also recommends initializing ad objects with an `Activity` instance for compatibility with mediated ad networks.\n"],null,["This guide is intended for publishers who are interested in using Google\nMobile Ads mediation with **Leadbolt**. It walks\nthrough the setup of a mediation adapter to work with your current Android app\nand the configuration of additional settings.\n\n| Leadbolt Resources |\n|-----------------------------------------------------------|\n| [Documentation](https://www.leadboltapps.com) |\n| [SDK](https://www.leadboltapps.com) |\n| [Adapter](https://www.leadboltapps.com) |\n| [Customer support](https://www.leadboltapps.com/contact/) |\n\nPrerequisites\n\n- An Android app with the Google Mobile Ads SDK 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\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 Leadbolt to your project\n\nInclude network adapter and SDK\n\nDownload the Leadbolt 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\nKotlin \n\n dependencies {\n implementation(fileTree(mapOf(\"dir\" to \"libs\", \"include\" to listOf(\"\\*.aar\", \"\\*.jar\"))))\n // ...\n }\n\nGroovy \n\n dependencies {\n implementation fileTree(dir: 'libs', include: \\['\\*.aar', '\\*.jar'\\])\n // ...\n }\n\nConfigure the AndroidManifest.xml file\n\nModify your `AndroidManifest.xml` file as instructed in the\nLeadbolt documentation.\n\nYour app doesn't need to call Leadbolt\ndirectly---the Google Mobile Ads SDK calls the\nLeadbolt 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\nLeadbolt.\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/early-access/nextgen/reference/com/google/android/libraries/ads/mobile/sdk/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."]]