Integrate nend with mediation

This guide shows you how to use the Google Mobile Ads SDK to load and display ads from nend using mediation, covering waterfall integrations. It covers how to add nend to an ad unit's mediation configuration, and how to integrate the nend SDK and adapter into a Unity app.

The dashboard interface for nend uses Japanese text for its labels, buttons, and descriptions, and the screenshots displayed below have not been translated. In the text of this guide however, labels and buttons are refererred to by their English names. "URL スキーム," for example, is "URL Scheme," and so on.

Supported integrations and ad formats

Integration
Bidding
Waterfall
Formats
Banner
Interstitial
Rewarded

Requirements

  • Unity 4 or higher
  • Latest Google Mobile Ads SDK
  • To deploy on Android
    • Android API level 19 or higher
  • To deploy on iOS
    • iOS deployment target of 12.0 or higher
  • A working Unity project configured with the Google Mobile Ads SDK. See Get Started for details.
  • Complete the mediation Get started guide

Step 1: Set up configurations in nend UI

Sign up or sign in to your nend account.

To add your application to the nend dashboard, first click the Placement Management tab, and then select Site/App. Click the Add an app button to add your app to nend.

Create an application

Enter the name of your app and choose your app platform as the application type. Enter the URL and check if your app is listed on the appropriate app store

