Disclosure: This website contains affiliate links, which means we may receive a commission if you click a link and purchase something through our website. Purchasing assets through our links won’t cost you any extra money and will help fund the hosting and development of this site.


Mobile Ads (GDPR Compliant)

Key features:

- Integrate easily all supported advertisers simply by importing their SDK, no other settings are required. It is not mandatory to integrate all/any of the supported advertisers to work.

- Load ad from any ad platform using the same line of code.

- Customizable mediation policy by using either order mediation or percent based mediation.

- Read mediation config file from an external server of choice to allow the ad display order to be changed without uploading a new build to the store.

- Works for Android, iOS and Windows store.(Vungle SDK currently has some problems with Unity versions 2017.3 and above for Windows builds)

- Built in Remove Ads functionality.


Currently supported advertisers:

AdColony
AdMob
AppLovin *NEW*
ChartBoost
Heyzap
UnityAds
Vungle

Supported ad types:

Banner
Interstitial
Video Reward

GDPR Compliance:

Our plugin does not collect any personal information only selected advertisers collect personal information about users. Here is a list of how any advertiser deals with personal user data and what you have to do to be compliant with GDPR:


Unity Ads

- Versions 2.0 and above will automatically present users with an opportunity to opt-out of targeted advertising, with no implementation needed from the publisher. On a per-app basis, the first time a Unity ad appears, the user will see a banner with the option to opt-out of behaviorally targeted advertising. Thereafter, the user can click an information button to receive the opt-out again.

- No specific action needed.



Vungle

- Vungle will display a consent dialog before playing an ad for a European user, and will remember the user’s consent or rejection for subsequent ads.

- No specific action needed.



Admob, AdColony, AppLovin, Heyzap

- All require that implementation of getting user consent for receiving targeted ads to be made by publisher in his application and then to be sent to their SDK(Admob, AdColony, Heyzap).

- If the application user does not accept the compliance they will keep serving ads but it will not be targeted anymore.

- Getting consent from the user is needed to display ads in order to be compliant with GDPR.



Chartboost

- Chartboost requires that implementation of getting user consent for receiving targeted ads to be made by publisher in his application and then sent to Chartboost SDK.

- If the application user does not accept the compliance Chartboost SDK will not provide any ads.

- Getting consent from the user is needed to display ads in order to be compliant with GDPR.



COPPA Compliance:

Your app needs to be COPPA compliant if is made for children under the age of 13. That means such an app is not allowed to to collect any data from its users.

Each advertiser we support has his own COPPA policy.

For Admob, AppLovin and Heyzap you have to check the box in our Settings Window.

For other advertisers you have to set COPPA compliance on their dashboard.

More details about COPPA can be found in our forum post.



Upgrade guide:

If you want to upgrade from v1.1.2 or lower to current version you have to manually delete the old version by removing this folder: Assets/GleyPlugins/Ads and only after import the new package. You will lose your advertiser settings so you will have to setup your id`s again in the Settings Window. This upgrade is not mandatory for your ads to work.



For detailed implementation example of how to get user consent and how to set up Mobile Ads to be compliant with GDPR

See the forum



For detailed instructions check the Documentation


Android Demo


For any questions:

Contact us


Changes in 1.3.5:

Fixed some error messages from Admob in multithreading apps.


Changes in 1.3.4:

Fixed manifest bug when not using Admob.

Updated Vungle implementation to support SDK version 6.3.0.


Changes in 1.3.3:

Settings window refresh fixed when using Admob ads.

Better manifest handling.


Changes in 1.3.2:

Support for Unity Monetization 3.0.0 that includes banner ads(banner ads are not available yet all over the world).

Support for android.gms.play-services-ads-17 and above.

Updated plugin to support Chartboost SDK v7.3.0.

Fixed some mediation file related bugs.


Changes in 1.3.1:

Resumed support for Vungle on Android.

Fixed warnings displayed in Unity Editor.


Changes in 1.3.0:

AppLovin support added.


Changes in 1.2.0:

Remove Ads functionality added.


Changes in 1.1.10:

Fixed bug when changing the GDPR consent from inside app after initialization.


Changes in 1.1.9:

Added advertiser parameter in OnComplete method for better tracking of ad network performance when using mediation.


Changes in 1.1.8:

Fixed a bug with Admob integration on multithreading apps.


Changes in 1.1.7:

Added methods to show ad from specific advertiser, so now mediation settings can be override at specific points in the app.


Changes in 1.1.6:

COPPA compliance added.


Changes in 1.1.5:

Changed Admob implementation to fix some banner load problems.

Better Admob banner fill rates with this version.

Support for banner and smart banner added.


Changes in 1.1.4:

Fixed Settings Window errors on some Unity versions.

Fixed Chartboost id`s bug on iOS.


Changes in 1.1.3:

New and easy to use Settings Window.

Independent mediation for interstitial and rewarded video.


Changes in 1.1.2:

Fixed a bug when no callback for Unity Ads interstitial is set.


Changes in 1.1.1:

Added GDPR compatibility for all supported advertisers.


Changes in 1.1.0:

Fixed banner switch from top to bottom on the same scene.

Fixed OnCompleteMethod bug when rewarded video was skipped.