Integrate myTarget with mediation

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

Supported integrations and ad formats

Integration
Bidding
Waterfall
Formats
Banner
Interstitial
Rewarded
Rewarded Interstitial

Requirements

  • Unity 4 or higher
  • Latest Google Mobile Ads SDK
  • To deploy on Android
    • Android API level 21 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 myTarget UI

First, sign up or log in to your myTarget account. Navigate to the Apps page by clicking on APPS on the header. Add your app by clicking ADD APP.

If your app supports both the Android and iOS platforms, you need to set up each one of them separately.

Android

Next, provide the Google Play URL for your app.

iOS

Next, provide the iTunes URL** for your app.

When adding an app, myTarget requires you to create an ad unit before you can complete the process.

Select BANNER from the available ad formats, and then click the ADD AD UNIT button.

Interstitial

Select INTERSTITIAL from the available ad formats, and then click the ADD AD UNIT button.

Rewarded

Select REWARDED VIDEO from the available ad formats, and then click the ADD AD UNIT button.

Native

Select NATIVE from the available ad formats, and then click on ADD AD UNIT.

In your ad unit's details page, make a note of your slot ID which can be found under the ad unit settings as slot_id. This slot ID will be used to set up your AdMob ad unit in the next section.

In addition to the slot_id, you'll also need your myTarget Permanent Access Token to set up your AdMob ad unit ID. Navigate to the Profile tab and select Access Tokens. Click Create Token or Show Token to view your myTarget Permanent Access Token.

Turn on test mode

Follow the instructions in myTarget's documentation to add and configure a test device in myTarget UI.

Step 2: Set up myTarget demand in Ad Manager 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.

Add Mail.ru to GDPR and US state regulations ad partners list

Follow the steps in GDPR settings and US state regulations settings to add Mail.ru to the GDPR and US state regulations ad partners list in the AdMob UI.

Step 3: Import the myTarget SDK and adapter

OpenUPM-CLI

If you have OpenUPM-CLI installed, you can install the Google Mobile Ads myTarget Mediation Plugin for Unity to your project by running the following command from your project's root directory:

openupm add com.google.ads.mobile.mediation.mytarget

OpenUPM

In your Unity project editor, select Edit > Project Settings > Package Manager to open the Unity Package Manager Settings.

Under the Scoped Registries tab, add OpenUPM as a scoped registry with the following details:

  • Name: OpenUPM
  • URL: https://package.openupm.com
  • Scope(s): com.google

OpenUPM Details

Then, navigate to Window > Package Manager to open the Unity Package Manager and select My Registries from the drop-down menu.

Unity Registries

Select the Google Mobile Ads myTarget Mediation package and click Install.

Install from OpenUPM

Unity Package

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

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

Import from Unity

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

Force Resolve

Step 4: Implement privacy settings on myTarget SDK

Under the Google EU User Consent Policy, you must ensure that certain disclosures are given to, and consents obtained from, users in the European Economic Area (EEA) regarding the use of device identifiers and personal data. This policy reflects the requirements of the EU ePrivacy Directive and the General Data Protection Regulation (GDPR). When seeking consent, you must identify each ad network in your mediation chain that may collect, receive, or use personal data and provide information about each network's use. Google currently is unable to pass the user's consent choice to such networks automatically.

The Google Mobile Ads mediation plugin for myTarget version 2.1.0 includes the SetUserConsent() and SetUserAgeRestricted() methods. The following sample code shows how to pass user consent information to the myTarget SDK. If you choose to call this method, it is recommended that you do so prior to requesting ads through the Google Mobile Ads SDK.

using GoogleMobileAds.Api.Mediation.MyTarget;
// ...

MyTarget.SetUserConsent(true);

If the user is known to be in an age-restricted category, you can also call the SetUserAgeRestricted() method.

MyTarget.SetUserAgeRestricted(true);

See myTarget's Privacy and GDPR guide for more information.

US states privacy laws

U.S. states privacy laws require giving users the right to opt out of the "sale" of their "personal information" (as the law defines those terms), with the opt-out offered via a prominent "Do Not Sell My Personal Information" link on the "selling" party's homepage. The U.S. states privacy laws compliance guide offers the ability to enable restricted data processing for Google ad serving, but Google is unable to apply this setting to each ad network in your mediation chain. Therefore, you must identify each ad network in your mediation chain that may participate in the sale of personal information and follow guidance from each of those networks to ensure compliance.

The Google Mobile Ads mediation plugin for myTarget version 3.13.3 includes the SetCCPAUserConsent(bool) method. The following sample code shows how to pass user consent information to the myTarget SDK. If you choose to call this method, it is recommended that you do so prior to requesting ads through the Google Mobile Ads SDK.

