AppLovin MAX
The legacy MAX HyprMX adapter is being sunset. Migrate to the custom adapter today to avoid any disruption to monetization
Introduction
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
Rewarded Ads
Interstitial Ads
Banner/MREC
Compatibility
HyprMX-MAX Adapter Version: 6.4.3.0
Compatible with AppLovin SDK: 12.4.0+
If you need support for older AppLovin versions, your HyprMX account manager is here to help.
Step 1: Add HyprMX as a Custom Network
In the MAX Dashboard, go to: MAX > Mediation > Manage > Networks.
Click "Click here to add a Custom Network" at the bottom of the page. The "Create Custom Network" page appears.
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
Press Save to create the SDK network.
Step 2: Create Ad Units
💡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:
Open MAX > Mediation > Manage > Ad Units in the MAX dashboard.
Click the ad unit where you want to enable HyprMX.
Scroll down to the Custom Networks section and enable HyprMX.
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
If you're migrating from the legacy adapter, disable the legacy adapter under the Other Networks section.
Important: Avoid Adapter Conflicts
To ensure smooth monetization and prevent issues, only one HyprMX adapter (legacy or custom) should be active at a time.
Save and repeat these steps for each Ad Unit you'd like to configure.
💡Migrating from the MAX Legacy Adapter?
If you’re not yet ready to go live with the custom adapter:
Temporarily disable the HyprMX custom adapter before clicking Save.
This lets you save any configuration changes and come back later to complete the setup.
If you’ve already completed Step 5, remember to re-enable the legacy adapter to avoid disrupting monetization.
When you're ready to go live with the custom adapter:
Disable the legacy adapter, enable the custom one, and then Save.
Having both adapters enabled at the same time can cause delivery conflicts and impact revenue.
Step 3: Install Custom Adapter
This guide assumes you already have the AppLovin Android SDK integrated into your project. If not, refer to the AppLovin integration guide before proceeding.
Follow these steps to install the HyprMX custom adapter via CocoaPods:
Make sure you’re using CocoaPods version 1.10.2 or newer.
If you're migrating from the legacy adapter, remove the following line from your Podfile to upgrade the adapter files:
pod 'AppLovinMediationHyprMXAdapter'Add the following to your Podfile:
pod 'HyprMX-Max', '6.4.3.0'Step 4: Test and Verify Integration
You can receive test ads by enabling test mode. When using the custom adapter, enable test mode before initializing MAX:
import HyprMX_Max // At top of same file
HyprMXAdapter.enableTestMode() // Before initializing AppLovin MAX SDKWe recommend putting HyprMX at the top of your waterfall during testing to ensure you receive ad requests.
Once the SDK is initialized, request an ad and confirm you see test ads. That’s it — you're integrated!
Need Help?
If you have any questions, your HyprMX account manager is just a message away!
License
By integrating the HyprMX SDK, you are agreeing to the End User License Agreement.
Last updated