I/Ads: Use
RequestConfiguration.Builder
.setTestDeviceIds(Arrays.asList("33BE2250B43518CCDA7DE426D04EE231"))
to get test ads on this device.
iOS
<Google> To get test ads on this device, set:
GADMobileAds.sharedInstance.requestConfiguration.testDeviceIdentifiers =
@[ @"2077ef9a63d2b398840261c8221a0c9b" ];
將英數字元組成的測試裝置 ID 複製到剪貼簿。
在發出廣告請求前修改程式碼，呼叫 MobileAds.instance.updateRequestConfiguration 並傳遞測試裝置 ID 清單。
[null,null,["上次更新時間：2025-08-26 (世界標準時間)。"],[[["\u003cp\u003eEnable test ads during development to avoid invalid activity flags on your AdMob account by preventing charges for clicks on real ads.\u003c/p\u003e\n"],["\u003cp\u003eUse Google-provided sample ad units for quick testing or enable test devices for more realistic testing scenarios with your own ad units.\u003c/p\u003e\n"],["\u003cp\u003eReplace test ad unit IDs with your own before publishing your app to ensure you're displaying real ads to users.\u003c/p\u003e\n"],["\u003cp\u003eEnsure your mediation networks have test ads enabled to avoid invalid activity concerns, and avoid clicking ads from networks without test ad support during development.\u003c/p\u003e\n"],["\u003cp\u003eTest devices, including Android emulators and iOS simulators, display a "Test Ad" label on test ads, but mediated ads may not show this label.\u003c/p\u003e\n"]]],["To safely test ads in your app, use either Google's sample ad units or enable test devices with your own ad units. Sample ad units are for quick testing, while enabling test devices allows testing with production-looking ads. Test devices can be added via the AdMob UI or programmatically by registering the device ID. Ensure to remove any code related to test devices before releasing the app and remember mediated ads don't display a \"Test Ad\" label.\n"],null,["Select 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\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 on them\nwithout charging Google advertisers. If you click on 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 sample ad units.\n\n2. Use your own ad unit and enable test devices.\n\nPrerequisites\n\n- Complete [Get Started](/admob/flutter/quick-start).\n\n- [Import the Google Mobile Ads Flutter plugin](/admob/flutter/quick-start#import_the_mobile_ads_sdk) to your Flutter app.\n\nSample ad units\n\nThe quickest way to enable testing is to use Google-provided test 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\nIt is important to note that Google has different test ad units for\n[Android](/admob/android/test-ads#demo_ad_units) and\n[iOS](/admob/ios/test-ads#demo_ad_units). You'll need to use an iOS test\nad unit for making test ad requests on iOS and an Android test ad unit for\nmaking requests on Android.\n\nThese ad units point to specific test creatives.\n| **Key Point:** Make sure you replace these test IDs with your own ad unit ID before publishing your app.\n\nEnable test devices\n\nIf you want to do more rigorous testing with production-looking ads, you can now\nconfigure your device as a test device and use your own ad unit IDs that you've\ncreated in the AdMob UI.\n\nFollow the steps below to add your device as a test device.\n| **Key Point:** Android emulators and iOS simulators are automatically configured as test devices.\n\nAdd your test device in the AdMob UI\n\nFor a simple, non-programmatic way to add a test device and test new or existing\napp builds, use the AdMob UI. [Learn how](//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\nAdd your test device programmatically\n\nIf you want to test ads in your app as you're developing, follow the\nsteps below to programmatically register your test device.\n\n1. Run an app configured with the Mobile Ads SDK and make an ad request\n using one of the test ad unit IDs listed above.\n\n void loadBanner() {\n \n final adUnitId = Platform.isAndroid\n ? 'ca-app-pub-3940256099942544/6300978111'\n : 'ca-app-pub-3940256099942544/2934735716';\n final bannerAd = BannerAd(\n adUnitId: adUnitId,\n request: AdRequest(),\n size: AdSize.banner,\n );\n bannerAd.load();\n \n }\n\n2. Check the console or logcat output for a message that looks like this:\n\n Android \n\n ```\n I/Ads: Use\n RequestConfiguration.Builder\n .setTestDeviceIds(Arrays.asList(\"33BE2250B43518CCDA7DE426D04EE231\"))\n to get test ads on this device.\n ```\n\n iOS \n\n ```\n \u003cGoogle\u003e To get test ads on this device, set:\n GADMobileAds.sharedInstance.requestConfiguration.testDeviceIdentifiers =\n @[ @\"2077ef9a63d2b398840261c8221a0c9b\" ];\n ```\n3. Copy your alphanumeric test device ID to your clipboard.\n\n4. Modify your code to call `MobileAds.instance.updateRequestConfiguration`\n with your test device IDs list before making the ad request.\n\n MobileAds.instance.updateRequestConfiguration(\n RequestConfiguration(testDeviceIds: ['33BE2250B43518CCDA7DE426D04EE231']));\n\n | Be sure to remove the code that sets these test devices before you release your app.\n5. Re-run your app. If you correctly added your device as a test device, you\n will see a **Test Ad** label centered at the top of banner, interstitial,\n and rewarded ads:\n\n\n Ads with this **Test Ad** label are safe to click. Any requests,\n impressions, and clicks on test ads don't show up in your account's\n reports.\n | Mediated ads DO NOT render a **Test Ad** label.\n6. Now that your device is registered as a test device, you can begin receiving\n more realistic test ads by replacing the test `adUnitID` with your own\n `adUnitID`.\n\nTesting with mediation\n\nGoogle's sample ad units only show Google Ads. To test your mediation\nconfiguration, you must\n[enable test devices](/admob/flutter/test-ads#enable_test_devices).\n\nMediated ads do NOT render a **Test Ad** label. You are responsible for ensuring\nthat test ads are enabled for each of your mediation networks so these networks\ndon't flag your account for invalid activity. See\n\\[each network's mediation guide\\]((/admob/flutter/choose-networks#network_details)\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 can\ncheck [`Ad.responseInfo`](/admob/flutter/mediation#check_which_ad_network_adapter_class_loaded_the_ad_2)\non any of the ad formats to figure out which ad network served the current ad."]]
