Native validator

Custom rendering lets you design an ad placement that matches the style of your app. While this provides a lot of flexibility, it's important to ensure your placements remain compliant with Ad Manager policies.

Native Validator is a new feature to help you catch policy violations before your app ships. It automatically identifies certain policy violations in your app and notifies you through the app's UI.

Key Point: Native Validator will appear only on test ads. Live ad requests will never show Native Validator.

Native Validator is enabled by default for test ads, but can be disabled as shown below. Keep in mind however that once the validator is disabled, test ads will no longer show information about potential issues with your ad layouts.

Prerequisites

• Next Gen Mobile Ads SDK 0.11.0-alpha01 or higher.

• Ensure your device is configured as a test device.

Using Native Validator

Native Validator automatically alerts you of certain policy violations in your UI through an overlay popup next to the ad.

Clicking on See Issues takes you to a fullscreen list of the relevant policy violations.

Disabling the validator

To disable Native Validator, call setNativeValidatorDisabled() when initializing Next Gen Mobile Ads SDK :

Kotlin

MobileAds.initialize(
  this@MainActivity,
  // Sample Ad Manager app ID: ca-app-pub-3940256099942544~3347511713
  InitializationConfig.Builder("SAMPLE_APP_ID")
    .setNativeValidatorDisabled()
    .build()
  ) {
    // Adapter initialization is complete.
}

Java

MobileAds.initialize(
    this,
    // Sample Ad Manager app ID: ca-app-pub-3940256099942544~3347511713
    new InitializationConfig.Builder("SAMPLE_APP_ID")
        .setNativeValidatorDisabled()
        .build(),
    initializationStatus -> {
        // Adapter initialization is complete.
    });