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.
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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[[["\u003cp\u003eCustom rendering allows for flexible ad placement design but must adhere to Ad Manager policies.\u003c/p\u003e\n"],["\u003cp\u003eNative Validator, enabled by default for test ads, automatically detects policy violations and provides feedback through the app's UI.\u003c/p\u003e\n"],["\u003cp\u003eGoogle Mobile Ads SDK 7.68.0 or higher and a configured test device are prerequisites for using Native Validator.\u003c/p\u003e\n"],["\u003cp\u003eNative Validator can be disabled by setting \u003ccode\u003eGADNativeAdValidatorEnabled\u003c/code\u003e to \u003ccode\u003efalse\u003c/code\u003e in the \u003ccode\u003eInfo.plist\u003c/code\u003e.\u003c/p\u003e\n"]]],[],null,["Select platform: [Android](/ad-manager/mobile-ads-sdk/android/native/validator \"View this page for the Android platform docs.\") [iOS](/ad-manager/mobile-ads-sdk/ios/native/validator \"View this page for the iOS platform docs.\")\n\n\u003cbr /\u003e\n\nCustom 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.\n\n\u003cbr /\u003e\n\nNative Validator is a new feature to help you catch policy violations before\nyour app ships. It automatically identifies certain policy violations in your\napp and notifies you through the app's UI.\n| **Key Point:** Native Validator will appear only on test ads. Live ad requests will never show Native Validator.\n\nNative Validator is enabled by default for test ads, but can be disabled as\nshown below. Keep in mind however that once the validator is disabled, test ads\nwill no longer show information about potential issues with your ad layouts.\n\nPrerequisites\n\n- Google Mobile Ads SDK 7.68.0 or higher.\n\n\u003c!-- --\u003e\n\n- Ensure your device is configured as a [test\n device](/ad-manager/mobile-ads-sdk/ios/test-ads#enable_test_devices).\n\nUsing Native Validator\n\nNative Validator automatically alerts you of certain policy violations in your\nUI through an overlay popup next to the ad.\n\nClicking on **See Issues** takes you to a fullscreen list of the relevant policy\nviolations.\n\nDisabling the validator\n\nTo disable Native Validator, add `GADNativeAdValidatorEnabled = false` to your\n`Info.plist`. \n\n \u003ckey\u003eGADNativeAdValidatorEnabled\u003c/key\u003e\n \u003cfalse/\u003e\n\nOr, edit it in the property list editor:"]]
