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.
To prepare your app, complete the steps in the following sections.
- Use Android Studio 3.2 or higher
- Make sure that your app's build file uses the following values:
- A
minSdkVersion
of21
or higher - A
compileSdkVersion
of28
or higher
- A
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
:
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
.
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.
NAM SDK is now imported and you're ready to implement an ad. NAM SDK offers a number of different 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. |
Mediation in NAM supports several ad source, with a mix of bidding and waterfall mediation integrations. Select an ad provider below for integration instructions specific to that ad source.
Ad Source |
---|
NAVER |
AppLovin |
Amazon Publisher Service |
Google Ad Manager |
Digital Turbine |
Meta Audience Network |
InMobi |
IronSource |
Line |
Unity |
Vungle |
Note
After contacting the NAM manager, add the module of the Mediation you want to integrate.
NAM SDK provides an option for developers to send targeting data. More information can be found here.
The documentation for latest version is available on here
Note
These applications are provided for demo purposes only. Do NOT use in production.
Bugs and feature requests can be filed with GitHub Issues.
See documentation for more information.
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.