Integrate Line with Mediation (Beta)

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 mediation adapter for Line has the following capabilities:

Integration
Bidding
Waterfall	^1
Formats
Banner
Interstitial
Rewarded
Native

¹ Waterfall integration is in closed beta, reach out to your account manager to request access.

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.

Note: Reach out to your Line Ads Network account manager to get access to create native ad placements in the Line UI.

Take note of the Slot ID.

Step 2: Set up Line demand in Ad Manager UI

Sign in to your Ad Manager account.

Add Line in Companies

Bidding

This step isn't required for bidding integrations.

Waterfall

Navigate to Admin > Companies, then click the New company button in the All companies tab. Select Ad network.

Select Line as the Ad network, enter a unique Name and enable Mediation.

You don't need to enter a Username or Password. Click Save when done.

Enable secure signal sharing

Bidding

Navigate to Admin > Global settings. Go to the Ad Exchange account settings tab and review and toggle on Secure signal sharing. Click Save.

Waterfall

This step isn't required for waterfall integrations.

Configure Line bidding

Bidding

Navigate to Delivery > Bidders, and click New bidder under the SDK Bidding tab.

Select Line as the bidder.

Toggle on Add this bidder's signal library to the list of allowed signals and Allow signals to be shared with this bidder. Then, click Continue.

Click Continue.

Click Done.

Waterfall

This step isn't required for waterfall integrations.

Configure ad unit mapping

Bidding

Navigate to Delivery > Bidders, and select the company for Line under the SDK Bidding tab.

Go to the Ad unit mapping tab and click New ad unit mapping.

Choose Specific ad unit. Select an ad unit and format, Mobile app as the Inventory type, and your Mobile application. Then, enter Application ID and Slot ID obtained in the previous section. Finally, click Save.

Important: Target the selected ad unit by at least one yield group, and the Application ID must be associated with the targeted app as in the Line UI.

Waterfall

Navigate to Delivery > Yield groups and click the New yield group button. Select your Mobile application.

Scroll down and click Add yield partner.

Select the company you created for Line in the previous section. Choose Mobile SDK mediation as the Integration type, Android as the Platform, and Active as the Status.

Enter the Application ID and Slot ID obtained in the previous section, and the Default CPM value. Click Save.

Important: The Application ID must be associated with the targeted app as in the Line UI.

Step 3: Import the Line SDK and Adapter

Note: Failure to integrate the compatible Line and Google Mobile Ads SDK versions might lead to build issues.

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.5.0")
    implementation("com.google.ads.mediation:line:2.8.20240827.0")
}

Manual integration

1. Download the latest version of the Line SDK's .aar file and add it to your project.

2. Navigate to the Line adapter artifacts on Google's Maven Repository. Select the latest version, download the Line adapter's .aar file, 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 Ad Manager.

Follow the instructions in Line's documentation on how to enable Line test ads.

Important: Disable test mode for Ad Manager and Line before releasing your app.

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 boolean to 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();

AdManagerAdRequest request = new AdManagerAdRequest.Builder()
   .addNetworkExtrasBundle(LineMediationAdapter.class, extras)
   .build();

Kotlin

val lineExtras = LineExtras(true)
val extras = lineExtras.build()

val request = AdManagerAdRequest.Builder()
   .addNetworkExtrasBundle(LineMediationAdapter::class.java, extras)
   .build()

Using native ads

Ad rendering

The Line adapter populates the following fields for a NativeAd.

Field	Assets always included by Line adapter
Headline
Image
Body
App icon	^1
Call to action
Star rating
Store
Price

¹ 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.getAdapterResponses() 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

Next Version

• Implemented AdLoader to enable RTB for Banner Ads.
• Implemented AdLoader to enable RTB for Interstitial Ads.
• Implemented AdLoader to enable RTB for Rewarded Ads.
• Implemented AdLoader to enable RTB for Native Ads.

Version 2.8.20240827.0

• Verified compatibility with FiveAd SDK version 2.8.20240827.0

Built and tested with:

• Google Mobile Ads SDK version 23.3.0.
• FiveAd SDK version 2.8.20240827.0

Version 2.8.20240808.0

• Verified compatibility with FiveAd SDK version 2.8.20240808.0

Built and tested with:

• Google Mobile Ads SDK version 23.2.0.
• FiveAd SDK version 2.8.20240808.0

Version 2.8.20240722.0

• Verified compatibility with FiveAd SDK version 2.8.20240722.0

Built and tested with:

• Google Mobile Ads SDK version 23.2.0.
• FiveAd SDK version 2.8.20240722.0

Version 2.7.20240515.0

• Verified compatibility with FiveAd SDK version 2.7.20240515.0

Built and tested with:

• Google Mobile Ads SDK version 23.1.0.
• FiveAd SDK version 2.7.20240515.0

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 FiveAdViewEventListener in favor of FiveAdCustomLayoutEventListener, FiveAdVideoRewardEventListener, FiveAdInterstitialEventListener and FiveAdNativeEventListener.
• 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 LineExtras class 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.