> For the complete documentation index, see [llms.txt](https://documentation.hyprmx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.hyprmx.com/sdk-integration-guides/ios/3rd-party-mediation/applovin-max.md).

# AppLovin MAX

{% hint style="danger" %}
The **legacy MAX HyprMX adapter** is being sunset. Migrate to the **custom adapter** **today** to avoid any disruption to monetization
{% endhint %}

## Introduction <a href="#hyprmxmobilesdkadmobadapteroverview-introduction" id="hyprmxmobilesdkadmobadapteroverview-introduction"></a>

This guide walks you through setting up the HyprMX iOS SDK as a custom ad network in AppLovin MAX mediation. The adapter can be set up with CocoaPods. See below for instructions on how to set up a new adapter or upgrade to newer versions.

## Supported Ad Formats <a href="#hyprmxmobilesdkadmobadapteroverview-introduction" id="hyprmxmobilesdkadmobadapteroverview-introduction"></a>

* Rewarded Ads
* Interstitial Ads&#x20;
* Banner/MREC&#x20;

## Compatibility <a href="#hyprmxmobilesdkadmobadapteroverview-upgradeinstructions5.0to5.4.5.0" id="hyprmxmobilesdkadmobadapteroverview-upgradeinstructions5.0to5.4.5.0"></a>

* **HyprMX-MAX Adapter Version:** 6.4.6.0
* **Compatible with AppLovin SDK:** 12.4.1+

{% hint style="info" %}
Find additional compatibility details on the [Downloads](/sdk-integration-guides/ios/downloads.md) page.
{% endhint %}

If you need support for older AppLovin versions, your HyprMX account manager is here to help.

## Step 1: Add HyprMX as a Custom Network <a href="#hyprmxmobilesdkadmobadapteroverview-upgradeinstructions5.0to5.4.5.0" id="hyprmxmobilesdkadmobadapteroverview-upgradeinstructions5.0to5.4.5.0"></a>

{% stepper %}
{% step %}
In the MAX Dashboard, go to: [MAX > Mediation > Manage > Networks](https://dash.applovin.com/o/mediation/networks/).
{% endstep %}

{% step %}
Click "**Click here to add a Custom Network"** at the bottom of the page. The "**Create Custom Network"** page appears.
{% endstep %}

{% step %}
Enter the following details about the custom network:

* **Network Type**: SDK
* **Custom Network Name**: HyprMX
* **iOS Adapter Class Name**: HyprMXAdapter
* **Android Adapter Class Name:** com.hyprmx.android.HyprMXMaxAdapter
  * Keep this blank if you're only integrating with iOS

{% hint style="info" %}
**Please note:** iOS and Android Class Names must be entered *exactly* as indicated above.
{% endhint %}

<figure><img src="/files/bt2kzlcC9T05CR61OrDw" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Press Save to create the SDK network.
{% endstep %}
{% endstepper %}

## Step 2: Create Ad Units <a href="#hyprmxmobilesdkadmobadapteroverview-upgradeinstructions5.0to5.4.5.0" id="hyprmxmobilesdkadmobadapteroverview-upgradeinstructions5.0to5.4.5.0"></a>

> 💡**Migrating from the MAX Legacy Adapter?**
>
> If you’ve previously set up HyprMX ad units using the legacy adapter, you’ll need to create **new placements** for the custom adapter.

**To set up:**

{% stepper %}
{% step %}
Open [MAX > Mediation > Manage > Ad Units](https://dash.applovin.com/o/mediation/ad_units/) in the MAX dashboard.
{% endstep %}

{% step %}
Click the ad unit where you want to enable HyprMX.
{% endstep %}

{% step %}
Scroll down to the Custom Networks section and enable **HyprMX.**

<figure><img src="/files/sgRWzKZV0SdqV4TqUaTO" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Enter relevant information for each placement.

> 💡**Migrating from the MAX Legacy Adapter?**
>
> To keep your reporting clean and seamless:
>
> * **Use the same Distributor ID(s)** you've been using with your current setup
> * **Use the same Placement Name(s)** as your current setup

* **App ID:** Your Distributor ID (from your account manager)
* **Placement ID:** Your Placement Name (from your account manager)
* **CPM Price:** Desired floor price
  {% endstep %}

{% step %}
Save and repeat these steps for each Ad Unit you'd like to configure.
{% endstep %}

{% step %}
If you’re migrating from the legacy adapter and still have older app builds with the legacy adapter live, keep the legacy adapter settings enabled under **Other Networks** to continue monetizing those builds. You may keep both legacy and custom adapter settings enabled at the same time, **but each app build should include only one HyprMX adapter to avoid conflicts.**

<figure><img src="/files/4I2eaxIJUCmpumkYW1Lo" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

## Step 3: Install Custom Adapter <a href="#hyprmxmobilesdkadmobadapteroverview-upgradeinstructions5.0to5.4.5.0" id="hyprmxmobilesdkadmobadapteroverview-upgradeinstructions5.0to5.4.5.0"></a>

This guide assumes you already have the AppLovin Android SDK integrated into your project. If not, refer to the [AppLovin integration guide](https://developers.applovin.com/en/max/ios/overview/integration) before proceeding. The custom adapter can be integrated using CocoaPods or Swift Package Manager.

### Swift Package Manager

Follow these steps to install the HyprMX custom adapter via Swift Package Manager:

{% stepper %}
{% step %}
From XCode's menu bar, navigate to File / Add Package Dependencies...
{% endstep %}

{% step %}
Place the following text into the search bar located in the upper right of the dialog.

```
git@github.com:JunGroupProductions/HyprMX-MAX-SPM.git
```

{% endstep %}

{% step %}
Select the "Exact Version" option for the Dependency Rule and use the following version:

```
6.4.60
```

{% endstep %}

{% step %}
Click the "Add Package" button.
{% endstep %}
{% endstepper %}

### CocoaPods

Follow these steps to install the HyprMX custom adapter via CocoaPods:

{% stepper %}
{% step %}
Make sure you’re using CocoaPods version `1.10.2` or newer.
{% endstep %}

{% step %}
If you're migrating from the legacy adapter, **remove** the following line from your Podfile to upgrade the adapter files:&#x20;

{% hint style="danger" %}
**Important: Avoid Adapter Conflicts**

Only use a **single** HyprMX adapter (either legacy or custom) in a given **app** **build**. Running more than one may cause conflicts and disrupt monetization.
{% endhint %}

```
pod 'AppLovinMediationHyprMXAdapter'
```

{% endstep %}

{% step %}
Add the following to your Podfile:

```
pod 'HyprMX-Max', '6.4.6.0'
```

{% endstep %}
{% endstepper %}

## Step 4: Test and Verify Integration <a href="#hyprmxmobilesdkadmobadapteroverview-upgradeinstructions5.0to5.4.5.0" id="hyprmxmobilesdkadmobadapteroverview-upgradeinstructions5.0to5.4.5.0"></a>

You can receive test ads by enabling test mode. When using the **custom adapter**, enable **test mode** **before** initializing MAX:

{% tabs %}
{% tab title="Swift" %}

```swift
import HyprMX_Max // At top of same file

HyprMXAdapter.enableTestMode() // Before initializing AppLovin MAX SDK
```

{% endtab %}

{% tab title="Objective-C" %}

```objectivec
#import <HyprMX_Max/HyprMX_Max-Swift.h> // At top of same file

[HyprMXAdapter enableTestMode]; // Before initializing AppLovin MAX SDK
```

{% endtab %}
{% endtabs %}

{% hint style="warning" %}
When testing HyprMX, ensure that your mobile device is **not** listed in the **MAX Test Devices** on the AppLovin Dashboard.
{% endhint %}

We recommend putting HyprMX at the top of your waterfall during testing to ensure you receive ad requests.

<figure><img src="/files/HUkarYgzepFZiUfr2sM1" alt=""><figcaption></figcaption></figure>

Once the SDK is initialized, request an ad and confirm you see **test ads**. That’s it — you're integrated!&#x20;

{% hint style="info" %}
**Don’t forget:** Disable test mode before going live to start receiving live ads.
{% endhint %}

## Need Help? <a href="#need-help" id="need-help"></a>

If you have any questions, your HyprMX account manager is just a message away!

## License <a href="#license" id="license"></a>

By integrating the HyprMX SDK, you are agreeing to the [End User License Agreement](https://hyprmx.com/eula.html).


---

# 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, and the optional `goal` query parameter:

```
GET https://documentation.hyprmx.com/sdk-integration-guides/ios/3rd-party-mediation/applovin-max.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.