Integrating nend with Mediation

This guide is for publishers who want to use the Google Mobile Ads SDK to load and display ads from nend via mediation. It explains how to add nend to an ad unit's mediation configuration, how to set up ad network optimization, and how to integrate the nend SDK and adapter into an iOS 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 this guide, labels and buttons are referred to by their English equivalents. "URL スキーム," for example, is "URL Scheme," and so on.

Supported formats and features

The AdMob mediation adapter for nend has the following capabilities:

Formats
Banners
Interstitials
Rewarded Video
Rewarded Video (new APIs)
Native
Features
Smart Banners
Ad Network Optimization (ANO)
Native Video

Requirements

  • iOS deployment target of 8.1 or higher
  • Latest Google Mobile Ads SDK

Step 1: Set up nend

Sign up or sign in to your nend account.

To add your application to the nend dashboard, first click on 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 iOS application as the application type. Enter the URL and check if your app is in the 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.

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

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 on 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 your desired 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 your desired 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 Video

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 your desired 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 your desired 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 your desired 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: Configure mediation settings for your AdMob ad unit

Next, you need to add nend to the mediation configuration for your ad unit. First, sign in to your AdMob account.

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 nend 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. Then click Add Ad Units.

Mediation group 2

Associate this mediation group with one or more of your existing AdMob ad units. Then click Done.

Select ad unit

You should now see the ad units card populated with the ad units you selected, as shown below:

Group ad units

Add nend as an ad source

In the Ad Sources card, select Add Ad Network.

Select nend and enable the Optimize switch. Enter your API Key for Scraping obtained from nend earlier as the Reporting API Key to set up ANO for nend. Then enter an eCPM value for nend and click Continue.

Enter the Spot ID and the API Key obtained in the previous section and click Done.

Using rewarded video ads

In the settings for your rewarded video ad unit, provide values for the reward amount and reward type. Then, to ensure you provide the same reward to the user no matter which ad network is served, check the Apply to all networks in Mediation groups box.

If you don't apply this setting, the nend adapter passes back the reward specified in the nend dashboard.

For more information on setting reward values for AdMob ad units, see Create an ad unit.

Step 3: Import the nend SDK and adapter

  • Add the following line to your project's Podfile:

    pod 'GoogleMobileAdsMediationNend'
    
  • From the command line run:

    pod install --repo-update

Manual integration

Download the latest version of the nend iOS SDK, and link nendSDK.framework in your project. Download NendAdapter and link NendAdapter.framework in your project.

Add the following frameworks to your project:

  • AdSupport.framework
  • Security.framework
  • ImageIO.framework
  • AVFoundation.framework
  • CoreMedia.framework
  • SystemConfiguration.framework
  • WebKit.framework

In addition, by adding the following frameworks, it becomes possible to use detailed information by ad delivery.

  • CoreLocation.framework
  • CoreMotion.framework
  • CoreTelephony.framework

Step 4: Additional code required

No additional code is required for nend integration.

Project settings

Add the -ObjC flag to the Other Linker Flags under Application Target > Build Settings.

Step 5: Test your implementation

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.

Optional steps

Network-specific parameters

The nend adapter supports additional request parameters, which can be passed to the adapter using the GADMAdapterNendExtras class.

  • userId - Sets the UserID of specific nend interstitial ad.
  • interstitialType - Nend provides the option of selecting either TYPE_NORMAL for regular insterstitial ads or TYPE_VIDEO for interstitial video ads.

Here are examples of how to set these ad request parameters:

Swift

let request = GADRequest()
let extras = GADMAdapterNendExtras()
extras.userId = "12345"
extras.interstitialType = GADMNendInterstitialTypeNormal
request.registerAdNetworkExtras(extras)

Objective-C

GADRequest *request = [GADRequest request];
GADMAdapterNendExtras *extras = [[GADMAdapterNendExtras alloc] init];
extras.userId = @"12345";
extras.interstitialType = GADMNendInterstitialTypeNormal;
[request registerAdNetworkExtras:extras];

Ad rendering

The Nend adapter returns its native ads as UnifiedNativeAd objects. It populates the following Native ads advanced field descriptions for a GADUnifiedNativeAd.

