If you are using mediation extras to pass in user ID and/or user consent, follow the instructions in Optional: User ID & User Consent. HyprMXMediationExtras has been removed and replaced with HyprMXAdapterConfiguration
The following section details how to use the Android HyprMX AdMob Adapter. This guide assumes you already have your gradle-based project up and running in Android Studio with AdMob Mediation.
Open your existing application in Android Studio
Add the following dependency to your app's build.gradle file:
In the parameter field, enter the distributor ID and placement name assigned to you by your HyprMX account manager. Please reach out to your account manager with what placements you'd like to use in your app and whether they will be rewarded or interstitial. The example below will assume that your account manager has created a "REWARDED" placement.
Tagging for child directed treatment is recommended for all users within applications that participate in Google Play’s Designed for Families program, are listed in Google Play’s Family section, or include children as one of the target audiences to prevent access to the AAID for end-users flagged as children.
If your app relies on server-to-server callbacks and requires you to set a static user ID that is publisher-defined for Rewarded Video, pass the user ID as instructed below. Please contact your HyprMX account services representative if you would like to implement a postback.
The user ID should not contain personal information such as an email address, screen name, or Google's Advertising Identifier (GAID).
HyprMX also allows you to set the user's consent status for jurisdictions that require passing consent using the setHasUserConsent API. Options are true for consent given or false for consent declined. Not setting consent will leave the status as UKNOWN.
Pass the user ID and consent status with the HyprMXAdapterConfiguration before initializing AdMob.