[null,null,["最后更新时间 (UTC):2025-08-20。"],[[["\u003cp\u003eEnable test ads during development to avoid invalid activity flags on your account by preventing accidental clicks on real ads.\u003c/p\u003e\n"],["\u003cp\u003eUse Google-provided demo ad units for quick testing or configure your device as a test device for more rigorous testing with your own ad unit IDs.\u003c/p\u003e\n"],["\u003cp\u003eRemember to replace demo ad unit IDs with your own before publishing and remove test device IDs from your code.\u003c/p\u003e\n"],["\u003cp\u003eFor mediation testing, enable test ads for each network individually, as mediated ads do not display the "Test Ad" label.\u003c/p\u003e\n"],["\u003cp\u003eUse \u003ccode\u003egetMediationAdapterClassName()\u003c/code\u003e to identify the ad network serving the current ad when unsure about a network's test ad support.\u003c/p\u003e\n"]]],[],null,["# Enable test ads\n\nSelect platform: [Android](/admob/android/test-ads \"View this page for the Android platform docs.\") [iOS](/admob/ios/test-ads \"View this page for the iOS platform docs.\") [Unity](/admob/unity/test-ads \"View this page for the Unity platform docs.\") [Flutter](/admob/flutter/test-ads \"View this page for the Flutter platform docs.\")\n\n\u003cbr /\u003e\n\n\n\u003cbr /\u003e\n\nThis guide explains how to enable test ads in your ads integration. It's\nimportant to enable test ads during development so that you can click them\nwithout charging Google advertisers. If you click too many ads without being\nin test mode, you risk your account being flagged for invalid activity.\n\nThere are two ways to get test ads:\n\n1. Use one of Google's [demo ad units](#demo_ad_units).\n2. Use your own ad unit and [enable test devices](#enable_test_devices).\n\nPrerequisite\n------------\n\n- Complete [Get Started](/admob/android/quick-start).\n\nDemo ad units\n-------------\n\nThe quickest way to enable testing is to use Google-provided demo ad units.\nThese ad units are not associated with your AdMob\naccount, so there's no risk of your account generating invalid traffic when\nusing these ad units.\n| **Key Point:** Make sure you replace these IDs with your own ad unit ID before publishing your app.\n\nHere are demo ad units that point to specific test creatives for each format:\n\n| Ad format | Demo ad unit ID |\n|---------------------------------------------------------------|------------------------------------------|\n| [App Open](/admob/android/app-open) | `ca-app-pub-3940256099942544/9257395921` |\n| [Adaptive Banner](/admob/android/banner) | `ca-app-pub-3940256099942544/9214589741` |\n| [Fixed Size Banner](/admob/android/banner/fixed-size) | `ca-app-pub-3940256099942544/6300978111` |\n| [Interstitial](/admob/android/interstitial) | `ca-app-pub-3940256099942544/1033173712` |\n| [Rewarded Ads](/admob/android/rewarded) | `ca-app-pub-3940256099942544/5224354917` |\n| [Rewarded Interstitial](/admob/android/rewarded-interstitial) | `ca-app-pub-3940256099942544/5354046379` |\n| [Native](/admob/android/native) | `ca-app-pub-3940256099942544/2247696110` |\n| [Native Video](/admob/android/native/video-ads) | `ca-app-pub-3940256099942544/1044960115` |\n\nEnable test devices\n-------------------\n\nIf you want to do more rigorous testing with production-looking ads, you can\nnow configure your device as a test device and use your own ad unit IDs that\nyou've created in the AdMob UI.\n\nTest devices can either be added in the AdMob UI or programmatically using the\nGoogle Mobile Ads SDK.\n\n\nFollow the steps below to add your device as a test device.\n| **Key Point:** Android emulators are automatically configured as test devices.\n\n### Add your test device in the AdMob UI\n\nFor a non-programmatic way to add a test device and test new or existing\napp builds, use the AdMob UI. [Learn\nhow](//support.google.com/admob/answer/9691433).\n| **Key Point:** New test devices typically start serving test ads in your app within 15 minutes, but it can also take up to 24 hours.\n\n### Add your test device programmatically\n\nTo register your test device, complete the following steps:\n\n1. Load your ads-integrated app and make an ad request.\n2. Check the logcat output for a message similar to the following, which shows you your device ID and how to add it as a test device: \n\n ```text\n I/Ads: Use RequestConfiguration.Builder.setTestDeviceIds(Arrays.asList(\"33BE2250B43518CCDA7DE426D04EE231\"))\n to get test ads on this device.\"\n ```\n Copy your test device ID to your clipboard.\n3. Modify your code to call\n\n [`RequestConfiguration.Builder.setTestDeviceIds()`](/admob/android/reference/com/google/android/gms/ads/RequestConfiguration.Builder#setTestDeviceIds(java.util.List%3Cjava.lang.String%3E))\n\n and pass in a list of your test device IDs.\n\n ### Java\n\n List\u003cString\u003e testDeviceIds = Arrays.asList(\"\u003cvar translate=\"no\"\u003eTEST_DEVICE_ID\u003c/var\u003e\");\n RequestConfiguration configuration =\n new RequestConfiguration.Builder().setTestDeviceIds(testDeviceIds).build();\n MobileAds.setRequestConfiguration(configuration); \n https://github.com/googleads/googleads-mobile-android-examples/blob/ccc290a583d7f552bdcf81ea76adc05beaa43f0b/java/advanced/APIDemo/app/src/main/java/com/google/android/gms/snippets/RequestConfigurationSnippets.java#L15-L18\n\n ### Kotlin\n\n val testDeviceIds = listOf(\"\u003cvar translate=\"no\"\u003eTEST_DEVICE_ID\u003c/var\u003e\")\n val configuration = RequestConfiguration.Builder().setTestDeviceIds(testDeviceIds).build()\n MobileAds.setRequestConfiguration(configuration) \n https://github.com/googleads/googleads-mobile-android-examples/blob/ccc290a583d7f552bdcf81ea76adc05beaa43f0b/kotlin/advanced/APIDemo/app/src/main/java/com/google/android/gms/snippets/RequestConfigurationSnippets.kt#L27-L29\n\n Replace \u003cvar translate=\"no\"\u003eTEST_DEVICE_ID\u003c/var\u003e with your test device ID.\n\n You can optionally check\n\n [`isTestDevice()`](/admob/android/reference/com/google/android/gms/ads/AdRequest#isTestDevice(android.content.Context))\n\n to confirm that your device was properly added as a test device.\n | **Caution:** Be sure to remove the code that sets these test device IDs before you release your app.\n4. Re-run your app. If the ad is a Google ad, you'll see a **Test Ad** label\n centered at the top of the ad (banner, interstitial, or rewarded video):\n\n | **Note:** To see the **Test Ad** label, you need to be using an SDK version of 11.6.0 or higher.\n\n For native advanced ads, the headline asset is prepended with the string **Test Ad**.\n\nAds with this **Test Ad** label are safe to click. Requests, impressions, and\nclicks on test ads won't show up in your account's reports.\n| **Note:** Mediated ads do *NOT* render a **Test Ad** label. See the following section for details.\n\nTesting with mediation\n----------------------\n\nGoogle's sample ad units only show Google Ads. To test your\nAdMob Mediation configuration,\nyou must use the [enable test devices](#enable_test_devices)\napproach.\n\nMediated ads do *NOT* render a Test Ad label. You are responsible for\nensuring that test ads are enabled for each of your mediation networks so these\nnetworks don't flag your account for invalid activity. See each network's\nrespective [mediation guide](/admob/android/mediation)\nfor more information.\n\nIf you aren't sure whether a mediation ad network adapter supports test ads, it\nis safest to avoid clicking on ads from that network during development. You\ncan use the\n\n[`getMediationAdapterClassName()`](/admob/android/reference/com/google/android/gms/ads/ResponseInfo#getMediationAdapterClassName())\n\nmethod on any of the ad formats to figure out which ad network served the\ncurrent ad."]]