Field Populated by the Nend adapter
Headline
Image 1
Body
App icon 2
Call to action
Advertiser Name
Star rating
Store
Price

1 Nend only provides an Image asset for native placements configured with an Ad image selection set to Horizontal (5: 3) large advertising image.

2 Nend does not provide an Icon asset for native placements configured with an Ad image selection set to No image (text only).

nend iOS Mediation Adapter Changelog

Version 6.0.3.0

  • Verified compatibility with nend SDK 6.0.3.
  • Updated the minimum required Google Mobile Ads SDK version to 7.65.0.

Built and tested with

  • Google Mobile Ads SDK version 7.65.0.
  • Nend SDK version 6.0.3.

Version 6.0.2.0

  • Verified compatibility with nend SDK 6.0.2.
  • Updated the minimum required Google Mobile Ads SDK version to 7.64.0.

Built and tested with

  • Google Mobile Ads SDK version 7.64.0.
  • Nend SDK version 6.0.2.

Version 6.0.1.0

  • Verified compatibility with nend SDK 6.0.1.

Built and tested with

  • Google Mobile Ads SDK version 7.62.0.
  • Nend SDK version 6.0.1.

Version 6.0.0.0

  • Verified compatibility with nend SDK 6.0.0.
  • Removed the GADNendRewardedNetworkExtras class. If you want to pass network extras to the nend iOS adapter, please use the GADMAdapterNendExtras class.
  • Renamed the following enums from the GADMAdapterNendExtras class:
    • GADMNendInterstitialType to GADMAdapterNendInterstitialType.
    • GADMNendNativeType to GADMAdapterNendNativeType.
  • Updated the minimum required Google Mobile Ads SDK version to 7.62.0.

Built and tested with

  • Google Mobile Ads SDK version 7.62.0.
  • Nend SDK version 6.0.0.

Version 5.4.1.0

  • Verified compatibility with nend SDK 5.4.1.
  • Added support for native ads.
  • Removed support for the i386 architecture.

Built and tested with

  • Google Mobile Ads SDK version 7.58.0.
  • Nend SDK version 5.4.1.

Version 5.3.1.0

  • Verified compatibility with nend SDK 5.3.1.

Build and tested with

  • Google Mobile Ads SDK version 7.52.0.
  • Nend SDK version 5.3.1.

Version 5.3.0.0

  • Verified compatibility with nend SDK 5.3.0.

Built and tested with:

  • Google Mobile Ads SDK version 7.50.0.
  • Nend SDK version 5.3.0.

Version 5.1.1.0

  • Updated the adapter to use the new rewarded API.
  • Now requires Google Mobile Ads SDK version 7.42.2 or higher.
  • Verified compatibility with nend SDK 5.1.1.
  • Changed condition that checking banner size. Appropriate size for SmartBanner
    • kGADAdSizeSmartBannerPortrait
      • iPhone: 320×50
      • iPad: 728×90 or 320×50
    • kGADAdSizeSmartBannerLandscape
      • iPad: 728×90 or 320×50
  • Added support for flexible banner ad sizes.

Version 5.1.0.0

  • Verified compatibility with nend SDK 5.1.0.

Version 5.0.3.0

  • Verified compatibility with nend SDK 5.0.3.

Version 5.0.2.0

  • Verified compatibility with nend SDK 5.0.2.

Version 5.0.1.0

  • Verified compatibility with nend SDK 5.0.1.

Version 5.0.0.0

  • Verified compatibility with nend SDK 5.0.0.

Version 4.0.6.0

  • Verified compatibility with nend SDK 4.0.6.
  • Remove to set userFeature property.

Version 4.0.5.0

  • Verified compatibility with nend SDK 4.0.5.

Version 4.0.4.0

  • Verified compatibility with nend SDK 4.0.4.

Version 4.0.3.0

  • Verified compatibility with nend SDK 4.0.3.

Version 4.0.2.0

  • First release in Google Mobile Ads mediation open source project.
  • Added support for reward-based video ads.

Previous Versions

  • Supports banner and interstitial ads.