Naver Ad Manager SDK for Android

Integrating the Naver Ad Manager(NAM) SDK into an app is the first step toward displaying ads and earning revenue. Once you've integrated the SDK, you can choose an ad format (such as banner or native or rewarded or interstitial) and follow the steps to implement it.

Before you begin

To prepare your app, complete the steps in the following sections.

App prerequisites

• Use Android Studio 3.2 or higher
• Make sure that your app's build file uses the following values:
• A minSdkVersion of 21 or higher
• A compileSdkVersion of 28 or higher

Configure your app

1. In your project-level build.gradle file, include Google's Maven repository and Maven central repository in both your buildscript and allprojects sections:

buildscript {
	repositories {
		google()
		mavenCentral()
	}
}

allprojects {
	repositories {
		google()
		mavenCentral()
	}
}

2. Set the compile options to java 8, in your module's app-level Gradle file, normally app/build.gradle:

android {
	compileOptions {
		sourceCompatibility JavaVersion.VERSION_1_8
		targetCompatibility JavaVersion.VERSION_1_8
	}
}

3. Add the dependencies for the Naver Ad Manager SDK to your module's app-level Gradle file, normally app/build.gradle:

(Required) Add the core dependency

dependencies {
implementation platform('com.naver.gfpsdk:nam-bom:<latest-version>')
implementation 'com.naver.gfpsdk:nam-core' // no version specified
}

Note: You can avoid specifying the version of each dependency with a Bill Of Materials.

(Optional) Add the mediation dependencies

For S2S mediation, make sure the following dependencies are place:

dependencies {
implementation 'com.naver.gfpsdk:nam-nda' // no version specified
}

For Google Ad Manager mediation, make sure the following dependencies are place:

dependencies {
implementation 'com.naver.gfpsdk:nam-dfp' // no version specified
}

For Meta Audience Network mediation, make sure the following dependencies are place:

dependencies {
implementation 'com.naver.gfpsdk:nam-fan' // no version specified
}

For InMobi mediation, make sure the following dependencies are place:

dependencies {
implementation 'com.naver.gfpsdk:nam-inmobi' // no version specified
}

For Unity mediation, make sure the following dependencies are place:

dependencies {
implementation 'com.naver.gfpsdk:nam-unity' // no version specified
}

For AppLovin mediation, make sure the following dependencies are place:

dependencies {
implementation 'com.naver.gfpsdk:nam-applovin' // no version specified
}

For Vungle mediation, make sure the following dependencies are place:

dependencies {
implementation 'com.naver.gfpsdk:nam-vungle' // no version specified
}

For Naver In-Stream ads, please adds following dependency:

dependencies {
implementation 'com.naver.gfpsdk:nam-ndavideo' // no version specified
}

For DigitalTurbine mediation, make sure the following dependencies are place:

dependencies {
implementation 'com.naver.gfpsdk:nam-dt' // no version specified
}

To use header bidding for Banner with Amazon Publusher Services, make sure the following dependencies are place:

dependencies {
implementation 'com.naver.gfpsdk:nam-aps' // no version specified
}

For IronSource mediation, make sure the following dependencies are place:

dependencies {
implementation 'com.naver.gfpsdk:nam-ironsource' // no version specified
}

For LAN mediation, make sure the following dependencies are place:

dependencies {
implementation 'com.naver.gfpsdk:nam-lan' // no version specified
}

4. Add your Publisher Code to your app's AndroidManifest.xml file.

To do so, add a <meta-data> tag with android:name="com.naver.gfpsdk.PUBLISHER_CD". For android:value, insert your own Publisher Code.

<manifest>
	<application>
		<meta-data
			android:name="com.naver.gfpsdk.PUBLISHER_CD"
			android:value="@string/publisher_cd" />
	</application>
</manifest>

Note: GfpSdkInitProvider will handle the initialization of NAM SDK. This ContentProvider is merged into the app's manifest by default when building with Gradle, and it runs automatically at app launch. No additional lines of code are needed in this case.

5. Select an ad format

NAM SDK is now imported and you're ready to implement an ad. NAM SDK offers a number of differenct ad formats, so you can choose the one that best fits your app's user experience.

Ad Provider	Description
Banner Ads	Rectangular ads that appear at the top or bottom of the device screen. Banner ads stay on screen while users are interacting with the app, and can refresh automatically after a certain period of time. If you're new to mobile advertising, they're a great place to start.
Native Ads	Customizable ads that match the look and feel of your app. You decide how and where they're placed, so the layout is more consistent with your app's design.
Native Simple Ads	Native Simple has been designed to make the implementation of native ads as easy as possible, and it's a great choice if you are new to the format.
In Stream Ads	In-Stream (Video) AD is placed between the beginning and the end of the video content.
Rewarded Ads	Rewarded ads provide incentives and rewards to users when they complete watching a video in full screen.

6. Select ad provider you want to integrate

NAM SDK mediation supports several ad provider, with a mix of bidding and waterfall mediation integrations. Select an ad provider below for integration instructions specific to that ad provider.

Ad Provider	Banner	Native	Native Simple	Rewarded	Interstitial	Description
NDA	O	O	O	O	X	S2S provider (Naver, Pubmatic, AppNexus, Rubicon, ...)
DFP	O	O	X	O	O	Google Ad Manager provider
FAN	O	O	X	O	O	Meta Audience Network provider
INMOBI	O	O	X	X	X	InMobi provider
UNITY	O	X	X	O	O	Unity provider
APPLOVIN	O	X	X	O	O	AppLovin provider
VUNGLE	X	X	X	O	O	Vungle provider
DigitalTurbine	O	X	X	O	O	DigitalTurbine provider
APS	O	X	X	X	X	AmazonPublisherServices provider (for header bidding)
LAN	X	O	O	O	O	Line provider
IronSource	X	X	X	O	O	IronSource provider

Note: After contacting the NAM manager, add the module of the Ad provider you want to add to.

7. (Optional) Targeting your ads

NAM SDK provides an option for developers to send targeting data. More information can be found here.

API

The documentation for latest version is available on here

Demo apps

• Java Example
• Kotlin Example

Note: These applications are provided for demo purposes only. Do NOT use in production.

Feedback and getting help

Bugs and feature requests can be filed with GitHub Issues.

License

NAM(Naver Ad Manager) SDK for Android
Copyright 2022-present NAVER Corp.
All rights reserved.
Unauthorized use, modification and redistribution of this software are strongly prohibited.