using GoogleMobileAds.Api.Mediation.MyTarget;
// ...

MyTarget.SetCCPAUserConsent(true);

Contact myTarget support for more information.

Step 5: Add required code

Android

No additional code is required for myTarget integration.

iOS

SKAdNetwork integration

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

Step 6: Test your implementation

Enable test ads

Make sure you register your test device for AdMob and enable test mode in myTarget UI.

Verify test ads

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

Error codes

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

Android

com.google.ads.mediation.mytarget.MyTargetAdapter
com.google.ads.mediation.mytarget.MyTargetNativeAdapter
com.google.ads.mediation.mytarget.MyTargetRewardedAdapter

iOS

GADMAdapterMyTarget
GADMediationAdapterMyTargetNative
GADMediationAdapterMyTargetRewarded

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

Android

Error code Reason
100 myTarget SDK returned an error.
101 myTarget server parameters configured in the Ad Manager UI are missing/invalid.
102 The requested ad size does not match a myTarget supported banner size.
103 Ad request is not a Unified native ad request.
104 The loaded native ad from myTarget is different from the requested native ad.
105 The loaded native ad from myTarget is missing some required assets (e.g. image or icon).

iOS

Error code Reason
100 myTarget SDK does not yet have an ad available.
101 myTarget server parameters configured in the Ad Manager UI are missing/invalid.
102 myTarget Adapter does not support the ad format being requested.
103 Tried to show a myTarget ad that is not loaded.
104 The requested ad size does not match a myTarget supported banner size.
105 Missing required native ad assets.

myTarget Unity Mediation Plugin Changelog

Version 3.19.0

Version 3.18.2

Version 3.18.1

Version 3.18.0

Version 3.17.1

Version 3.17.0

Version 3.16.2

Version 3.16.1

Version 3.16.0

Version 3.15.0

Version 3.14.0

Version 3.13.2

Version 3.13.1

Version 3.13.0

Version 3.12.0

Version 3.11.4

Version 3.11.3

Version 3.11.2

Version 3.11.1

Version 3.11.0

Version 3.10.2

Version 3.10.1

Version 3.10.0

Version 3.9.0

Version 3.8.2

Version 3.8.1

Version 3.8.0

Version 3.7.0

Version 3.6.1

Version 3.6.0

Version 3.5.2

Version 3.5.1

Version 3.5.0

Version 3.4.0

Version 3.3.0

Version 3.2.0

Version 3.1.0

Version 3.0.0

  • Updated the plugin to support the new open-beta Rewarded API.
  • Supports myTarget Android adapter version 5.3.9.0.
  • Supports myTarget iOS adapter version 5.0.4.0.

Version 2.3.2

  • Supports myTarget Android adapter version 5.2.5.0.
  • Supports myTarget iOS adapter version 4.8.9.0.

Version 2.3.1

  • Supports myTarget Android adapter version 5.2.5.0.
  • Supports myTarget iOS adapter version 4.8.5.0.

Version 2.3.0

  • Supports myTarget Android adapter version 5.2.2.0.
  • Supports myTarget iOS adapter version 4.8.0.0.

Version 2.2.0

  • Supports myTarget Android adapter version 5.1.4.0.
  • Supports myTarget iOS adapter version 4.8.0.0.

Version 2.1.2

  • Supports myTarget Android adapter version 5.1.3.0.
  • Supports myTarget iOS adapter version 4.7.11.0.

Version 2.1.1

  • Supports myTarget Android adapter version 5.1.1.0.
  • Supports myTarget iOS adapter version 4.7.10.0.

Version 2.1.0

  • Supports myTarget Android SDK version 5.1.0.
  • Supports myTarget iOS SDK version 4.7.9.
  • Added the following methods:
    • MyTarget.SetUserConsent() method to forward the user's consent status to the MyTarget SDK.
    • MyTarget.SetUserAgeRestricted method that sets a flag to indicate if the user is known to be in an age-restricted category (i.e., under the age of 16).
    • MyTarget.IsUserConsent() method to get the user's current consent status.
    • MyTarget.IsUserAgeRestricted() method to get the flag indicating that the user is known to be in an age-restricted category (i.e., under the age of 16).

Version 2.0.1

  • Supports myTarget Android SDK version 5.0.2.
  • Supports myTarget iOS SDK version 4.7.8.

Version 2.0.0

  • Supports myTarget Android SDK version 5.0.0.
  • Supports myTarget iOS SDK version 4.7.7.

Version 1.1.0

  • Supports myTarget Android SDK version 4.7.2.
  • Supports myTarget iOS SDK version 4.7.6.

Version 1.0.0

  • First release!
  • Supports myTarget Android SDK version 4.6.27.
  • Supports myTarget iOS SDK version 4.6.24.