> For the complete documentation index, see [llms.txt](https://aatkit.gitbook.io/rtbsdk-release-notes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aatkit.gitbook.io/rtbsdk-release-notes/android/release-notes.md).

# Release Notes

## 1.9

<details>

<summary>1.9.3</summary>

2025-12-09

### Fixes

* Fixed very rare crash when presenting new banner ad.

</details>

<details>

<summary>1.9.2</summary>

2025-11-20

### New Features <a href="#new-features" id="new-features"></a>

* Added support for [hybrid native ads](https://aatkit.gitbook.io/rtbsdk-android-integration/formats/advanced/beta-hybrid-native-ads), format allowing to combine banner and native ad request.

### Changes <a href="#changes" id="changes"></a>

* Removed AppCompat dependency.
* Lowered minimum Android SDK Platform requirement for AdMob and AppLovin Mediation Adapters to API level 23.
* Updated build tools and target SDK versions.

</details>

## 1.8

<details>

<summary>1.8.3</summary>

2025-08-11

#### New Features <a href="#new-features-1" id="new-features-1"></a>

* Introduced support for [passing the UTIQ identifier](https://aatkit.gitbook.io/rtbsdk-android-integration/formats/advanced/utiq)
* Introduced support for [passing GPID (global placement ID) identifier](https://aatkit.gitbook.io/rtbsdk-android-integration/formats/advanced/global-placement-id)

</details>

## 1.7

<details>

<summary>1.7.4</summary>

2025-07-08

### Fixes

* Fixed issue with MRAID expand function handling, potentially causing crashes for certain creatives.
* Ensured all resources used by RTBSDK use prefixed names to avoid conflicts.

</details>

<details>

<summary>1.7.3</summary>

2025-06-26

## **New Features**

* Introduced support for Rewarded Video format. See the [rewarded video ads integration guide](https://aatkit.gitbook.io/rtbsdk-android-integration/formats/rewarded-video) to learn more.
* Introduced Rewarded Video ads support for AdMob Custom Events.
* Introduced Rewarded Video ads support for the AppLovin Mediation Adapter.

</details>

## 1.6

<details>

<summary>1.6.3</summary>

2025-04-04

### Fixes

* Fixed parsing of optional bidFloor parameter in the [AppLovin Custom Adapter](https://aatkit.gitbook.io/rtbsdk-android-integration/other/applovin-custom-adapter).

</details>

<details>

<summary>1.6.2</summary>

2025-03-05

### **New Features** <a href="#new-features" id="new-features"></a>

* Introduced support for passing user targeting before requesting new ads. See format integration instructions for more details.

### **Improvements** <a href="#improvements" id="improvements"></a>

* Delayed rendering of the ad creative in ad view until it is attached to window.

</details>

## 1.5

<details>

<summary>1.5.1</summary>

2025-02-11

### New Features <a href="#new-features-1" id="new-features-1"></a>

* Introduced support for AdMob Custom Events. Please refer to the documentation for the integration details.
* Introduced native ads support in the AppLovin Mediation Adapter.

### **Improvements**

* Added verification for Google Playstore SDK ownership

</details>

## 1.4

<details>

<summary>1.4.7</summary>

2024-11-12

* Added `displaymanager` and `displaymanagerver` parameters to bid requests

</details>

<details>

<summary>1.4.6</summary>

2024-11-07

* Improvements for MRAID video ads.

</details>

<details>

<summary>1.4.5</summary>

2024-10-25

* Improved OMID handling.

</details>

<details>

<summary>1.4.4</summary>

2024-09-23

### New Features

* Added support for native ads. See the [native ads integration guide](https://aatkit.gitbook.io/rtbsdk-android-integration/formats/native-ads) to learn more.
* Added OMSDK support for both banners and fullscreen ads.
* Created the [AppLovin Custom Adapter](https://aatkit.gitbook.io/rtbsdk-android-integration/other/applovin-custom-adapter), allowing to integrate RTB SDK as part of AppLovin mediation.

### Improvements

* Extended the `RTBBidInfo` with creative and campaign ID fields.&#x20;

</details>

## 1.3

<details>

<summary>1.3.4</summary>

2024-09-04

### Fixes

* Fixed DSPAdapters handling for RTBBannerView

</details>

<details>

<summary>1.3.3</summary>

2024-08-26

### Fixes

* Fixed exception in fullscreen MRAIDView's when RTBFullscreenAd.show() call

</details>

<details>

<summary>1.3.2</summary>

2024-07-31

### **API Changes**

* Completely reworked special API for separate loading and rendering of banner ads. See the [updated integration instruction](https://aatkit.gitbook.io/rtbsdk-android-integration/formats/advanced/separate-loading-and-rendering-of-banner-ads) for details.

</details>

<details>

<summary>1.3.1</summary>

2024-07-15

### Fixes

* Fixed rare exception in fullscreen MRAIDView's onConfigurationChanged event handling

</details>

<details>

<summary>1.3.0</summary>

2024-07-08

### Improvements

* Added MRAID support for both banners and fullscreen formats.
* Provided the bidder (DSP name) with bid responses (Check the API changes section for more information).
* Implement the new `RTBBannerAd` feature that loads the banner but does not render it directly like the `RTBBannerView`. See [here](https://aatkit.gitbook.io/rtbsdk-android-integration/formats/advanced/separate-loading-and-rendering-of-banner-ads) for more information.

### **API Changes**

* Enhanced the `RTBBannerViewDelegate` by updating the `bannerViewDidReceiveAd` API to include the bidder (DSP name) in the bidding response. The bidder and the bid price are now encapsulated within the new `bidInfo` parameter.
  * The new method signature is `fun bannerViewDidReceiveAd(bannerView: RTBBannerView, bidInfo: RTBBidInfo, networkName: String)`
* Enhanced the `RTBBannerAdDelegate` by updating the `bannerAdDidReceiveAd` API to include the bidder (DSP name) in the bidding response. The bidder and the bid price are now encapsulated within the new `bidInfo` parameter.
  * The new method signature is `fun bannerAdDidReceiveAd(bidInfo: RTBBidInfo, networkName: String)`
* Enhanced the `RTBFullscreenDelegate` by updating the `fullscreenAdDidReceiveAd` API to include the bidder (DSP name) in the bidding response. The bidder and the bid price are now encapsulated within the new `bidInfo` parameter.
  * The new method signature is `fun fullscreenAdDidReceiveAd(fullscreenAd: RTBFullscreenAd, bidInfo: RTBBidInfo, networkName: String)`
* `RTBBidInfo` interface:

```kotlin
class RTBBidInfo(val priceCPM: Float, val bidder: String) {

    override fun toString(): String {
        return "RTBBidInfo(priceCPM=$priceCPM, bidder='$bidder')"
    }
}
```

</details>

## 1.1

<details>

<summary>1.1.4</summary>

2024-04-04

* Fixed wrong value being passed as COPPA setting

</details>

<details>

<summary>1.1.3</summary>

2024-04-04

* First version published on Maven

</details>

<details>

<summary>1.1.2</summary>

2024-03-12

* Changed obfuscation settings to avoid generating potentially conflicting classes like `a.a`

</details>

<details>

<summary>1.1.1</summary>

2024-03-07

* Fixed reacting to consent string changes during session

</details>

<details>

<summary>1.1.0</summary>

2024-02-22

* Implement Google Bidding. Google Bidding can and may only be used via Gravite's mediation SDK [AATKit](https://aatkit.gitbook.io/release-notes).

</details>

## 1.0

<details>

<summary>1.0.4</summary>

2024-02-13

* Add fullscreen close button delay (configurable from the dashboard).

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://aatkit.gitbook.io/rtbsdk-release-notes/android/release-notes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.