This guide shows you how to use the Google Mobile Ads SDK to load and display ads from Line using mediation, covering waterfall integrations. It covers how to add Line to an ad unit's mediation configuration, and how to integrate the Line SDK and adapter into an Android app.
The dashboard interface for Line uses Japanese text for its labels, buttons, and descriptions. The screenshots in this guide have not been translated. In this guide's descriptions and instructions however, labels and buttons are translated with their English language equivalents in parentheses.
Supported integrations and ad formats
The AdMob mediation adapter for Line has the following capabilities:
| Integration | |
|---|---|
| Bidding | |
| Waterfall | 1 |
| Formats | |
| Banner | |
| Interstitial | |
| Rewarded | |
| Native | |
1 Waterfall integration is in open beta.
Requirements
- Android API level 21 or higher
Latest Google Mobile Ads SDK
Complete the mediation Get started guide
Step 1: Set up configurations in Line UI
Log in to your Line account.
Add a new application
Click 広告枠管理 (Ad Slot Management) > メディア (Media). Then, click 新規作成 (Create New).
Fill out the form and click 登録 (Register).
Take note of the Application ID.
Create an ad placement
Click the ID of the application you want to add an ad placement. Then, select 詳細 (Detail).
Click スロット 追加 (Add Slot).
Fill out the form and once done, click (登録) Register.
Take note of the Slot ID.
Step 2: Set up Line demand in AdMob UI
Configure mediation settings for your ad unit
You need to add Line to the mediation configuration for your ad unit.
First, sign in to your AdMob account. Next, navigate to the Mediation tab. If you have an existing mediation group you'd like to modify, click the name of that mediation group to edit it, and skip ahead to Add Line as an ad source.
To create a new mediation group, select Create Mediation Group.
Enter your ad format and platform, then click Continue.
Give your mediation group a name, and select locations to target. Next, set the mediation group status to Enabled, and then click Add Ad Units.
Associate this mediation group with one or more of your existing AdMob ad units. Then click Done.
You should now see the ad units card populated with the ad units you selected:
Add Line as an ad source
Under the Waterfall card in the Ad Sources section, select Add Ad Source. Then select Line.
Select Line. Then enter an eCPM value for Line and click Continue.
If you already have a mapping for Line, you can select it. Otherwise, click Add mapping.
Next, enter the Application ID and Slot ID obtained in the previous section. Then click Done.
Step 3: Import the Line SDK and Adapter
Android Studio integration (recommended)
In your app-level build.gradle.kts file, add the following implementation
dependencies and configurations. Use the latest versions of the Line SDK
and adapter:
dependencies {
implementation("com.google.android.gms:play-services-ads:23.0.0")
implementation("com.google.ads.mediation:line:2.7.20240214.1")
}
Manual integration
Download the latest version of the Line SDK's
.aarfile and add it to your project.Navigate to the Line adapter artifacts on Google's Maven Repository. Select the latest version, download the Line adapter's
.aarfile, and add it to your project.
Step 4: Add required code
No additional code is required for Line integration.
Step 5: Test your implementation
Enable test ads
Make sure you register your test device for AdMob.
Follow the instructions in Line's documentation on how to enable Line test ads.
Verify test ads
To verify that you are receiving test ads from Line, enable single ad source testing in ad inspector using the Line (Waterfall) ad source(s).
Optional steps
Network-specific parameters
The Line adapter supports an additional request parameter which can be passed
to the adapter using the LineExtras class. This class constructor includes
the following parameters:
enableAdSound- A
booleanto specify the default sound start state of banner, interstitial and rewarded ads.
Here's a code example of how to create an ad request that sets these parameters:
Java
LineExtras lineExtras = new LineExtras(true);
Bundle extras = lineExtras.build();
AdRequest request = new AdRequest.Builder()
.addNetworkExtrasBundle(LineMediationAdapter.class, extras)
.build();
Kotlin
val lineExtras = LineExtras(true)
val extras = lineExtras.build()
val request = AdRequest.Builder()
.addNetworkExtrasBundle(LineMediationAdapter::class.java, extras)
.build()
Using native ads
Ad rendering
The Line adapter populates the following
Native ads advanced field descriptions
for a
NativeAd.
| Field | Assets always included by Line adapter |
|---|---|
| Headline | |
| Image | |
| Body | |
| App icon | 1 |
| Call to action | |
| Star rating | |
| Store | |
| Price |
1 For native ads, the Line SDK does not provide an app icon asset. Instead, the Line adapter populates the app icon with a transparent image.
Error codes
If the adapter fails to receive an ad from Line, you can check the
underlying error from the ad response using
ResponseInfo.getAdapterResponse()
under the following classes:
com.line.ads
com.google.ads.mediation.line.LineMediationAdapter
Here are the codes and accompanying messages thrown by the Line adapter when an ad fails to load:
| Error code | Domain | Reason |
|---|---|---|
| 1-10 | com.five_corp.ad | Line SDK returned an SDK-specific error. See Line's documentation for more details. |
| 101 | com.google.ads.mediation.line | Missing or invalid Application ID. |
| 102 | com.google.ads.mediation.line | Missing or invalid Slot ID. |
| 103 | com.google.ads.mediation.line | The requested ad size does not match a Line supported banner ad size. |
| 104 | com.google.ads.mediation.line | Failed to load an interstitial or rewarded ad due to missing activity context. |
| 105 | com.google.ads.mediation.line | Line SDK failed to show an interstitial or rewarded ad. |
| 106 | com.google.ads.mediation.line | Failed to load a native ad due to missing assets. |
LINE Android Mediation Adapter Changelog
Version 2.7.20240214.1
- Updated the minimum required Google Mobile Ads SDK version to 23.0.0.
- Verified compatibility with FiveAd SDK version 2.7.20240214.0.
Built and tested with:
- Google Mobile Ads SDK version 23.0.0.
- FiveAd SDK version 2.7.20240214.0.
Version 2.7.20240214.0
- Verified compatibility with FiveAd SDK version 2.7.20240214.0.
Built and tested with:
- Google Mobile Ads SDK version 22.6.0.
- FiveAd SDK version 2.7.20240214.0.
Version 2.7.20240126.0
- Verified compatibility with FiveAd SDK version 2.7.20240126.0.
Built and tested with:
- Google Mobile Ads SDK version 22.6.0.
- FiveAd SDK version 2.7.20240126.0.
Version 2.7.20240112.0
- Removed deprecated
FiveAdViewEventListenerin favor ofFiveAdCustomLayoutEventListener,FiveAdVideoRewardEventListener,FiveAdInterstitialEventListenerandFiveAdNativeEventListener. - Verified compatibility with FiveAd SDK version 2.7.20240112.
- Updated the minimum required Google Mobile Ads SDK version to 22.6.0.
Built and tested with:
- Google Mobile Ads SDK version 22.6.0.
- FiveAd SDK version 2.7.20240112.
Version 2.6.20230607.1
- Added
LineExtrasclass for publishers to define default sound settings for banner, interstitial and rewarded ad formats. - Updated the minimum required Google Mobile Ads SDK version to 22.4.0.
Built and tested with:
- Google Mobile Ads SDK version 22.4.0.
- FiveAd SDK version 2.6.20230607.
Version 2.6.20230607.0
- Initial release.
- Adds support for banner, interstitial, rewarded and native ad formats.
- Verified compatibility with FiveAd SDK version 2.6.20230607.
Built and tested with:
- Google Mobile Ads SDK version 22.1.0.
- FiveAd SDK version 2.6.20230607.