MonetizePro

What Is MonetizePro?

MonetizePro is a UE4 C++ Runtime plugin that adds ad monetization to games without writing platform-specific code. Define your ad units once in Project Settings, then load and show any ad format from Blueprint in one node.

Features

System Requirements

Installation

1. Copy the plugin folder Place the MonetizePro folder inside your project's Plugins/ directory. The MonetizePro.uplugin file must be at the root.
2. Enable in the Editor Main menu → Edit → Plugins → search MonetizePro → tick Enabled → click Restart Now.
3. C++ projects only Add the module to your game's Build.cs:

   PrivateDependencyModuleNames.Add("MonetizePro");

   Blueprint-only projects skip this step.
4. Verify Main menu → Edit → Project Settings → Plugins → MonetizePro should appear. If it does, the plugin is active.

Project Settings

All runtime configuration lives here. Changes are saved to Config/DefaultMonetizePro.ini and can be source-controlled.

Ad Unit Registry

Each row in the Ad Units array represents one placement in your game. Give it a unique name, choose its format, and fill in the platform-specific IDs.

Example entries

// Project Settings → Ad Units — example rows

Row 0:  Name = "HomeScreen_Banner"       Type = Banner
        Android = "ca-app-pub-3940256099942544/6300978111"  ← test ID
        iOS     = "ca-app-pub-3940256099942544/2934735716"

Row 1:  Name = "GameOver_Interstitial"   Type = Interstitial
        Android = "ca-app-pub-3940256099942544/1033173712"
        iOS     = "ca-app-pub-3940256099942544/4411468910"

Row 2:  Name = "ExtraLife_Rewarded"      Type = Rewarded
        Android = "ca-app-pub-3940256099942544/5224354917"
        iOS     = "ca-app-pub-3940256099942544/1712485313"

AdMob — Android

The Android SDK is injected automatically by UPL. No manual download is required.

What UPL_Android.xml injects

1. Set your App ID
   Project Settings → MonetizePro → AdMob App ID (Android)
2. Keep Test Mode on during development. Use the official Google test unit IDs (see Test Mode section).
3. Package for Android — Gradle will pull the SDK automatically during the build.

AdMob — iOS

The real SDK binaries are already bundled inside the plugin. No download is needed.

System frameworks linked automatically

1. Set your App ID
   Project Settings → MonetizePro → AdMob App ID (iOS)
2. Update ATT description
   Open Private/Platform/UPL_IOS.xml and edit NSUserTrackingUsageDescription to describe your app's tracking usage.
3. Build on macOS
   Requires macOS 13+ and Xcode 16+. iOS builds cannot be packaged from Windows.

AdsJumbo — Win64

The header interface is included. The binary files must be obtained from adsjumbo.com/developers and placed in the correct folders.

Auto-detection logic in Build.cs

You never need to edit Build.cs. The plugin compiles cleanly in stub mode (logged no-ops) until the real binaries are present.

Getting the Subsystem

The subsystem is your single entry point for all ad operations. It is created automatically when the game instance starts — you never construct it manually.

In any Blueprint: right-click graph → search MonetizePro → select Get MonetizePro Subsystem

Events

Bind these delegates in Begin Play before loading any ads. All events are delivered on the Game Thread.

Banner Ads

Recommended flow

Interstitial Ads

Full-screen ads shown at natural transition points. Pre-load during idle time so the ad is ready instantly when needed.

Rewarded Ads

Opt-in videos the user watches in exchange for in-game items. The reward is only granted after the video plays fully.

Callback order

Best practice flow

Rewarded Interstitial

Like rewarded ads but shown without the user opting in. Reward is still delivered via OnRewardGranted. Requires AdMob account allowlisting.

App Open Ads

Shown when the user brings the app to the foreground. Pre-load on startup, show on OnApplicationReactivated.

Native Ads

Native ads load ad data; you render it using your own UMG widgets. MonetizePro fires OnAdLoaded when data is ready.

Utility Nodes

These are pure (no execution pin) Blueprint nodes callable anywhere.

// C++ equivalent — same result as the Blueprint pure node
bool bSupported = UMonetizeProBPLibrary::IsMonetizationSupported();
FString UnitId   = Sub->GetAdUnitId(FName("ExtraLife_Rewarded"), EAdType::Rewarded);

Ad Formats

Banner Sizes

Platform Support Matrix

* Win64 requires AdsJumbo.lib + AdsJumbo.dll in ThirdParty. Without binaries, calls are safe no-ops.

Privacy & Compliance

GDPR

Call Set GDPR Consent before the first ad load. You are responsible for showing your own consent dialog and passing the result.

COPPA

Call Set COPPA Compliance (true) before the first ad load for child-directed apps. This disables personalised ads and location targeting for all users of that app instance.

ATT — iOS 14+

The NSUserTrackingUsageDescription string in UPL_IOS.xml drives the iOS system ATT prompt. Update this string to accurately describe your tracking usage before submitting to App Store review.

Test Mode

Project Settings → Debug → Test Mode (default: true). Use Google's official test unit IDs while developing.

Logging & Debugging

Common messages

// Provider not configured
"No provider matched for current platform/config. Falling back to NullProvider."
→ Set Active Ad Provider in Project Settings

// Name not found in registry
"Ad unit 'ExtraLife_Rewarded' (type 3) not found in Project Settings."
→ Check spelling and Ad Type match in Project Settings → Ad Units

// AdsJumbo SDK missing
"[AdsJumboProvider] SDK binaries not found."
→ Place AdsJumbo.lib + AdsJumbo.dll in ThirdParty/AdsJumbo/Win64/Lib/ and /Bin/

// No provider set
"[NullAdProvider] LoadBanner called — no active provider configured."
→ Set Active Ad Provider in Project Settings → Provider

File Structure

Architecture

Callback data flow

1. Blueprint calls LoadRewarded("ExtraLife_Rewarded") on the subsystem.
2. Subsystem resolves the name → platform Unit ID string via ResolveAdUnitId().
3. Subsystem forwards to the active IAdProvider implementation.
4. Native SDK fires a callback (potentially on a background thread).
5. Provider wraps it in AsyncTask(ENamedThreads::GameThread, …) and calls the bound TFunction<>.
6. Subsystem broadcasts the DYNAMIC_MULTICAST_DELEGATE — Blueprint receives the event safely on the Game Thread.

Changelog