Installing and configuring the plugin
Integration Guide.
Last updated
Integration Guide.
Last updated
Release version 1.4.1 | Release date 05/15/2025
Use our demo application as an example.
To install the Unity Plugin, you will need:
Check out the demo application
Download and import the latest version of the plugin into your project.
Configure External Dependency Manager
Check the installation correctness by initializing the plugin with debug mode enabled
Import the plugin into your project using the Custom Package option.
The plugin includes the External Dependency Manager.
You may not import it if it has already been installed in the project.
External Dependency Manager is a plugin for resolving dependency conflicts
To resolve dependency conflicts in your application, follow these steps:
Navigate to Build Settings → Android → Player Settings → Publishing settings
For Unity 2018.4 - Unity 2019.2: add the Custom Gradle Template flag
For Unity 2019.3 or newer: add the Custom Main Gradle Template flag
Go to External Dependency Manager → Android Resolver → Settings
Enable the Patch mainTemplate.gradle setting
Enable the Use Jetifier setting
Select the Force Resolve option in External Dependency Manager → Android Resolver → Force Resolve
If the dependencies are installed successfully, you will see the Resolution Succeeded alert
If code obfuscation is enabled in your application, then add the following text to the end of the file proguard-rules.pro:
If you are using an adapter for Applovin, then follow these steps for the platform you are working with// Some code
If you are using an adapter for Applovin, then add the following <meta-data> element to your AndroidManifest.xml inside the <application> element:
To make sure that the plugin is installed correctly, you will need to enable debug mode and initialize the plugin.
In debug mode the plugin logs errors and events. It is disabled by default.
Use the EnableDebug method to enable debug mode.
Inherit the class that will work with the SDK from the interface for tracking SDK initialization.
If the plugin is installed correctly, you will see the following message in the console.
This message indicates that the plugin is installed correctly, but ad display is only possible after building the application for Android/iOS.
We recommend that you don't disable debug mode until you finish working with ads.
In case of errors, we recommend clearing the External Dependency Manager cache and selecting Force Resolve in External Dependency Manager → Android Resolver.
If this doesn't help, try installing the plugin in a clean project. If the plugin is installed correctly, try to debug errors in your project.
If you are unable to install the plugin correctly and the above steps didn't lead to successful initialization, please contact support.
If you are using Madex mediation (working with other ad networks through our plugin):
Import the file into the project received from the Madex account manager (drag and drop the file into the project or use the Custom Package option)
Select the Force Resolve option in External Dependency Manager → Android Resolver → Force Resolve
Check for an update before building the app.
The Madex Unity Plugin provides a convenient interface for updating the plugin and managing ad networks. In the Dependency Manager window, you can update the plugin to the latest version and choose the ad networks you want to use.
It is determined automatically, but in some cases, Madex Unity Plugin may not be able to determine it.
If Madex Unity Plugin did not determine your App ID, you will see the following message in the console.
In this case, you need to set the ID manually.
To set up Apple ID, use the setCustomParams method.
For more effective targeted advertising and increased revenue, you can collect the Apple device advertising identifier and pass it to Madex Unity Plugin.
To enable IDFA collection, check the following checkboxes in the plugin setting:
NSUserTrackingUsageDescription - Permission to collect the advertising identifier (Advertising Identifier IDFA).
To make targeted ads work more effectively and increase revenue, you can collect in app data about a user's exact and/or approximate geolocation, and feed it into the Madex Unity Plugin.
To enable geolocation data collection on Android, check the following checkboxes in the plugin settings:
ACCESS_COARSE_LOCATION - Permission to collect approximate user geolocation.
ACCESS_FINE_LOCATION - Permission to collect precise user geolocation.
In order to comply with the requirements of the app store and the laws governing the collection, processing and use of user's personal data, it is required to obtain his consent to the above actions.
Usually, the user's consent is obtained on a special screen when the application is first launched — consent-screen.
The Madex Unity Plugin implements such a screen, you can add and configure it using the Content Manager library.
You can find out more about its installation and configuration in the corresponding section.
Download the latest version of the plugin at the .
You can copy your APPLOVIN_SDK_KEY in the "Keys" section of your Applovin.
You can copy your APPLOVIN_SDK_KEY in the "Keys" section of your Applovin .
Use the code below to initialize the plugin in your project.
You can copy your publisher_id in the "Settings" section of your Madex .
Done! The plugin is installed, you can proceed to .
We also recommend to take a look at the installation and initialization in the .
For more effective targeted advertising and increased revenue, Madex Unity Plugin collects and transmits user data - a unique numerical application identifier from the Apple AppStore.
Replace apple_id with your App ID from the AppStore developer account. You can find it on the app page in the .
The error occurs due to the peculiarities of xcframework linking in Unity. In order to fix the error, you need to download MadexPostProcessBuildiOS.cs from this and place it in the scripts folder or in another folder for your scripts.
