Creative Debugger

With the AppLovin MAX SDK, you can expose comprehensive ad information in MAX-mediated apps. You can identify problematic ads when you incorporate the creative debugger into your test environments, QA processes, and support ticket systems.

The creative debugger displays a button in the application for five seconds when you complete a special gesture (described in the video below). If you then press the button that appears, you will see a new screen that contains a list of recently displayed ads. If you select an ad from this list, information displays about that ad (such as its mediated network and creative ID), so you can report creative issues for that ad.

This gesture is available for full-screen ads only. It is enabled by default for both development and production builds.

To report any issues with ads and to get help from the associated ad network, select the problematic ad and click the Report button, which creates an ad issue report. Send this report to the appropriate ad network partner. For issues with AppLovin ads, send this report to your account manager or submit a ticket to AppLovin Support.

Disabling the Creative Debugger

The following code shows you how to disable the creative debugger with the MAX SDK:

UAppLovinMAX::SetCreativeDebuggerEnabled(false);

Creative ID

You can also retrieve the creative ID of displayed ads of various mediated networks. You can do this either by using the creative debugger, or by using the MAX SDK. The following code shows you how to do this with the MAX SDK:

  • On Interstitial Ad Displayed Dynamic Delegate (AppLovinMAXDelegate): Ad Info. Break AdInfo: Ad Info, Ad Unit Identifier, Network Name, Creative Identifier, Placement, Revenue.
  • UAppLovinMAX::OnInterstitialAdDisplayedDelegate.AddLambda([](const FAdInfo &AdInfo)
    {
      FString CreativeId = AdInfo.CreativeIdentifier;
    });

The table below indicates which ad networks, ad formats, and adapter versions support this feature. The Ad Callback column shows you in which ad callback the creative ID becomes available.

Ad Network Ad Formats Ad Callback Android Adapter Version iOS Adapter Version
* Interstitial, MREC, Native, and Rewarded bidding ads are officially supported, on Android only, starting from version 22.5.0.0 of Smaato’s Android adapter.
AppLovin Interstitial, Rewarded Ad Loaded 9.15.0 6.15.0
Amazon Banner, Interstitial, MREC, Rewarded Ad Loaded 9.6.2.1 4.5.6.1
BidMachine Banner, Interstitial, MREC, Native, Rewarded Ad Loaded 1.9.4.2 1.9.4.1.2
Chartboost Interstitial, Rewarded N/A N/A 8.4.0.1
DT Exchange Banner, Interstitial, Rewarded Ad Displayed 7.7.4.1 7.8.0.1
Google Ad Manager Banner, Interstitial, Rewarded Ad Loaded 19.6.0.2 7.69.0.1
Google bidding and Google AdMob Banner, Interstitial, Rewarded Ad Loaded 19.6.0.2 7.69.0.1
InMobi Banner, Interstitial, Rewarded Ad Loaded 9.1.1.3 9.1.1.1
Liftoff Monetize Banner, Interstitial, MREC, Native, Rewarded Ad Displayed 6.10.1.0 6.8.1.3
Ad Loaded 7.1.0.0 7.2.0.0
Meta Audience Network Banner, Interstitial, Rewarded Ad Loaded All All
Mintegral Banner, Interstitial, Rewarded Ad Loaded 15.4.31.1 6.7.5.0.1
Pangle Banner, Interstitial, Rewarded Ad Loaded All All
Smaato Banner, Interstitial,* MREC,* Native,* Rewarded* Ad Loaded 21.5.7.1 21.6.10.1

Network Name

You can also retrieve the name of the ad network that is responsible for an ad. The following code shows you how to do this with the MAX SDK:

  • On Interstitial Ad Displayed Dynamic Delegate (AppLovinMAXDelegate): Ad Info. Break AdInfo: Ad Info, Ad Unit Identifier, Network Name, Creative Identifier, Placement, Revenue.
  • UAppLovinMAX::OnInterstitialAdDisplayedDelegate.AddLambda([](const FAdInfo &AdInfo)
    {
      FString NetworkName = AdInfo.NetworkName;
    });