Integrate myTarget with AdMob Mediation

This guide shows you how to use Google Mobile Ads SDK for React Native 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 React Native app.

Supported integrations and ad formats

Integration
Bidding
Waterfall
Formats
App Open
Banner
Interstitial
Rewarded
Rewarded Interstitial
Native

Prerequisites

Before you continue, verify the following:

Step 1: Set up configurations in myTarget UI

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.

Update your app-ads.txt

Authorized Sellers for Apps app-ads.txt 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.

To implement app-ads.txt for myTarget, see How to create and publish a file.

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 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.

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

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

Step 3: Import the myTarget SDK and adapter

In your project's root directory, install the Google Mobile Ads SDK for React Native mediation adapter for myTarget. Complete the following:

  1. Copy the Google Mobile Ads SDK for React Native adapter tar file from the gma-sdk-react-native/adapters/mytarget/ directory into your project's local_packages/ directory. If you don't have the adapters folder, see Prerequisites.

    mkdir -p local_packages
cp EXTRACT_DIR/gma-sdk-react-native/adapters/mytarget/gma-mediation-mytarget-0.1.0.tgz local_packages/

    Replace EXTRACT_DIR with the path to the directory where you extracted the archive.

  2. Install the adapter package using your preferred package manager:

    npm

    npm install ./local_packages/gma-mediation-mytarget-0.1.0.tgz

    yarn

    yarn add ./local_packages/gma-mediation-mytarget-0.1.0.tgz

Step 4: Implement privacy settings on myTarget SDK

To comply with the Google EU User Consent Policy, you must make certain disclosures to your users in the European Economic Area (EEA), the UK, and Switzerland, and obtain their consent for the use of cookies or other local storage where legally required, and for the collection, sharing, and use of personal data for ads personalization. This policy reflects the requirements of the EU ePrivacy Directive and the General Data Protection Regulation (GDPR). You are responsible for verifying that consent is propagated to each ad source in your mediation chain.

myTarget React Native adapter version N/A and later supports passing GDPR consent signals from UMP SDK and consent management platforms that integrate with Google's Additional Consent specification to myTarget SDK.

US states privacy laws

US 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 through a prominent "Do Not Sell My Personal Information" link on the "selling" party's homepage. The US 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.

See the US states privacy laws section in the Android and iOS developer guides.

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).

Optional steps

Network-specific parameters

The myTarget adapter supports passing a MyTargetMediationExtras object to the ad request to set network-specific parameters.

Use the isIosDebugMode parameter to enable or disable debug logging from the myTarget iOS adapter. The underlying iOS adapter enables logging by default. For more information, see the iOS network-specific parameters guide.

The following sample code shows how to set isIosDebugMode:

import { MyTargetMediationExtras } from '@google/gma-mediation-mytarget';

const request: AdRequest = {
  // ...
  mediationExtras: [
    new MyTargetMediationExtras({
      isIosDebugMode: true, // Enable debug logging on iOS
    }),
  ],
};

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).
106 myTarget SDK failed to show the ad.

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.

Version 0.1.1 (In progress)

Version 0.1.0

  • Initial release.