(see nend's unreleased apps FAQ if your app has not yet been released). Select a category for your app and click Create when done.

Android

iOS

Your application will be shown on the dashboard once it is created.

Android

iOS

Create a placement

Once the app is registered, you can move on to creating a placement. To create a placement for banner ads, go to the Placement Management tab and click the Placement. Then click the Create a new placement button.

Select your app in the drop-down menu. Then, follow the instructions below that corresponds to your preferred ad format.

Choose Still image for the Ad type, and Banner for the Inventory type. Once that's done, enter a Placement Name, fill out the Introduction to inventory, choose an Inventory format, and finally choose an Inventory size. When finished, click the Create button to create your placement.

Interstitial

Choose Still image for the Ad type, and Interstitial for the Inventory type. Once that's done, enter a Placement Name, fill out the Introduction to inventory, and select an Ad display frequency from the drop-down list. When finished, click the Create button to create your placement.

For Interstitial video ads, choose Video for the Ad type, and Interstitial for the Inventory type. Once that's done, enter a Placement Name, fill out the Introduction to inventory, and choose an appropriate a Category from the drop-down list. When finished, click the Create button to create your placement.

Rewarded

Choose Video for the Ad type, and Reward for the Inventory type. Once that's done, enter a Placement Name, fill out the Introduction to inventory, and choose an appropriate a Category from the drop-down list.

Under Reward settings, select a Reward content using the drop-down list, enter your preferred Virtual currency name. When finished, click the Create button to create your placement.

Native

Choose Still image for the Ad type, and Native for the Inventory type. Once that's done, enter a Placement Name, fill out the Introduction to inventory, and select a Ad image selection. When finished, click the Create button to create your placement.

For Native video ads, choose Video for the Ad type, and Native (custom) for the Inventory type. Once that's done, enter a Placement Name, fill out the Introduction to inventory, and choose an appropriate a Category from the drop-down list.

Under Native settings, select a Video ad orientation and Native ad type from the list. When finished, click the Create button to create your placement.

To set up your AdMob ad unit in the next section, you'll need the apiKey and spotID for each placement. To locate them, head to the Placement Management tab and select the SDK button under the name of your app.

Take note of the apiKey and spotID.

You'll also need your API Key for nend's reporting API, which they call the API Key for Scraping. You can find it in the Tools tab.

Step 2: Set up nend demand in AdMob UI

Configure mediation settings for your ad unit

Android

For instructions, see step 2 in the guide for Android.

iOS

For instructions, see step 2 in the guide for iOS.

Step 3: Import the nend SDK and adapter

Download the latest version of Google Mobile Ads mediation plugin for nend from the download link in the Changelog and extract the GoogleMobileAdsNendMediation.unitypackage package from the zip file.

In your Unity project editor, select Assets > Import Package > Custom Package and find the GoogleMobileAdsNendMediation.unitypackage file you downloaded. Make sure that all the files are selected and click Import.

Then, select Assets > Play Services Resolver > Android Resolver > Force Resolve. The Unity Play Services Resolver library will perform dependency resolution from scratch and copy the declared dependencies into the Assets/Plugins/Android directory of your Unity app.

Step 4: Add required code

Android

No additional code is required for nend integration.

iOS

SKAdNetwork integration

Follow nend'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 AdMob. To get test ads for banners, interstitials, and rewarded, nend recommends using the API keys and Spot IDs provided in the nend test ad units page. These can be entered as the API Keys and Spot IDs for your AdMob ad units while testing, and then replaced with an actual API Key and Spot ID when your app is ready for production.

Verify test ads

To verify that you are receiving test ads from nend, enable single ad source testing in ad inspector using the nend (Waterfall) ad source(s).

Error codes

If the adapter fails to receive an ad from nend, publishers can check the underlying error from the ad response using ResponseInfo under the following classes:

Android

com.google.ads.mediation.nend.NendAdapter
com.google.ads.mediation.nend.NendRewardedAdapter
com.google.ads.mediation.nend.NendMediationAdapter

iOS

GADMAdapterNend
GADMAdapterNend
GADMAdapterNendRewarded
GADMediationAdapterNend

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

Android

Error code Domain Reason
101 com.google.ads.mediation.nend nend requires an activity context to load and show ads.
102 com.google.ads.mediation.nend nend server parameters configured in the AdMob UI are missing/invalid.
103 com.google.ads.mediation.nend nend ad is not yet ready to be shown.
104 com.google.ads.mediation.nend nend failed to play the ad.
105 com.google.ads.mediation.nend The requested ad size does not match a nend supported banner size.
106 com.google.ads.mediation.nend The Context object reference is null and/or was recently released from memory.
200-299 net.nend.android nend SDK returned an interstitial ad load error. See code for more details.
300-399 net.nend.android nend SDK returned an interstitial show ad error. See code for more details.
400-499 net.nend.android nend SDK returned an ad error. See code for more details.

iOS

Error code Domain Reason
101 com.google.mediation.nend nend SDK returned a load failure callback with no additional error information.
102 com.google.mediation.nend nend SDK returned a show failure callback with no additional error information.
103 com.google.mediation.nend nend server parameters configured in the AdMob UI are missing/invalid.
104 com.google.mediation.nend Failed to load native ads image assets.
105 com.google.mediation.nend Failed to show nend ads due to ad not ready.
106 com.google.mediation.nend The requested banner ad size does not match a nend supported banner size.
200-699 Sent by nend SDK. nend SDK returned an error. See nend's document for more details.

nend Unity Mediation Plugin Changelog

Version 8.0.0

Version 7.0.0

Version 6.0.1

Version 6.0.0

Version 5.2.0

Version 5.1.0

Version 5.0.0

Version 4.0.1

Version 4.0.0

Version 3.0.0

Version 2.3.0

Version 2.2.0

Version 2.1.0

  • Updated the plugin to support the new Rewarded API.
  • Supports nend Android adapter version 5.1.0.2.
  • Supports nend iOS adapter version 5.1.1.0.

Version 2.0.3

  • Supports nend Android adapter version 5.0.2.1.
  • Supports nend iOS adapter version 5.0.2.0.

Version 2.0.2

  • Supports nend Android adapter version 5.0.2.0.
  • Supports nend iOS adapter version 5.0.2.0.

Version 2.0.1

  • Supports nend Android adapter version 5.0.2.0.
  • Supports nend iOS adapter version 5.0.1.0.

Version 2.0.0

  • Supports nend Android adapter version 5.0.0.0.
  • Supports nend iOS adapter version 5.0.0.0.

Version 1.0.2

  • Supports nend Android adapter version 4.0.5.0.
  • Supports nend iOS adapter version 4.0.6.0.

Version 1.0.1

  • Supports nend Android SDK version 4.0.4.
  • Supports nend iOS SDK version 4.0.4.

Version 1.0.0

  • First release!
  • Supports nend Android SDK version 4.0.2.
  • Supports nend iOS SDK version 4.0.2.