Help Center

Testing

After adding a new app to Appodeal and integrating SDK, we recommend testing your app. Here are the tips for successful testing.

Integration Review

Step 1: Prepare Settings On Appodeal Side 

Check The Mediation Settings

Go to Application Settings →  Mediation Settings →  Line Items. 



Choose the ad type you are interested in and check the network connection.

In the Line Items section, you can see the rules for networks automatically connecting. Once you reach all the requirements, networks will be connected automatically using the Appodeal default account. Example:

For new applications, a few networks will be connected by default if the Appodeal server receives a request for the ad type.
If you see “This network will be activated by ad request.” try to request real ads to activate this network using the Appodeal default account.

Make sure you have at least 2-3 enabled networks. If the requirements for automatic networks connection are not reached, link a personal account using Networks Setup to have more networks connected.

Make sure the ad units are enabled for the connected networks:

Check Priorities (Waterfall Configuration)

Go to Application settings →  Mediation Settings → Priorities, choose the ad type.



By default, there is only a default priority configuration for the waterfall, where all ad units from connected networks are placed.
Make sure the line items have been added to your current configuration.



If they haven’t, add them in the configuration by drag and drop the ad units from the Unused Line Items list on the left to Automatic Priority.

Step 2: Test Your SDK Integration

Check SDK Integration With Test Ads.

Test mode ads have a 100% fill rate, they are loaded almost immediately comparing real ads, which loading can take some time (0-30 seconds depends on the ad type).

  1. Enable test mode.
  2. Enable SDK logging 
  3. Make sure that all necessary adapters have been integrated into the app. It’s required to have all adapters marked by a star in Mediation Wizard for getting test ads.
  4. Run the app and go to all placements where you added ads. Make sure they are loaded and shown successfully.
  5. Open the logs tab and check Appodeal SDK logs.

Requests for test ads are not counted as real requests, meanwhile, Appodeal needs at least one real request for automatically activating networks for the ad type.

Check SDK Integration With Real Ads.

We recommend testing apps using test mode to prevent invalid activity on real ads. However, it's necessary to make sure SDK integration is correct and all networks are ready to use.

  1. Disable test mode by commenting out the method you used to enable it.
  2. Check that the logging of Appodeal SDK is enabled.
  3. Make sure that all necessary adapters for the networks you plan to use were integrated. For more information please visit the Mediation Wizard.
  4. Open your application and initialize SDK to make a request to activate the ad networks. You can see all the activity of our SDK in the logs by the Appodeal tag.
  5. When networks’ set up is ready, run the app again and open the logs console. Make sure there are no errors in the logs. Use the SDK logging to analyze Appodeal logs. Go through all placements where you added ads. Make sure they are loaded and shown successfully with no exceptions and errors.

If your app is not published in one of the supported app stores (Google Play, App Store, Amazon), then the number of impressions of live ads is restricted to two thousand.

Useful SDK Methods

Enable Test Mode

Using test mode allows you to get our test ad creatives with 100% fill rate. 

Appodeal.setTesting(true);

Enable Logging

SDK logging allows you to check SDK integration and activity, including information about waterfalls with ad units, ads requesting, loading, and some other. We recommend always enabling logs and use the verbose log level to get full SDK information. 

To enable debug logging, use the code below: 

Appodeal.setLogLevel(Log.LogLevel.verbose);
Logs will be written to logcat using the Appodeal tag.

Available parameters:

  • Log.LogLevel.none logs off;
  • Log.LogLevel.debug debug messages;
  • Log.LogLevel.verbose all SDK and ad network messages.


Connect a device with the app installed, open the Android Studio Logcat console, run the app and check SDK logs by the Appodeal tag. 
For more information about the console please visit Debugging with Android Studio.

Test Third-Party Network Adapters Integration

You can use our Test Activity for manual testing adapters integration.

To start Test Activity call: 

Appodeal.startTestActivity(activity);

Disable Networks

Appodeal.disableNetwork(context, "NETWORK_NAME");
You can find all available NETWORK_NAME in AppodealNetworks.

Important

Should be called before the SDK initialization.


Disable Networks For Specific Ad Types

Appodeal.disableNetwork(context, "NETWORK_NAME", adTypes);
Example: 
Appodeal.disableNetwork(context, AppodealNetworks.ADMOB, Appodeal.BANNER | Appodeal.INTERSTITIAL);

Important

Should be called before the SDK initialization.