Skip to main content

Mediation Integration

NAVER Ad Manager provides various ad providers such as Google, Meta, etc., and allows you to selectively add separate modules for publishing ads from specific ad providers.

To check all the provided ad providers and the ad types supported by each provider, please refer to Ad Provider Information.

dependencies {
    implementation(platform("com.naver.gfpsdk:nam-bom:8.3.1"))
    implementation("com.naver.gfpsdk:nam-core")                 // NAM Core (required)
    implementation("com.naver.gfpsdk.mediation:nam-nda")        // NAVER S2S mediation
    implementation("com.naver.gfpsdk.mediation:nam-dfp")        // DFP mediation
    implementation("com.naver.gfpsdk.mediation:nam-fan")        // FAN mediation
    implementation("com.naver.gfpsdk.mediation:nam-inmobi")     // InMobi mediation
    implementation("com.naver.gfpsdk.mediation:nam-unity")      // Unity mediation
    implementation("com.naver.gfpsdk.mediation:nam-applovin")   // AppLovin(MAX) mediation
    implementation("com.naver.gfpsdk.mediation:nam-vungle")     // Vungle mediation
    implementation("com.naver.gfpsdk.mediation:nam-dt")         // DigitalTurbine(Fyber) mediation
    implementation("com.naver.gfpsdk.mediation:nam-aps")        // AmazonPublisherServices(APS) mediation
    implementation("com.naver.gfpsdk.mediation:nam-ironsource") // IronSource mediation
    implementation("com.naver.gfpsdk.mediation:nam-lan")        // Line mediation
    implementation("com.naver.gfpsdk.mediation:nam-bidmachine") // BidMachine mediation
    implementation("com.naver.gfpsdk.mediation:nam-chartboost") // Chartboost mediation
}

At this time, NAM provides a Bill of Materials (BOM) to manage all mediation module versions by specifying only the nam-bom version. By specifying the nam-bom version, stable mediation module versions compatible with the same version of the nam-core module are provided. Version-specific mediation module mapping information can be found in Version Compatibility.

Module Guide​

Below is a guide for additional considerations that may be required when integrating certain mediation modules.

Gradle Settings​

Some modules require the addition of third-party Gradle repositories.

IronSource​

repositories {
    maven {
        url = uri("https://android-sdk.is.com/")
    }
}

BidMachine​

repositories {
    maven {
        url = uri("https://artifactory.bidmachine.io/bidmachine")
    }
}

Chartboost​

repositories {
    maven {
        url = uri("https://cboost.jfrog.io/artifactory/chartboost-ads/")
    }
}

InMobi​

The InMobi library internally uses the Picasso library.

During the build process, it uses the com.android.support library, which may cause issues related to AndroidX.

Therefore, if you are using the nam-inmobi module, please set android.enableJetifier=true in the gradle.properties file.

DFP (Google) Module​

To initialize Google Ad Manager internally, the App ID must be registered in the AndroidManifest.xml file.

If you add the nam-dfp module without this configuration, the app may terminate abnormally.

<manifest>
  <application>
    <!-- Sample Ad Manager app ID: ca-app-pub-3940256099942544~3347511713 -->
    <meta-data
            android:name="com.google.android.gms.ads.APPLICATION_ID"
            android:value="ca-app-pub-xxxxxxxxxxxxxxxx~yyyyyyyyyy"/>
  </application>
</manifest>
info

You can find the complete sample in the GitHub repository NAM Android SDK.