Native Validator

AI-generated Key Takeaways

• Custom rendering allows for flexible ad placement design but must adhere to Ad Manager policies.

• Native Validator, enabled by default for test ads, automatically detects policy violations and provides feedback through the app's UI.

• Google Mobile Ads SDK 7.68.0 or higher and a configured test device are prerequisites for using Native Validator.

• Native Validator can be disabled by setting GADNativeAdValidatorEnabled to false in the Info.plist.

Select platform: Android iOS

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

• Google Mobile Ads SDK 7.68.0 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, add GADNativeAdValidatorEnabled = false to your Info.plist.

<key>GADNativeAdValidatorEnabled</key>
<false/>

Or, edit it in the property list editor: