unity-admob

Unity AdMob Rewarded Ad Implementation Skill

Purpose

Implement a Google AdMob rewarded ad system with GDPR consent handling (UMP SDK). The architecture uses a callback-based request pattern: callers pass reward/failure callbacks through an event, and AdManager handles the ad lifecycle transparently.

When to Use

• Adding rewarded video ads
• Integrating Google Mobile Ads SDK
• Setting up GDPR consent (UMP SDK)
• Refactoring direct AdManager references to event-based communication
• Adding ad-gated features (watch ad to unlock, skip timer, etc.)

Architecture Overview

App Start
    |
    v
ConsentManager.RequestConsent()
    |
    v (consent complete)
MobileAds.Initialize()
    |
    v
LoadRewardedAd()  <---- auto-reload after each show
    |
    v
_adReadyVariable = true
    |
[User taps ad button] (only enabled when adReady == true)
    |
    v
Event.Raise(new AdRequest(onRewarded, onFailed))
    |
    v
AdManager.Show() --> OnUserEarnedReward --> request.OnRewarded()
                 --> OnAdFailed          --> request.OnFailed()

Key Principles:

• Callers never reference AdManager directly
• Communication via event carrying an AdRequest DTO with callbacks
• BoolVariable exposes ad readiness for UI button state
• ConsentManager runs before any ad initialization
• Auto-reload after each ad show or failure

Implementation Steps

Step 1: Install Google Mobile Ads Plugin

Import Google Mobile Ads Unity Plugin via .unitypackage or UPM. Configure GoogleMobileAdsSettings asset with App IDs.

Step 2: Create AdRequest DTO

A plain C# class carrying callbacks:

using System;

public class AdRequest
{
    public Action OnRewarded { get; }
    public Action OnFailed { get; }

    public AdRequest(Action onRewarded, Action onFailed = null)
    {
        OnRewarded = onRewarded;
        OnFailed = onFailed;
    }
}

Step 3: Create ConsentManager

Handles UMP SDK consent flow before ad initialization:

public class ConsentManager : MonoBehaviour
{
    private Action _onConsentCompleted;

    public void RequestConsent(Action onConsentCompleted)
    {
        _onConsentCompleted = onConsentCompleted;
#if UNITY_ANDROID || UNITY_IOS
        var requestParameters = new ConsentRequestParameters();
        ConsentInformation.Update(requestParameters, OnConsentInfoUpdated);
#else
        _onConsentCompleted?.Invoke();
#endif
    }
    // ... platform-specific consent form handling
}

Step 4: Create AdManager

Core lifecycle:

1. Awake() - Set _adReadyVariable = false
2. Start() - Call _consentManager.RequestConsent(InitializeAds)
3. OnEnable() - Subscribe to ad request event
4. OnDisable() - Unsubscribe from ad request event

Critical patterns:

• InitializeAds() - MobileAds.Initialize(), then LoadRewardedAd()
• LoadRewardedAd() - Destroy old ad, set ready=false, load new one
• HandleAdRequest(AdRequest) - Store request, call _rewardedAd.Show()
• On reward callback: _currentRequest.OnRewarded?.Invoke()
• On failure/close: auto-reload next ad
• Exponential backoff retry (max 3 attempts)

Step 5: Wire Up Ad Callers

Each caller (popup, button, etc.) needs:

• Reference to the ad request event
• Reference to _adReadyVariable for button enable/disable
• Pattern: event.Raise(new AdRequest(onSuccess, onFailure))

Step 6: Editor Mock Support

In #else (non-mobile) blocks, simulate ad success:

#else
    Debug.Log("[AdManager] Editor mode - simulating ad success.");
    _currentRequest?.OnRewarded?.Invoke();
    _currentRequest = null;
#endif

Set _adReadyVariable = true in editor mode so buttons are enabled.

Step 7: Ad Unit IDs

Use test IDs during development:

#if UNITY_ANDROID
    private const string AD_UNIT_ID = "ca-app-pub-3940256099942544/5224354917"; // Test
#elif UNITY_IOS
    private const string AD_UNIT_ID = "ca-app-pub-3940256099942544/1712485313"; // Test
#endif

Pre-release: Replace with real Ad Unit IDs from AdMob console.

Step 8: GoogleMobileAdsSettings

Configure Assets/GoogleMobileAds/Resources/GoogleMobileAdsSettings:

• AdMob Android App Id: ca-app-pub-XXXXX~XXXXX
• AdMob iOS App Id: ca-app-pub-XXXXX~XXXXX

Important: App ID uses ~ (tilde), Ad Unit ID uses / (slash).

Step 9: Create Inspector Setup Guide

Document all SerializeField assignments, SOAP asset creation, and pre-release checklist.

Communication Patterns

With SOAP (Recommended for SOAP projects)

Create ScriptableEvent<AdRequest> subclass. See references/implementation-patterns.md.

Without SOAP

Use C# events or direct reference:

// Direct reference approach
adManager.ShowRewardedAd(new AdRequest(onReward, onFail));

// Or static event approach
AdManager.OnAdRequested?.Invoke(new AdRequest(onReward, onFail));

Common Pitfalls

Pitfall	Solution
Ad buttons active when no ad loaded	Gate buttons on _adReadyVariable.Value == true
Consent form blocks forever	Add timeout, invoke callback on error too
Ads don't work in Editor	Use #if UNITY_ANDROID || UNITY_IOS guards, simulate in else block
Mock ad panel blocks input	Set CanvasGroup blocksRaycasts = false and Image raycastTarget = false when hidden
Ad not reloading after show	Register OnAdFullScreenContentClosed to trigger LoadRewardedAd()
First ad takes long to load	Start loading in Start() via consent flow, not on first request

Additional Resources

Reference Files

• references/implementation-patterns.md - Complete code templates with SOAP and non-SOAP variants