Select platform: [Android (beta)
![New-selected](https://developers.google.com/static/admob/images/new-selected.svg)](https://developers.google.com/admob/android/next-gen/mediation/mytarget "View this page for the Android (beta) platform docs.") [Android](https://developers.google.com/admob/android/mediation/mytarget "View this page for the Android platform docs.") [iOS](https://developers.google.com/admob/ios/mediation/mytarget "View this page for the iOS platform docs.") [Unity](https://developers.google.com/admob/unity/mediation/mytarget "View this page for the Unity platform docs.") [Flutter](https://developers.google.com/admob/flutter/mediation/mytarget "View this page for the Flutter platform docs.")

<br />

This guide shows you how to use GMA Next-Gen SDK to load and display
ads from myTarget using [AdMob Mediation](https://developers.google.com/admob/android/next-gen/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
an Android app.

## Supported integrations and ad formats

The mediation adapter for myTarget has the following capabilities:

| Integration ||
|---|---|
| Bidding |   |
| Waterfall |   |
| Banner |   |
| Interstitial |   |
| Rewarded |   |
| Native |   |

## Requirements

- Android API level 24 or higher

<!-- -->

- Latest GMA Next-Gen SDK.

- Complete the mediation
  [Get started guide](https://developers.google.com/admob/android/next-gen/mediation).

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

Next, provide the

**Google Play URL**
for your app.

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

When adding an app, myTarget requires you to create an ad unit before you can
complete the process.
**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

You need to add myTarget to the
mediation configuration for your ad unit.

First, sign in to your [AdMob account](https://apps.admob.com/). Next, 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](https://developers.google.com/admob/android/next-gen/mediation/mytarget#add-ad-source).

To create a new mediation group, select **Create Mediation Group**.

![](https://developers.google.com/static/admob/images/mediation/admob-mediation-group-create.png)

Enter your ad format and platform, then click **Continue**.

![](https://developers.google.com/static/admob/images/mediation/admob-mediation-group-new-Android.png)

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

![](https://developers.google.com/static/admob/images/mediation/admob-mediation-group-details-Android.png)

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

![](https://developers.google.com/static/admob/images/mediation/admob-ad-units-select-Android.png)

You should now see the ad units card populated with the ad units you selected:

![](https://developers.google.com/static/admob/images/mediation/admob-ad-units-card-Android.png)

#### Add myTarget as an ad source

<br />

Under the **Waterfall** card in the **Ad Sources** section, select **Add Ad
Source** .  

Select **myTarget** and enable the **Optimize** switch. Enter the **Permanent Access Token** obtained in the previous section to set up ad source optimization for myTarget. Then enter an **eCPM value** for myTarget and click **Continue** .  

![](https://developers.google.com/static/admob/images/mediation/mytarget/admob-add-ad-network.png)  
| **Note**: You only need to set up ad source optimization once per network.

If you already have a mapping for myTarget, you can select it. Otherwise, click **Add mapping** .  
![](https://developers.google.com/static/admob/images/mediation/mytarget/waterfall-add-mapping-1-Android.png)  
Next, enter the **Slot ID** obtained in the previous section. Then click **Done** .  
![](https://developers.google.com/static/admob/images/mediation/mytarget/waterfall-add-mapping-2-Android.png)  
| **Note** : Ad source optimization takes a few days to gather enough data to accurately calculate eCPM for a mediation network. In the meantime, the ad source optimization status is `PENDING`, so you must manually set an eCPM value for the network. Once the eCPM can be calculated, the ad source automatically starts updating the eCPM on your behalf.

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

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

| **Note:** Failure to integrate the compatible myTarget and GMA Next-Gen SDK versions might lead to build issues.

### Android Studio integration (recommended)

In your app-level gradle file, add the following implementation
dependencies
and configurations:  

### Kotlin

```kotlin
dependencies {
    implementation("com.google.android.libraries.ads.mobile.sdk:ads-mobile-sdk:0.22.0-beta04")
    implementation("com.google.ads.mediation:mytarget:5.27.4.0")
}

configurations.configureEach {
    exclude(group = "com.google.android.gms", module = "play-services-ads")
    exclude(group = "com.google.android.gms", module = "play-services-ads-lite")
}
```

### Groovy

```groovy
dependencies {
    implementation 'com.google.android.libraries.ads.mobile.sdk:ads-mobile-sdk:0.22.0-beta04'
    implementation 'com.google.ads.mediation:mytarget:5.27.4.0'
}

configurations.configureEach {
    exclude group: 'com.google.android.gms', module: 'play-services-ads'
    exclude group: 'com.google.android.gms', module: 'play-services-ads-lite'
}
```

### Manual integration

- To include the myTarget SDK, consult the [myTarget Android SDK
  documentation](https://target.my.com/help/partners/mob/androidsdkstart/en).

- Navigate to the [myTarget adapter
  artifacts](https://maven.google.com/web/index.html#com.google.ads.mediation:mytarget)
  on Google's Maven Repository. Select the latest version, download the
  myTarget adapter's .aar file, and add it to your project.

## Step 4: Implement privacy settings on myTarget SDK

### EU consent and GDPR


To [comply with
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 consent is propagated to each ad source in your
mediation chain.
Google is unable to pass the user's
consent choice to such networks automatically.

In SDK version

5.1.0,

myTarget added a user consent API to support privacy requirements. The
following sample code shows how to pass this 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 GMA Next-Gen SDK.  

### Java

    import com.my.target.common.MyTargetPrivacy;
    // ...

    MyTargetPrivacy.setUserConsent(true);

### Kotlin

    import com.my.target.common.MyTargetPrivacy
    // ...

    MyTargetPrivacy.setUserConsent(true)

Additionally, if the user is known to be in an age-restricted category, you can
use the following code to pass this consent information to the myTarget SDK.  

### Java

    import com.my.target.common.MyTargetPrivacy;
    // ...

    MyTargetPrivacy.setUserAgeRestricted(true);

### Kotlin

    import com.my.target.common.MyTargetPrivacy
    // ...

    MyTargetPrivacy.setUserAgeRestricted(true)

See myTarget's
[Privacy and GDPR](https://target.my.com/help/partners/mob/gdpr_compliant/en) guide
for more information and the values that can be provided in the method.

### 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/android/next-gen/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.

In SDK version

5.9.0,

myTarget added a user consent API to support privacy requirements. The
following sample code shows how to pass this 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 GMA Next-Gen SDK.  

### Java

    import com.my.target.common.MyTargetPrivacy;
    // ...

    MyTargetPrivacy.setCcpaUserConsent(true);

### Kotlin

    import com.my.target.common.MyTargetPrivacy
    // ...

    MyTargetPrivacy.setCcpaUserConsent(true)

Contact [myTarget support](https://target.my.com/help/partners/mob/support/en) for
more information and the values that can be provided in the method.

## Step 5: Add required code

No additional code is required for myTarget integration.

## Step 6: Test your implementation

### Enable test ads

Make sure you
[register your test device](https://developers.google.com/admob/android/next-gen/test-ads#enable_test_devices)
for

AdMob and [enable test mode](https://developers.google.com/admob/android/next-gen/mediation/mytarget#turn-on-test-mode) in
myTarget UI.


| **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/android/next-gen/ad-inspector#single_ad_source_testing)
in ad inspector using the
**myTarget (Waterfall)** ad source(s).

## Optional steps

### Using native ads

#### Ad rendering

The myTarget adapter returns its native ads as

`NativeAd`

objects. It populates the following

[native ads field descriptions](https://support.google.com/admob/answer/6240809)

for a

[`NativeAd`](https://developers.google.com/admob/android/next-gen/reference/com/google/android/libraries/ads/mobile/sdk/nativead/NativeAd).


| Field | Populated by myTarget adapter |
|---|---|
| Headline | Always |
| Image | Always |
| Body | Always |
| App icon | Always |
| Call to action | Always |
| Star rating | Not guaranteed |
| Store | Not guaranteed |
| Price | Not guaranteed |
| Logo | Not guaranteed |
| Advertiser | Always |

The myTarget SDK always returns `0` for `mediaView` width and height, so the
myTarget adapter always returns `0` for
[`getAspectRatio()`](https://developers.google.com/admob/android/reference/com/google/android/gms/ads/MediaContent#getAspectRatio()).
The myTarget SDK will fix this issue in a future release.

#### Impression and click tracking

GMA Next-Gen SDK uses the myTarget SDK's callbacks for impression and
click tracking, so the reports from both sources should match up with few
to no discrepancies.

## Error codes

If the adapter fails to receive an ad from myTarget, you can check the
underlying error from the ad response using


[`ResponseInfo.getAdSourceResponses()`](https://developers.google.com/admob/android/next-gen/reference/com/google/android/libraries/ads/mobile/sdk/common/ResponseInfo#getAdSourceResponses())

under the following classes:  

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

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

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

## myTarget Android Mediation Adapter Changelog

#### Version 5.27.4.0

- Verified compatibility with myTarget SDK version 5.27.4.

Built and tested with:

- Google Mobile Ads SDK version 24.7.0.
- MyTarget SDK version 5.27.4.

#### Version 5.27.3.0

- Verified compatibility with myTarget SDK version 5.27.3.

Built and tested with:

- Google Mobile Ads SDK version 24.6.0.
- MyTarget SDK version 5.27.3.

#### Version 5.27.2.0

- Verified compatibility with myTarget SDK version 5.27.2.

Built and tested with:

- Google Mobile Ads SDK version 24.4.0.
- MyTarget SDK version 5.27.2.

#### Version 5.27.1.1

- Updated the minimum required Android API level to 23.
- Updated the minimum required Google Mobile Ads SDK version to 24.0.0.

Built and tested with:

- Google Mobile Ads SDK version 24.0.0.
- MyTarget SDK version 5.27.1.

#### Version 5.27.1.0

- Verified compatibility with myTarget SDK version 5.27.1.

Built and tested with:

- Google Mobile Ads SDK version 23.6.0.
- MyTarget SDK version 5.27.1.

#### Version 5.27.0.0

- Verified compatibility with myTarget SDK version 5.27.0.

Built and tested with:

- Google Mobile Ads SDK version 23.6.0.
- MyTarget SDK version 5.27.0.

#### Version 5.26.0.0

- Verified compatibility with myTarget SDK version 5.26.0.

Built and tested with:

- Google Mobile Ads SDK version 23.5.0.
- MyTarget SDK version 5.26.0.

#### Version 5.25.0.0

- Verified compatibility with myTarget SDK version 5.25.0.

Built and tested with:

- Google Mobile Ads SDK version 23.5.0.
- MyTarget SDK version 5.25.0.

#### Version 5.23.0.0

- Updated adapter to implement `onFailedToShow` method for fullscreen ads.
- Verified compatibility with myTarget SDK version 5.23.0.

Built and tested with:

- Google Mobile Ads SDK version 23.4.0.
- MyTarget SDK version 5.23.0.

#### Version 5.22.1.0

- Increased the maximum heap size for the Gradle JVM from 512MB to 1GB.
- Verified compatibility with myTarget SDK version 5.22.1.

Built and tested with:

- Google Mobile Ads SDK version 23.2.0.
- MyTarget SDK version 5.22.1.

#### Version 5.21.1.0

- Verified compatibility with myTarget SDK version 5.21.1.

Built and tested with:

- Google Mobile Ads SDK version 23.2.0.
- MyTarget SDK version 5.21.1.

#### Version 5.21.0.0

- Verified compatibility with myTarget SDK version 5.21.0.

Built and tested with:

- Google Mobile Ads SDK version 23.0.0.
- MyTarget SDK version 5.21.0.

#### Version 5.20.1.0

- Updated the minimum required Google Mobile Ads SDK version to 23.0.0.
- Verified compatibility with myTarget SDK version 5.20.1.

Built and tested with:

- Google Mobile Ads SDK version 23.0.0.
- MyTarget SDK version 5.20.1.

#### Version 5.20.0.0

- Verified compatibility with myTarget SDK version 5.20.0.

Built and tested with:

- Google Mobile Ads SDK version 22.5.0.
- MyTarget SDK version 5.20.0.

#### Version 5.19.0.0

- Verified compatibility with myTarget SDK version 5.19.0.

Built and tested with:

- Google Mobile Ads SDK version 22.3.0.
- MyTarget SDK version 5.19.0.

#### Version 5.18.0.0

- Verified compatibility with myTarget SDK version 5.18.0.

Built and tested with:

- Google Mobile Ads SDK version 22.2.0.
- MyTarget SDK version 5.18.0.

#### Version 5.17.0.0

- Verified compatibility with myTarget SDK version 5.17.0.

Built and tested with:

- Google Mobile Ads SDK version 22.2.0.
- MyTarget SDK version 5.17.0.

#### Version 5.16.5.0

- Verified compatibility with myTarget SDK version 5.16.5.

Built and tested with:

- Google Mobile Ads SDK version 22.0.0.
- MyTarget SDK version 5.16.5.

#### Version 5.16.4.1

- Updated adapter to use new `VersionInfo` class.
- Updated the minimum required Google Mobile Ads SDK version to 22.0.0.

Built and tested with:

- Google Mobile Ads SDK version 22.0.0.
- MyTarget SDK version 5.16.4.

#### Version 5.16.4.0

- Verified compatibility with myTarget SDK version 5.16.4.
- Updated the minimum required Google Mobile Ads SDK version to 21.5.0.

Built and tested with:

- Google Mobile Ads SDK version 21.5.0.
- MyTarget SDK version 5.16.4.

#### Version 5.16.3.0

- Verified compatibility with myTarget SDK version 5.16.3.
- Updated the minimum required Google Mobile Ads SDK version to 21.4.0.

Built and tested with:

- Google Mobile Ads SDK version 21.4.0.
- MyTarget SDK version 5.16.3.

#### Version 5.16.2.0

- Verified compatibility with myTarget SDK version 5.16.2.

Built and tested with:

- Google Mobile Ads SDK version 21.3.0.
- MyTarget SDK version 5.16.2.

#### Version 5.16.1.0

- Verified compatibility with myTarget SDK version 5.16.1.

Built and tested with:

- Google Mobile Ads SDK version 21.3.0.
- MyTarget SDK version 5.16.1.

#### Version 5.16.0.0

- Verified compatibility with myTarget SDK version 5.16.0.

Built and tested with:

- Google Mobile Ads SDK version 21.3.0.
- MyTarget SDK version 5.16.0.

#### Version 5.15.5.0

- Verified compatibility with myTarget SDK version 5.15.5.
- Updated the minimum required Google Mobile Ads SDK version to 21.3.0.

Built and tested with:

- Google Mobile Ads SDK version 21.3.0.
- MyTarget SDK version 5.15.5.

#### Version 5.15.4.0

- Verified compatibility with myTarget SDK version 5.15.4.
- Updated the minimum required Google Mobile Ads SDK version to 21.1.0.

Built and tested with:

- Google Mobile Ads SDK version 21.1.0.
- MyTarget SDK version 5.15.4.

#### Version 5.15.3.0

- Verified compatibility with myTarget SDK version 5.15.3.

Built and tested with:

- Google Mobile Ads SDK version 21.0.0.
- MyTarget SDK version 5.15.3.

#### Version 5.15.2.1

- Updated the minimum required Google Mobile Ads SDK version to 21.0.0.
- Updated the minimum required Android API level to 19.

Built and tested with:

- Google Mobile Ads SDK version 21.0.0.
- MyTarget SDK version 5.15.2.

#### Version 5.15.2.0

- Verified compatibility with myTarget SDK version 5.15.2.

Built and tested with:

- Google Mobile Ads SDK version 20.6.0.
- MyTarget SDK version 5.15.2.

#### Version 5.15.1.0

- Verified compatibility with myTarget SDK version 5.15.1.
- Updated `compileSdkVersion` and `targetSdkVersion` to API 31.
- Updated the minimum required Google Mobile Ads SDK version to 20.6.0.

Built and tested with:

- Google Mobile Ads SDK version 20.6.0.
- MyTarget SDK version 5.15.1.

#### Version 5.15.0.0

- Verified compatibility with myTarget SDK version 5.15.0.

Built and tested with:

- Google Mobile Ads SDK version 20.5.0.
- MyTarget SDK version 5.15.0.

#### Version 5.14.4.0

- Verified compatibility with myTarget SDK version 5.14.4.
- Added mediation extras handling for `CustomParams`.
- Fixed an issue where the native ad `MediaView` was not properly registered as a clickable asset.
- Updated the minimum required Google Mobile Ads SDK version to 20.5.0.

Built and tested with:

- Google Mobile Ads SDK version 20.5.0.
- MyTarget SDK version 5.14.4.

#### Version 5.14.3.0

- Verified compatibility with myTarget SDK version 5.14.3.

Built and tested with:

- Google Mobile Ads SDK version 20.4.0.
- MyTarget SDK version 5.14.3.

#### Version 5.14.2.0

- Verified compatibility with myTarget SDK version 5.14.2.

Built and tested with:

- Google Mobile Ads SDK version 20.4.0.
- MyTarget SDK version 5.14.2.

#### Version 5.14.1.0

- Verified compatibility with myTarget SDK version 5.14.1.
- Updated the minimum required Google Mobile Ads SDK version to 20.4.0.

Built and tested with:

- Google Mobile Ads SDK version 20.4.0.
- MyTarget SDK version 5.14.1.

#### Version 5.13.4.0

- Verified compatibility with myTarget SDK version 5.13.4.

Built and tested with:

- Google Mobile Ads SDK version 20.3.0.
- MyTarget SDK version 5.13.4.

#### Version 5.13.3.0

- Verified compatibility with myTarget SDK version 5.13.3.
- Updated the minimum required Google Mobile Ads SDK version to 20.3.0.

Built and tested with:

- Google Mobile Ads SDK version 20.3.0.
- MyTarget SDK version 5.13.3.

#### Version 5.13.2.0

- Verified compatibility with myTarget SDK version 5.13.2.

Built and tested with:

- Google Mobile Ads SDK version 20.2.0.
- MyTarget SDK version 5.13.2.

#### Version 5.13.1.0

- Verified compatibility with myTarget SDK version 5.13.1.
- Updated the minimum required Google Mobile Ads SDK version to 20.2.0.

Built and tested with:

- Google Mobile Ads SDK version 20.2.0.
- MyTarget SDK version 5.13.1.

#### Version 5.13.0.0

- Verified compatibility with myTarget SDK version 5.13.0.

Built and tested with:

- Google Mobile Ads SDK version 20.1.0.
- MyTarget SDK version 5.13.0.

#### Version 5.12.3.0

- Verified compatibility with myTarget SDK version 5.12.3.
- Updated the minimum required Google Mobile Ads SDK version to 20.1.0.

Built and tested with:

- Google Mobile Ads SDK version 20.1.0.
- MyTarget SDK version 5.12.3.

#### Version 5.12.2.0

- Verified compatibility with myTarget SDK version 5.12.2.
- Updated the minimum required Google Mobile Ads SDK version to 20.0.0.

Built and tested with:

- Google Mobile Ads SDK version 20.0.0.
- MyTarget SDK version 5.12.2.

#### Version 5.11.12.0

- Verified compatibility with myTarget SDK version 5.11.12.

Built and tested with:

- Google Mobile Ads SDK version 19.7.0.
- MyTarget SDK version 5.11.12.

#### Version 5.11.10.0

- Verified compatibility with myTarget SDK version 5.11.10.
- Added descriptive error codes and reasons for adapter load/show failures.
- Updated the minimum required Google Mobile Ads SDK version to 19.7.0.

Built and tested with:

- Google Mobile Ads SDK version 19.7.0.
- MyTarget SDK version 5.11.10.

#### Version 5.11.7.0

- Verified compatibility with myTarget SDK version 5.11.7.

Built and tested with:

- Google Mobile Ads SDK version 19.6.0.
- MyTarget SDK version 5.11.7.

#### Version 5.11.6.0

- Verified compatibility with myTarget SDK version 5.11.6.
- Removed support for the deprecated `NativeContentAd` and `NativeAppInstallAd` formats. Apps should request for unified native ads.
- Fixed an issue where banner ads sometimes load with a larger size than requested.
- Updated the minimum required Google Mobile Ads SDK version to 19.6.0.

Built and tested with:

- Google Mobile Ads SDK version 19.6.0.
- MyTarget SDK version 5.11.6.

#### Version 5.11.5.0

- Verified compatibility with myTarget SDK version 5.11.5.

Built and tested with:

- Google Mobile Ads SDK version 19.5.0.
- MyTarget SDK version 5.11.5.

#### Version 5.11.4.0

- Verified compatibility with myTarget SDK version 5.11.4.

Built and tested with:

- Google Mobile Ads SDK version 19.5.0.
- MyTarget SDK version 5.11.4.

#### Version 5.11.3.0

- Added support for myTarget's adaptive banner ad size.
- Verified compatibility with myTarget SDK version 5.11.3.
- Updated the minimum required Google Mobile Ads SDK version to 19.5.0.

Built and tested with:

- Google Mobile Ads SDK version 19.5.0.
- MyTarget SDK version 5.11.3.

#### Version 5.10.0.0

- Verified compatibility with myTarget SDK version 5.10.0.
- Updated the minimum required Google Mobile Ads SDK version to 19.4.0.

Built and tested with:

- Google Mobile Ads SDK version 19.4.0.
- MyTarget SDK version 5.10.0.

#### Version 5.9.1.0

- Verified compatibility with myTarget SDK version 5.9.1.

Built and tested with:

- Google Mobile Ads SDK version 19.2.0.
- MyTarget SDK version 5.9.1.

#### Version 5.8.4.0

- Verified compatibility with myTarget SDK version 5.8.4.

Built and tested with:

- Google Mobile Ads SDK version 19.2.0.
- MyTarget SDK version 5.8.4.

#### Version 5.8.3.0

- Verified compatibility with myTarget SDK version 5.8.3.
- Updated the minimum required Google Mobile Ads SDK version to 19.2.0.

Built and tested with:

- Google Mobile Ads SDK version 19.2.0.
- MyTarget SDK version 5.8.3.

#### Version 5.8.2.0

- Verified compatibility with myTarget SDK version 5.8.2.
- Updated the adapter to support inline adaptive banner requests.

Built and tested with:

- Google Mobile Ads SDK version 19.1.0.
- MyTarget SDK version 5.8.2.

#### Version 5.8.1.0

- Verified compatibility with myTarget SDK version 5.8.1.

Built and tested with:

- Google Mobile Ads SDK version 19.1.0.
- MyTarget SDK version 5.8.1.

#### Version 5.8.0.0

- Verified compatibility with myTarget SDK version 5.8.0.

Built and tested with:

- Google Mobile Ads SDK version 19.1.0.
- MyTarget SDK version 5.8.0.

#### Version 5.7.1.0

- Verified compatibility with myTarget SDK version 5.7.1.

Built and tested with:

- Google Mobile Ads SDK version 19.1.0.
- MyTarget SDK version 5.7.1.

#### Version 5.7.0.0

- Verified compatibility with myTarget SDK version 5.7.0.
- Updated the minimum required Google Mobile Ads SDK version to 19.1.0.

Built and tested with:

- Google Mobile Ads SDK version 19.1.0.
- MyTarget SDK version 5.7.0.

#### Version 5.6.3.0

- Verified compatibility with myTarget SDK version 5.6.3.

Built and tested with:

- Google Mobile Ads SDK version 19.0.1.
- MyTarget SDK version 5.6.3.

#### Version 5.6.2.0

- Verified compatibility with myTarget SDK version 5.6.2.
- Updated the minimum required Google Mobile Ads SDK version to 19.0.1.

Built and tested with:

- Google Mobile Ads SDK version 19.0.1.
- MyTarget SDK version 5.6.2.

#### Version 5.6.1.0

- Verified compatibility with myTarget SDK version 5.6.1.

Built and tested with:

- Google Mobile Ads SDK version 19.0.0.
- MyTarget SDK version 5.6.1.

#### Version 5.6.0.0

- Verified compatibility with myTarget SDK version 5.6.0.
- Updated the minimum required Google Mobile Ads SDK version to 19.0.0.
- Updated the minimum required Android API level to 16.

Built and tested with:

- Google Mobile Ads SDK version 19.0.0.
- MyTarget SDK version 5.6.0.

#### Version 5.5.5.0

- Verified compatibility with myTarget SDK version 5.5.5.
- Updated the minimum required Google Mobile Ads SDK version to 18.3.0.

Built and tested with:

- Google Mobile Ads SDK version 18.3.0.
- MyTarget SDK version 5.5.5.

#### Version 5.4.6.0

- Verified compatibility with myTarget SDK version 5.4.6.
- Updated the minimum required Google Mobile Ads SDK version to 18.2.0.

#### Version 5.4.5.0

- Verified compatibility with myTarget SDK version 5.4.5.
- Updated the minimum required Google Mobile Ads SDK version to 18.1.0.

#### Version 5.4.0.0

- Verified compatibility with myTarget SDK version 5.4.0.

#### Version 5.3.9.1

- Added support for flexible banner ad sizes.

#### Version 5.3.9.0

- Verified compatibility with myTarget SDK version 5.3.9.
- Updated adapter to support new open-beta Rewarded API.
- Updated the minimum required Google Mobile Ads SDK version to 17.2.0.

#### Version 5.3.6.0

- Verified compatibility with myTarget SDK version 5.3.6.

#### Version 5.2.5.0

- Verified compatibility with myTarget SDK version 5.2.5.
- Fixed a bug where the adapter fails to request a Banner ad when using a custom size.

#### Version 5.2.2.0

- Verified compatibility with myTarget SDK version 5.2.2.

#### Version 5.2.1.0

- Verified compatibility with myTarget SDK version 5.2.1.

#### Version 5.2.0.0

- Verified compatibility with myTarget SDK version 5.2.0.

#### Version 5.1.4.0

- Verified compatibility with myTarget SDK version 5.1.4.

#### Version 5.1.3.0

- Verified compatibility with myTarget SDK version 5.1.3.

#### Version 5.1.2.0

- Verified compatibility with myTarget SDK version 5.1.2.

#### Version 5.1.1.0

- Verified compatibility with myTarget SDK version 5.1.1.

#### Version 5.1.0.1

- Updated adapter to use the Unified Native Ads adapter API.

#### Version 5.1.0.0

- Verified compatibility with myTarget SDK version 5.1.0.

#### Version 5.0.4.0

- Verified compatibility with myTarget SDK version 5.0.4.

#### Version 5.0.2.1

- Updated the adapter to make it compatible with Google Mobile Ads SDK version 15.0.0.

#### Version 5.0.2.0

- Verified compatibility with myTarget SDK version 5.0.2.

#### Version 5.0.0.0

- Verified compatibility with myTarget SDK version 5.0.0.
- Updated the adapter to make it compatible with myTarget SDK 5.0.0 and Android Studio 3.1.

#### Version 4.7.2.0

- Verified compatibility with myTarget SDK version 4.7.2.

#### Version 4.7.1.0

- Verified compatibility with myTarget SDK version 4.7.1.
- Added support for video and carousel ads inside MediaView.

#### Version 4.6.28.0

- Updated the adapter project for Android Studio 3.0.
- Verified compatibility with myTarget SDK version 4.6.28.

#### Version 4.6.27.0

- First release!
- Added support for banner, interstitial, rewarded, and native ads.