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 iOS 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

• iOS deployment target of 12.0 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, iOS 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.

Using CocoaPods (recommended)

Add the following line to your project's Podfile:

pod 'GoogleMobileAdsMediationLine'

From the command line run:

pod install --repo-update

Manual integration

• Download the latest version of the Line SDK and link FiveAd.framework in your project.
• Download the latest version of the Line adapter from the download link in Changelog and link LineAdapter.framework in your project.

Step 4: Add required code

SKAdNetwork integration

Follow Line's documentation to add the SKAdNetwork identifiers to your project's Info.plist file.

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 GADMediationAdapterLineExtras class. This class includes the following properties:

adAudio

Specifies 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:

Swift

import LineAdapter
// ...

let request = GAMRequest()
let extras = GADMediationAdapterLineExtras()
extras.adAudio = GADMediationAdapterLineAdAudio.unmuted
// ...
request.register(extras)

Objective-C

#import <LineAdapter/LineAdapter.h>
// ...

GAMRequest *request = [GAMRequest request];
GADMediationAdapterLineExtras *extras = [[GADMediationAdapterLineExtras alloc] init];
extras.adAudio = GADMediationAdapterLineAdAudioUnmuted;
// ...
[request registerAdNetworkExtras:extras];

Using native ads

Ad rendering

The Line adapter populates the following fields for a GADNativeAd.

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 GADResponseInfo.adNetworkInfoArray under the following classes:

GADMediationAdapterLine

Here are the codes and accompanying messages thrown by the Line adapter when an ad fails to load:

Error code	Domain	Reason
1-10	Sent by Line SDK	Line SDK returned an SDK-specific error. See Line's documentation for more details.
101	com.google.ads.mediation.line	Invalid server parameters (e.g. Missing Application ID or Slot ID).
102	com.google.ads.mediation.line	The requested ad size does not match a Line supported banner ad size.
103	com.google.ads.mediation.line	Failed to load an information icon image asset in native ad.

LINE iOS Mediation Adapter Changelog

Version 2.9.20241106.1

• Updated the adapter to use the latest ad load API for bidding banner ads.
• Fixed an issue preventing ad events from forwarding correctly for bidding interstitial ads.

Built and tested with:

• Google Mobile Ads SDK version 11.12.0.
• FiveAd SDK version 2.9.20241106.

Version 2.9.20241106.0

• Verified compatibility with FiveAd SDK version 2.9.20241106.

Built and tested with:

• Google Mobile Ads SDK version 11.12.0.
• FiveAd SDK version 2.9.20241106.

Version 2.8.20240827.1

• Updated CFBundleShortVersionString to have three components instead of four.

Built and tested with:

• Google Mobile Ads SDK version 11.10.0.
• FiveAd SDK version 2.8.20240827.

Version 2.8.20240827.0

• Verified compatibility with FiveAd SDK version 2.8.20240827.
• Added bidding support for banner, interstitial, rewarded, and native ad formats.

Built and tested with:

• Google Mobile Ads SDK version 11.8.0.
• FiveAd SDK version 2.8.20240827.

Version 2.8.20240612.0

• Added audio control for native ad via GADVideoOptions.
• Verified compatibility with FiveAd SDK version 2.8.20240612.

Built and tested with:

• Google Mobile Ads SDK version 11.5.0.
• FiveAd SDK version 2.8.20240612.

Version 2.7.20240411.0

• Verified compatibility with FiveAd SDK version 2.7.20240411.

Built and tested with:

• Google Mobile Ads SDK version 11.3.0.
• FiveAd SDK version 2.7.20240411.

Version 2.7.20240318.0

• Verified compatibility with FiveAd SDK version 2.7.20240318.

Built and tested with:

• Google Mobile Ads SDK version 11.2.0.
• FiveAd SDK version 2.7.20240318.

Version 2.7.20240214.1

• Now requires minimum iOS version 12.0.
• Now requires Google Mobile Ads SDK version 11.0 or higher.
• Included Info.plist in the frameworks within LineAdapter.xcframework.

Built and tested with:

• Google Mobile Ads SDK version 11.0.1.
• FiveAd SDK version 2.7.20240214.

Version 2.7.20240214.0

• Verified compatibility with FiveAd SDK version 2.7.20240214.

Built and tested with:

• Google Mobile Ads SDK version 11.0.1.
• FiveAd SDK version 2.7.20240214.

Version 2.7.20240126.0

• Verified compatibility with FiveAd SDK version 2.7.20240126.
• Updated the adapter implementation with FiveAd SDK new delegate protocols.

Built and tested with:

• Google Mobile Ads SDK version 10.14.0.
• FiveAd SDK version 2.7.20240126.

Version 2.7.20231115.0

• Verified compatibility with FiveAd SDK version 2.7.20231115.
• Included GADMediationAdapterLineExtras header in the modulemap.

Built and tested with:

• Google Mobile Ads SDK version 10.14.0.
• FiveAd SDK version 2.7.20231115.

Version 2.6.20230609.1

• Added GADMediationAdapterLineAudioState to manage the initial audio state of the banner, interstitial, and rewarded ad when it is first displayed.

Built and tested with:

• Google Mobile Ads SDK version 10.14.0.
• FiveAd SDK version 2.6.20230609.

Version 2.6.20230609.0

• Initial release!
• Added waterfall support for banner, interstitial, rewarded, and native ad formats.
• Verified compatibility with FiveAd SDK version 2.6.20230609.

Built and tested with:

• Google Mobile Ads SDK version 10.9.0.
• FiveAd SDK version 2.6.20230609.