<br />

This guide shows you how to use Google Mobile Ads SDK for React Native to load and display
ads from myTarget using
[mediation](https://developers.google.com/admob/react-native/mediation.md.txt), 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 | Yes |
| App Open |   |
| Banner | Yes |
| Interstitial | Yes |
| Rewarded | Yes |
| Rewarded Interstitial |   |
| Native | Yes |

## Prerequisites

Before you continue, verify the following:

- Latest Google Mobile Ads SDK for React Native version.
- React Native framework version 0.85.0 or later.
- To deploy on Android
  - Android API level 24 or later.
- To deploy on iOS
  - iOS deployment target of 13.0 or later.
- A working React Native project configured with Google Mobile Ads SDK for React Native. See [Set up Google Mobile Ads SDK for React Native](https://developers.google.com/admob/react-native/quick-start.md.txt) for details.
  - Make sure you have downloaded and extracted the `adapters` folder from the [`gma-sdk-react-native`](https://drive.google.com/corp/drive/folders/1s5j2kx0yyYxLsdLNyBrhNJvkzmaUgOwD) folder. If you don't have the `adapters` folder, follow steps one, two, and three in [Install Google Mobile Ads SDK for React Native](https://developers.google.com/admob/react-native/quick-start.md.txt#install).
- [Set up AdMob Mediation](https://developers.google.com/admob/react-native/mediation.md.txt).

## Step 1: Set up configurations in myTarget UI

[Log in](https://target.vk.ru/) to your myTarget account. Navigate to the Apps page
by clicking on **APPS** on the header. Add your app by clicking **ADD APP**.

![](https://developers.google.com/static/admob/images/mediation/mytarget/add_app.png)

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.

![](https://developers.google.com/static/admob/images/mediation/mytarget/add_url_Android.png)

### iOS

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

![](https://developers.google.com/static/admob/images/mediation/mytarget/add_url_iOS.png)

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

> [!NOTE]
> **Note:** To add an ad unit to an existing app, open your app details page by clicking on your app's name and then click **CREATE AD UNIT.**

### Banner

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

![](https://developers.google.com/static/admob/images/mediation/mytarget/ad_unit_banner.png)

### Interstitial

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

![](https://developers.google.com/static/admob/images/mediation/mytarget/ad_unit_interstitial.png)

### Rewarded

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

![](https://developers.google.com/static/admob/images/mediation/mytarget/ad_unit_rewarded.png)

### Native

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

![](https://developers.google.com/static/admob/images/mediation/mytarget/ad_unit_native.png)

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.

![](https://developers.google.com/static/admob/images/mediation/mytarget/overview.png)

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

![](https://developers.google.com/static/admob/images/mediation/mytarget/access_token.png)

### Update your app-ads.txt


[Authorized Sellers for Apps app-ads.txt](https://iabtechlab.com/wp-content/uploads/2019/03/app-ads.txt-v1.0-final-.pdf) 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](https://support.google.com/admob/answer/9363762).

To implement `app-ads.txt` for myTarget, see
[How to create and publish a file](https://target.vk.ru/help/partners/mob/adstxt/en#create).

### Turn on test mode

Follow the instructions in
[myTarget's documentation](https://target.my.com/help/partners/mob/testcreative/en)
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](https://developers.google.com/admob/android/mediation/mytarget.md.txt#step-2).

### iOS

For instructions, see step 2 in the guide for

[iOS](https://developers.google.com/admob/ios/mediation/mytarget.md.txt#step-2).

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

> [!IMPORTANT]
> **Important:** Verify that you have **Account Management** permission to complete the configuration for EU Consent and GDPR, US State regulations, and User Messaging Platform. See [Manage user access to your
> account](https://support.google.com/admob/answer/2784628) for details.

Follow the steps in

[European regulations settings](https://support.google.com/admob/answer/10113004#adding_ad_partners_to_published_gdpr_messages)

and

[US state regulations settings](https://support.google.com/admob/answer/14125907)


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](https://developers.google.com/admob/react-native/mediation/mytarget.md.txt#prerequisites).

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

   Replace <var class="readonly" translate="no">EXTRACT_DIR</var> with the path to the
   directory where you extracted the archive.
2. Install the adapter package using your preferred package manager:

   ### npm

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

   ### yarn

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


## Step 4: Implement privacy settings on myTarget SDK

### EU Consent and GDPR


To [comply with
the Google EU User Consent Policy](https://www.google.com/about/company/consentstaging.html), 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](https://developers.google.com/admob/react-native/privacy.md.txt)
and consent management platforms that integrate with

[Google's Additional Consent specification](https://support.google.com/admob/answer/9681920)

to myTarget SDK.

### US states privacy laws


[US states privacy laws](https://support.google.com/admob/answer/9561022)
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](https://developers.google.com/admob/react-native/privacy/us-states) offers the ability to enable
[restricted data processing](https://privacy.google.com/businesses/rdp/)
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](https://developers.google.com/admob/android/mediation/mytarget.md.txt#us-states-privacy-laws)
and [iOS](https://developers.google.com/admob/ios/mediation/mytarget.md.txt#us-states-privacy-laws)
developer guides.

## Step 5: Add required code

### Android

No additional code is required for
myTarget integration.

### iOS

### SKAdNetwork integration

Follow [myTarget's
documentation](https://target.my.com/help/partners/mob/ios14integration/en)
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](https://developers.google.com/admob/react-native/test-ads.md.txt#enable_test_devices)
for

AdMob and [enable test mode](https://developers.google.com/admob/react-native/mediation/mytarget.md.txt#turn-on-test-mode) in
myTarget UI.


> [!IMPORTANT]
> **Important:** Disable test mode for AdMob and myTarget before releasing your app.

### Verify test ads

To verify that you are receiving test ads from
myTarget,
enable
[single ad source testing](https://developers.google.com/admob/react-native/ad-inspector#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](https://developers.google.com/admob/ios/mediation/mytarget.md.txt#network-specific_parameters)
guide.

The following sample code shows how to set `isIosDebugMode`:

```javascript
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`](https://developers.google.com/admob/react-native/response-info.md.txt) under the
following classes:

### Android

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

### iOS

```objective-c
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.

<!-- -->

- Supports [myTarget Android adapter version 5.51.2.1](https://github.com/googleads/googleads-mobile-android-mediation/blob/main/ThirdPartyAdapters/mytarget/CHANGELOG.md#version-55121).
- Supports [myTarget iOS adapter version 5.46.0.0](https://github.com/googleads/googleads-mobile-ios-mediation/blob/main/adapters/MyTarget/CHANGELOG.md#version-54600).
- Built and tested with the Google Mobile Ads React Native Plugin version 0.1.0.