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 19 or higher
- To deploy on iOS
- iOS deployment target of 11.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 the myTarget network
First, sign up or log in to your myTarget account. Navigate to the Apps page by clicking on APPS in 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
Provide the Google Play Store URL for your app.
iOS
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.
Banner
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.
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. The 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.
Step 2: Configure mediation settings for your AdMob ad unit
You need to add myTarget to the mediation configuration for your AdMob ad units. First sign into your AdMob account.
If you're deploying your Unity app to both Android and iOS, you need two AdMob ad units, one for each platform.
Android
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 myTarget 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, and then click Add Ad Units.
Associate this mediation group with one or more of your existing AdMob ad units. Then, click Done.
You should now see the ad units card populated with the ad units you selected as shown below:
Add myTarget as an ad source
In the Ad Sources card, select Add Ad Network.
Select myTarget as the ad network, enable the Optimize switch, enter the Permanent Access Token obtained in the previous section and enter an eCPM value for myTarget to set up ad source optimization for myTarget. Then, click Continue.
If you already have a mapping for myTarget, you can simply select it. Otherwise, click Add mapping.
Next, enter a Mapping name and the Slot ID obtained in the previous section. Then click Done.
iOS
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 myTarget 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, and then click Add Ad Units.
Associate this mediation group with one or more of your existing AdMob ad units. Then, click Done.
You should now see the ad units card populated with the ad units you selected as shown below:
Add myTarget as an ad source
In the Ad Sources card, select Add Ad Network.
Select myTarget as the ad network, enable the Optimize switch, enter the Permanent Access Token obtained in the previous section and enter an eCPM value for myTarget to set up ad source optimization for myTarget. Then, click Continue.
If you already have a mapping for myTarget, you can simply select it. Otherwise, click Add mapping.
Next, enter a Mapping name and the Slot ID obtained in the previous section. Then click Done.
Rewarded ads
In the settings for your rewarded ad unit, check the Apply to all networks in Mediation groups box so that you provide the same reward to the user no matter which ad network is served.
For more information on setting reward values for AdMob ad units, see Create an ad unit.
Step 3: Import the myTarget SDK and adapter
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.
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: Additional code required
No additional code is required for myTarget integration.
Step 5: Test your implementation
When testing, myTarget recommends using the Slot IDs from its open source example apps (Android | iOS) to request ads. These can be entered as the Slot ID for your AdMob ad units for testing purposes, and then replaced with an actual Slot ID when your app is ready for production.
Optional steps
EU Consent and GDPR
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.
Add Mail.ru to GDPR ad partners list
Follow the steps in GDPR settings to add Mail.ru to the GDPR ad partners list in the AdMob UI.
CCPA
The California Consumer Privacy Act (CCPA) requires giving California state residents 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 CCPA preparation 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 with CCPA.
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.
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 AdMob 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 AdMob 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.13.1
- Moved adapter content to
GoogleMobileAds/Mediation/MyTarget/
. - Refactored adapter namespace to use
GoogleMobileAds.Mediation.MyTarget
. - Supports myTarget Android adapter version 5.16.4.1.
- Supports myTarget iOS adapter version 5.17.4.0.
- Built and tested with the Google Mobile Ads Unity Plugin version 8.1.0.
Version 3.13.0
- Supports myTarget Android adapter version 5.16.4.0.
- Supports myTarget iOS adapter version 5.17.4.0.
- Built and tested with the Google Mobile Ads Unity Plugin version 8.0.0.
Version 3.12.0
- Supports myTarget Android adapter version 5.15.5.0.
- Supports myTarget iOS adapter version 5.16.0.0.
- Built and tested with the Google Mobile Ads Unity Plugin version 7.3.0.
Version 3.11.4
- Supports myTarget Android adapter version 5.15.4.0.
- Supports myTarget iOS adapter version 5.15.2.0.
- Built and tested with the Google Mobile Ads Unity Plugin version 7.2.0.
Version 3.11.3
- Renamed the
IsConsent()
method from theMyTarget
class toGetUserConsent()
. - Added the following methods to the
MyTarget
class:SetCCPAUserConsent(bool)
GetCCPAUserConsent()
- Supports myTarget Android adapter version 5.15.3.0.
- Supports myTarget iOS adapter version 5.15.2.0.
- Built and tested with the Google Mobile Ads Unity Plugin version 7.2.0.
Version 3.11.2
- Supports myTarget Android adapter version 5.15.2.1.
- Supports myTarget iOS adapter version 5.15.2.0.
- Built and tested with the Google Mobile Ads Unity Plugin version 7.0.2.
Version 3.11.1
- Supports myTarget Android adapter version 5.15.1.0.
- Supports myTarget iOS adapter version 5.15.1.0.
- Built and tested with the Google Mobile Ads Unity Plugin version 7.0.0.
Version 3.11.0
- Supports myTarget Android adapter version 5.15.0.0.
- Supports myTarget iOS adapter version 5.15.0.1.
- Built and tested with the Google Mobile Ads Unity Plugin version 7.0.0.
Version 3.10.2
- Supports myTarget Android adapter version 5.14.4.0.
- Supports myTarget iOS adapter version 5.14.4.0.
Version 3.10.1
- Supports myTarget Android adapter version 5.14.3.0.
- Supports myTarget iOS adapter version 5.14.2.0.
Version 3.10.0
- Supports myTarget Android adapter version 5.14.2.0.
- Supports myTarget iOS adapter version 5.14.1.0.
Version 3.9.0
- Supports myTarget Android adapter version 5.13.0.0.
- Supports myTarget iOS adapter version 5.11.2.0.
Version 3.8.2
- Supports myTarget Android adapter version 5.11.7.0.
- Supports myTarget iOS adapter version 5.9.10.0.
Version 3.8.1
- Supports myTarget Android adapter version 5.11.5.0.
- Supports myTarget iOS adapter version 5.9.6.0.
Version 3.8.0
- Supports myTarget Android adapter version 5.11.4.0.
- Supports myTarget iOS adapter version 5.9.5.0.
Version 3.7.0
- Supports myTarget Android adapter version 5.10.0.0.
- Supports myTarget iOS adapter version 5.7.5.0.
Version 3.6.1
- Renamed the
MyTarget.IsUserConsent()
method toMyTarget.IsConsent()
. - Supports myTarget Android adapter version 5.9.1.0.
- Supports myTarget iOS adapter version 5.7.2.0.
Version 3.6.0
- Supports myTarget Android adapter version 5.9.0.0.
- Supports myTarget iOS adapter version 5.7.0.0.
Version 3.5.2
- Supports myTarget Android adapter version 5.8.3.0.
- Supports myTarget iOS adapter version 5.6.3.0.
Version 3.5.1
- Supports myTarget Android adapter version 5.8.2.0.
- Supports myTarget iOS adapter version 5.6.1.0.
Version 3.5.0
- Supports myTarget Android adapter version 5.8.1.0.
- Supports myTarget iOS adapter version 5.6.0.0.
Version 3.4.0
- Supports myTarget Android adapter version 5.8.0.0.
- Supports myTarget iOS adapter version 5.5.2.0.
Version 3.3.0
- Supports myTarget Android adapter version 5.7.0.0.
- Supports myTarget iOS adapter version 5.5.1.0.
Version 3.2.0
- Supports myTarget Android adapter version 5.6.3.0.
- Supports myTarget iOS adapter version 5.4.9.0.
Version 3.1.0
- Supports myTarget Android adapter version 5.4.6.0.
- Supports myTarget iOS adapter version 5.3.3.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.