Test Mode

You can use Test Mode to verify that specific ad networks have been successfully integrated. Test Mode increases the likelihood that you receive ad fill during testing. The simplest way you can enable it is by opening the Mediation Debugger and enabling test ads. Alternatively, you can enable it programmatically, as shown below.

Note

AppLovin does not track impressions, clicks, or revenue for test ads. Use test ads only to test your app integration.

Note

When you enable test mode, the MAX SDK outputs verbose device logging to your IDE’s console.

How to Enable Test Mode Programmatically

You can enable test ads for one or more devices by programmatically passing their test device advertising IDs in the AppLovin SDK.

To do this, pass a list of GAIDs in AppLovinSdkInitializationConfiguration as shown below. You must set test GAIDs when you create the first SDK instance. The following code snippets demonstrate how to do this:

Java

AppLovinSdkInitializationConfiguration initConfig = AppLovinSdkInitializationConfiguration.builder( "«SDK-key»" )
  .setMediationProvider( AppLovinMediationProvider.MAX )
  .setTestDeviceAdvertisingIds( Arrays.asList("«your-GAID»") )
  .build();

Kotlin

val initConfigBuilder = AppLovinSdkInitializationConfiguration.builder("«SDK-key»")
  .setMediationProvider(AppLovinMediationProvider.MAX)
  .setTestDeviceAdvertisingIds(Arrays.asList("«your-GAID»"))
  .build()

You can find your SDK key in the Account > General > Keys section of the AppLovin dashboard.

Troubleshooting

To verify that you enabled Test Mode successfully, check for the line that reads Test Mode On: true in the initialization section of the AppLovin SDK logs:

AppLovin SDK
Version: 13.2.0
⋮
Test Mode On: true
⋮

If test ads do not load, try loading live ads. No fills are common during testing and typically do not indicate issues with your integration.