This guide shows you how to use Google Mobile Ads SDK (Legacy) to load and display ads from LY Ads Network using [AdMob Mediation](https://developers.google.com/admob/android/mediation.md.txt), covering waterfall integrations. It covers how to add LY Ads Network to an ad unit's mediation configuration, and how to integrate the LY Ads Network SDK and adapter into an Android app. ## Supported integrations and ad formats The mediation adapter for LY Ads Network has the following capabilities: | Integration || |---|---| | Bidding | Yes | | Waterfall | Yes | | Banner | Yes | | Interstitial | Yes | | Rewarded | Yes | | Native | Yes | ## Prerequisites Before you continue, verify the following: - Android API level 24 or later. - Latest Google Mobile Ads SDK (Legacy) version. - [Set up AdMob Mediation](https://developers.google.com/admob/android/mediation.md.txt). ## Step 1: Set up configurations in LY Ads Network UI [Sign up and log in](https://adsnetwork.line.biz/) to your LY Ads Network account. ### Add a new application Navigate to the **App** tab and click the **New registration** button. ![New Registration](https://developers.google.com/static/admob/images/mediation/line/new-registration.png) Fill out the form and click **registration**. ![New Registration Form](https://developers.google.com/static/admob/images/mediation/line/new-registration-form.png) Take note of the **App ID**. ![Registration Details](https://developers.google.com/static/admob/images/mediation/line/registration-details-Android.png) ### Create an ad slot On the **App** tab, select your app to view your app's details. Under the **Slot** section, click **Add**. ![Add Slot](https://developers.google.com/static/admob/images/mediation/line/add-slot.png) Fill out the form for details about the slot. For **Bidding Type** , select **Standard** to configure this slot for waterfall mediation, or **Google SDK Bidding** to configure this slot for Bidding. Click **Create** once the form is filled. > [!NOTE] > **Note:** The **Advertising format** and **Bidding Type** cannot be changed after registering the slot. Reach out to your LY Ads Network account manager to get access to create native ad placements in the LY Ads Network UI. ![Add Slot Form](https://developers.google.com/static/admob/images/mediation/line/add-slot-form.png) Take note of the **Slot ID**. ![Slot Details](https://developers.google.com/static/admob/images/mediation/line/slot-details.png) After you create your first slot, click **Review** on your app's detail page to get approval from LY Ads Network. This may take some time. Contact your LY Ads Network representative if you have any questions. ![Request Review](https://developers.google.com/static/admob/images/mediation/line/request-review.png) ### Create a Reporting API Key Navigate to the **Managing reporting API keys** tab and click the **Create API key** button. ![Reporting API Key Tab](https://developers.google.com/static/admob/images/mediation/line/reporting_api_key.png) Fill out the form and click **Save**. ![Reporting API Key Form](https://developers.google.com/static/admob/images/mediation/line/reporting_api_key_form.png) Take note of your **API Key ID** and **API Key Secret**. ![Reporting API Key Form](https://developers.google.com/static/admob/images/mediation/line/reporting_api_key_details.png) ### Update your app-ads.txt [Authorized Sellers for Apps app-ads.txt](https://iabtechlab.com/wp-content/uploads/2019/03/app-ads.txt-v1.0-final-.pdf) is an IAB Tech Lab initiative that helps ensure your app ad inventory is only sold through channels you've identified as authorized. To prevent a significant loss in ad revenue, you'll need to implement an `app-ads.txt` file. If you haven't done so already, [set up an app-ads.txt file for your app](https://support.google.com/admob/answer/9363762). To implement `app-ads.txt` for LY Ads Network, see [About app-ads.txt](https://adsnetwork-docs.linebiz.com/fivesdk-android/store-release/app-ads-txt.html). ## Step 2: Set up LY Ads Network demand in AdMob UI ### Configure mediation settings for your ad unit You need to add LY Ads Network to the mediation configuration for your ad unit. First, sign in to your [AdMob account](https://apps.admob.com/). 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 LY Ads Network as an ad source](https://developers.google.com/admob/android/mediation/line.md.txt#add-ad-source). To create a new mediation group, select **Create Mediation Group**. ![](https://developers.google.com/static/admob/images/mediation/admob-mediation-group-create.png) Enter your ad format and platform, then click **Continue**. ![](https://developers.google.com/static/admob/images/mediation/admob-mediation-group-new-Android.png) 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**. ![](https://developers.google.com/static/admob/images/mediation/admob-mediation-group-details-Android.png) Associate this mediation group with one or more of your existing AdMob ad units. Then click **Done**. ![](https://developers.google.com/static/admob/images/mediation/admob-ad-units-select-Android.png) You should now see the ad units card populated with the ad units you selected: ![](https://developers.google.com/static/admob/images/mediation/admob-ad-units-card-Android.png) ### Add LY Ads Network as an ad source ### Bidding
In the **Ad Sources** section, find the **Bidding** card and select **Add ad source** . Then select **LY Ads Network** . Click **How to sign a partnership agreement** and [set up a bidding partnership](https://support.google.com/admob/answer/9842838) with LY Ads Network. ![](https://developers.google.com/static/admob/images/mediation/line/bidding-agreement-1.png) Click **Acknowledge \& agree** , then click **Continue** . ![](https://developers.google.com/static/admob/images/mediation/line/bidding-agreement-2.png) If you already have a mapping for LY Ads Network, you can select it. Otherwise, click **Add mapping** . ![](https://developers.google.com/static/admob/images/mediation/line/bidding-add-mapping-1-Android.png) Next, enter the **Application ID** and **Slot ID** obtained in the previous section. Then click **Done** . **Important** : The **Application ID** must be associated with the targeted app as in the LY Ads Network UI. ![](https://developers.google.com/static/admob/images/mediation/line/bidding-add-mapping-2-Android.png) ### Waterfall
Under the **Waterfall** card in the **Ad Sources** section, select **Add Ad Source** . Select **LY Ads Network** and enable the **Optimize** switch. Enter the **API Key ID** and **API Key Secret** obtained in the previous section to set up ad source optimization for LY Ads Network. Then enter an **eCPM value** for LY Ads Network and click **Continue** . ![](https://developers.google.com/static/admob/images/mediation/line/admob-add-ad-network.png) > [!NOTE] > **Note**: You only need to set up ad source optimization once per network.
If you already have a mapping for LY Ads Network, you can select it. Otherwise, click **Add mapping** . ![](https://developers.google.com/static/admob/images/mediation/line/waterfall-add-mapping-1-Android.png) Next, enter the **Application ID** and **Slot ID** obtained in the previous section. Then click **Done** . **Important** : The **Application ID** must be associated with the targeted app as in the LY Ads Network UI. ![](https://developers.google.com/static/admob/images/mediation/line/waterfall-add-mapping-2-Android.png) > [!NOTE] > **Note** : Ad source optimization takes a few days to gather enough data to accurately calculate eCPM for a mediation network. In the meantime, the ad source optimization status is `PENDING`, so you must manually set an eCPM value for the network. Once the eCPM can be calculated, the ad source automatically starts updating the eCPM on your behalf. ## Step 3: Import the LY Ads Network SDK and Adapter > [!NOTE] > **Note:** Failure to integrate the compatible LY Ads Network and Google Mobile Ads SDK (Legacy) versions might lead to build issues. ### Android Studio integration (recommended) In your app-level gradle file, add the following implementation dependencies: ### Kotlin ```kotlin dependencies { implementation("com.google.android.gms:play-services-ads:25.5.0") implementation("com.google.ads.mediation:line:3.2.0.0") } ``` ### Groovy ```groovy dependencies { implementation 'com.google.android.gms:play-services-ads:25.5.0' implementation 'com.google.ads.mediation:line:3.2.0.0' } ``` ### Manual integration 1. Download the latest version of the [LY Ads Network SDK](https://mvnrepository.com/artifact/com.linecorp.adsnetwork/fivead)'s `.aar` file and add it to your project. 2. Navigate to the [LY Ads Network adapter artifacts](https://maven.google.com/web/index.html#com.google.ads.mediation:line) on Google's Maven Repository. Select the latest version, download the LY Ads Network adapter's `.aar` file, and add it to your project. ## Step 4: Add required code No additional code is required for LY Ads Network integration. ## Step 5: Test your implementation ### Enable test ads Make sure you [register your test device](https://developers.google.com/admob/android/test-ads.md.txt#enable_test_devices) for AdMob. The LY Ads Network adapter contains a helper method to enable test mode for LY Ads Network. You must set this option before you [initialize Google Mobile Ads SDK (Legacy)](https://developers.google.com/admob/android/quick-start.md.txt#initialize_the_mobile_ads_sdk) to ensure they get forwarded properly to the LY Ads Network SDK. ### Java ```java LineMediationAdapter.Companion.setTestMode(true); ``` ### Kotlin ```kotlin LineMediationAdapter.setTestMode(true) ``` > [!IMPORTANT] > **Important:** Disable test mode for AdMob and LY Ads Network before releasing your app. ### Verify test ads To verify that you are receiving test ads from LY Ads Network, enable [single ad source testing](https://developers.google.com/admob/android/ad-inspector.md.txt#single_ad_source_testing) in ad inspector using the **LY Ads Network** ad source(s). ## Optional steps ### Network-specific parameters The LY Ads Network 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 ```java LineExtras lineExtras = new LineExtras(/* enableAdSound: */ true); Bundle extras = lineExtras.build(); AdRequest request = new AdRequest.Builder().addNetworkExtrasBundle(LineMediationAdapter.class, extras).build(); ```
### Kotlin ```kotlin val lineExtras = LineExtras(enableAdSound = true) val extras = lineExtras.build() val request = AdRequest.Builder().addNetworkExtrasBundle(LineMediationAdapter::class.java, extras).build() ```
### Using native ads #### Ad rendering The LY Ads Network adapter populates the following [Native ads advanced field descriptions](https://support.google.com/admob/answer/6240809) for a [`NativeAd`](https://developers.google.com/admob/android/reference/com/google/android/gms/ads/nativead/NativeAd.md.txt). | Field | Assets always included by LY Ads Network adapter | |---|---| | Headline | Yes | | Image | Yes | | Body | Yes | | App icon | ^[1](https://developers.google.com/admob/android/mediation/line.md.txt#app-icon-footnote)^ | | Call to action | Yes | | Star rating | | | Store | | | Price | | ^1^ For native ads, the LY Ads Network SDK does not provide an app icon asset. Instead, the LY Ads Network adapter populates the app icon with a transparent image. ## Error codes If the adapter fails to receive an ad from LY Ads Network, you can check the underlying error from the ad response using [`ResponseInfo.getAdapterResponses()`](https://developers.google.com/admob/android/reference/com/google/android/gms/ads/ResponseInfo.md.txt#getAdapterResponses()) under the following classes: ```java com.line.ads com.google.ads.mediation.line.LineMediationAdapter ``` Here are the codes and accompanying messages thrown by the LY Ads Network adapter when an ad fails to load: | Error code | Domain | Reason | |---|---|---| | 1-10 | com.five_corp.ad | LY Ads Network SDK returned an SDK-specific error. See LY Ads Network's [documentation](https://adsnetwork-docs.linebiz.com/fivesdk-android/trouble-shooting/quick-diagnosis.html) 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 LY Ads Network 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 | LY Ads Network 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. | | 107 | com.google.ads.mediation.line | FiveAd SDK returned a null ad loader. | ## LINE Android Mediation Adapter Changelog #### Next Version - Updated the adapter to use the `InitializationCompleteCallback.onInitializationFailed(AdError)` API. #### Version 3.2.0.0 - Verified compatibility with FiveAd SDK version 3.2.0.0. Built and tested with: - Google Mobile Ads SDK version 25.5.0. - Google Mobile Ads Next-Gen SDK version 1.6.0. - FiveAd SDK version 3.2.0.0. #### Version 3.1.1.2 - Pin the adapter's Kotlin dependency to 1.9.0 (the min Kotlin version supported by GMA NextGen SDK). Built and tested with: - Google Mobile Ads SDK version 25.4.0. - Google Mobile Ads Next-Gen SDK version 1.4.0. - FiveAd SDK version 3.1.1.1. #### Version 3.1.1.1 - Maps `AgeRestrictedTreatment` to Line's ChildDirectedTreatment API. Built and tested with: - Google Mobile Ads SDK version 25.4.0. - Google Mobile Ads Next-Gen SDK version 1.2.1. - FiveAd SDK version 3.1.1.1. #### Version 3.1.1.0 - Verified compatibility with FiveAd SDK version 3.1.1.0. Built and tested with: - Google Mobile Ads SDK version 25.2.0. - Google Mobile Ads Next-Gen SDK version 1.2.1. - FiveAd SDK version 3.1.1.0. #### Version 3.1.0.0 - Added property to build the adapter with GMA Next-Gen SDK dependency. - Verified compatibility with FiveAd SDK version 3.1.0.0. Built and tested with: - Google Mobile Ads SDK version 25.1.0. - Google Mobile Ads Next-Gen SDK version 0.25.0-beta01. - FiveAd SDK version 3.1.0.0. #### Version 3.0.1.2 Built and tested with: - Google Mobile Ads SDK version 25.1.0. - FiveAd SDK version 3.0.1.2. #### Version 3.0.1.1 - Native ad impressions are now overwritten by FiveAd SDK when using Google Mobile Ads SDK v24.4.0 or above. Built and tested with: - Google Mobile Ads SDK version 24.9.0. - FiveAd SDK version 3.0.1.1. #### Version 3.0.1.0 - Added support for forwarding the tagForUnderAgeOfConsent Google Mobile Ads SDK parameter to the FiveAd SDK. - Verified compatibility with FiveAd SDK version 3.0.1.0. Built and tested with: - Google Mobile Ads SDK version 24.9.0. - FiveAd SDK version 3.0.1.0. #### Version 3.0.0.0 - Verified compatibility with FiveAd SDK version 3.0.0.0. Built and tested with: - Google Mobile Ads SDK version 24.9.0. - FiveAd SDK version 3.0.0.0. #### Version 2.9.20251028.0 - Verified compatibility with FiveAd SDK version 2.9.20251028. Built and tested with: - Google Mobile Ads SDK version 24.7.0. - FiveAd SDK version 2.9.20251028.0 #### Version 2.9.20250924.1 - Removed class-level references to Context. Can help reduce memory leak issues. Built and tested with: - Google Mobile Ads SDK version 24.7.0. - FiveAd SDK version 2.9.20250924.1. #### Version 2.9.20250924.0 - Verified compatibility with FiveAd SDK version 2.9.20250924. Built and tested with: - Google Mobile Ads SDK version 24.6.0. - FiveAd SDK version 2.9.20250924.0 #### Version 2.9.20250718.0 - Verified compatibility with FiveAd SDK version 2.9.20250718. Built and tested with: - Google Mobile Ads SDK version 24.3.0. - FiveAd SDK version 2.9.20250718.0. #### Version 2.9.20250519.0 - Verified compatibility with FiveAd SDK version 2.9.20250519. Built and tested with: - Google Mobile Ads SDK version 24.3.0. - FiveAd SDK version 2.9.20250519.0. #### Version 2.9.20250317.1 - Fixes banner loading dimensions for bidding ads with new FiveAd API Built and tested with: - Google Mobile Ads SDK version 24.1.0. - FiveAd SDK version 2.9.20250317.0 #### Version 2.9.20250317.0 - Verified compatibility with FiveAd SDK version 2.9.20250317. Built and tested with: - Google Mobile Ads SDK version 24.1.0. - FiveAd SDK version 2.9.20250317.0 #### Version 2.9.20250110.1 - Updated the minimum required Android API level to 23. - Updated the minimum required Google Mobile Ads SDK version to 24.0.0. Built and tested with: - Google Mobile Ads SDK version 24.0.0. - FiveAd SDK version 2.9.20250110.0 #### Version 2.9.20250110.0 - Removed deprecated `UnifiedNativeAdMapper` class in favor of `NativeAdMapper` - Fixed signals collection process. - Fixed initialization process for waterfall interstitial and rewarded ad formats. - Verified compatibility with FiveAd SDK version 2.9.20250110. Built and tested with: - Google Mobile Ads SDK version 23.6.0. - FiveAd SDK version 2.9.20250110.0 #### Version 2.9.20241129.0 - Added bidding support for banner, interstitial, rewarded and native ad formats. - Verified compatibility with FiveAd SDK version 2.9.20241129. Built and tested with: - Google Mobile Ads SDK version 23.5.0. - FiveAd SDK version 2.9.20241129.0 #### Version 2.8.20240827.0 - Verified compatibility with FiveAd SDK version 2.8.20240827. 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. 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. 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. 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. 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. 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. 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.