AdMob test ads: demo ad unit IDs, test devices and Ad Inspector
Google's demo AdMob ad unit IDs for Android and iOS, how to set up test devices, why you must never click your own live ads, and a checklist before release.

While you build, use Google's demo ad unit IDs or mark your phone as a test device. Both give you real-looking ads that don't count as real impressions or clicks. Never tap a live ad in your own app: Google's policy bans it, even for testing, and it can put your AdMob account at risk.
This page has every demo ad unit ID for Android and iOS in one table, copied from Google's documentation (checked November 2026), plus how to set up test devices, what the test label looks like, how to test mediation with Ad Inspector, and a checklist for switching to real IDs before you ship.
Never click your own live ads
Google's behavioral policies say publishers may not click their own ads, and that testing your own ads by clicking on them is not allowed. Google recommends test ads instead. Its test ads guide warns that if you click too many ads without being in test mode, you risk the account being flagged for invalid activity.
Google's warnings and suspensions page says repeated or serious violations can lead to a suspension, during which no ads are shown for about 30 days and payments are held, and that earnings tied to violations may be withheld. Google's behavioral policies say it may also disable ad serving to your app or close the account. The safe habit is simple: develop with test ads, and don't tap live ones.
Demo ad unit IDs for every format
These come from Google's tables for Android and iOS. They only work with Google's test setup and won't earn anything.
| Format | Android | iOS |
|---|---|---|
| App open | ca-app-pub-3940256099942544/9257395921 | ca-app-pub-3940256099942544/5575463023 |
| Anchored adaptive banner | ca-app-pub-3940256099942544/9214589741 | ca-app-pub-3940256099942544/2435281174 |
| Inline adaptive banner | ca-app-pub-3940256099942544/9214589741 | ca-app-pub-3940256099942544/2435281174 |
| Fixed size banner | ca-app-pub-3940256099942544/6300978111 | ca-app-pub-3940256099942544/2934735716 |
| Interstitial | ca-app-pub-3940256099942544/1033173712 | ca-app-pub-3940256099942544/4411468910 |
| Rewarded | ca-app-pub-3940256099942544/5224354917 | ca-app-pub-3940256099942544/1712485313 |
| Rewarded interstitial | ca-app-pub-3940256099942544/5354046379 | ca-app-pub-3940256099942544/6978759866 |
| Native | ca-app-pub-3940256099942544/2247696110 | ca-app-pub-3940256099942544/3986624511 |
| Native video | ca-app-pub-3940256099942544/1044960115 | ca-app-pub-3940256099942544/2521693316 |
| Picture-in-picture | ca-app-pub-3940256099942544/9657123429 | ca-app-pub-3940256099942544/8810945611 |
The app ID is separate from ad unit IDs. Google's quick starts give sample app IDs: ca-app-pub-3940256099942544~3347511713 on Android (the com.google.android.gms.ads.APPLICATION_ID manifest entry) and ca-app-pub-3940256099942544~1458002511 on iOS (the GADApplicationIdentifier key in Info.plist). Note that the banner IDs above are for the formats in the banner sizes guide.
Test devices: use your own ad units safely
Demo IDs are quick, but you may want your real ad units to serve test ads, for instance to check that your own configuration works. That's what test devices are for: with a device registered, Google serves test ads for any ad unit, including yours.
- Emulators and simulators are test devices already. Google says Android emulators are configured as test devices automatically, and so are iOS simulators.
- Physical devices must be registered, either in the AdMob UI or in code. New devices typically start serving test ads within 15 minutes, though it can take up to 24 hours.
In the AdMob UI
Go to Settings, then Test devices, and click Add test device. You can register up to 250 devices. Enter a name, pick the platform and enter the advertising ID (Android) or IDFA (iOS). You can also choose a gesture, shake or flick twice, that opens Ad Inspector (Google's steps).
In code
Find your device ID in the logs (logcat on Android), then register it:
// Android (Kotlin)
val testDeviceIds = listOf("TEST_DEVICE_ID")
val configuration = RequestConfiguration.Builder().setTestDeviceIds(testDeviceIds).build()
MobileAds.setRequestConfiguration(configuration)
// iOS (Swift)
MobileAds.shared.requestConfiguration.testDeviceIdentifiers = ["TEST_DEVICE_ID"]
Google tells you to remove this code before you release the app.
How to tell it's a test ad
Test ads carry a label. On iOS Google's page says to expect a Test mode label centered at the top of the ad (native advanced ads add "Test mode" to the headline). The Android page describes a Test Ad label, which needs SDK 11.6.0 or higher. Mediated ads from other networks don't show the label at all, so don't read its absence as a bug.
Testing mediation with Ad Inspector
Ad Inspector is an in-app overlay for real-time analysis of test ad requests. For mediation, Google says it shows the waterfall details per request, the status of each third-party adapter, and lets you test individual ad sources and check ad unit health. Bidding details need SDK 20.2.0 or higher on Android and 8.5.0 or higher on iOS.
It only launches on test devices. Open it from code:
// Android (Kotlin)
MobileAds.openAdInspector(context) { error ->
// Non-null if ad inspector closed because of an error.
}
// iOS (Swift)
MobileAds.shared.presentAdInspector(from: viewController) { error in
// Non-nil if the inspector could not be displayed.
}
On iOS the view controller has to be fully on screen, so don't call it from viewDidLoad. Ad Inspector also uses more memory in the SDK on test devices, which is one more reason to keep test-only code out of release builds.
Switching to real IDs before release
- Replace every demo ad unit ID with your own from AdMob. Google says to do this before publishing.
- Use your real AdMob app ID in the manifest and
Info.plist, not the sample one. - Remove test device code (
setTestDeviceIds,testDeviceIdentifiers) and any consentreset()or debug geography settings. - Keep IDs out of the wrong build. A common pattern is debug builds use demo IDs and release builds use real ones, set in your build configuration.
- Check consent and privacy options: see the consent guide.
- Watch the first live ads without clicking them.
Tip: Once real ads are running, the free AdMob revenue calculator helps you sanity-check impressions and eCPM against what you expect to earn.
After release, Storewatch shows AdMob estimated earnings, impressions, eCPM, match rate and ad requests for each app, next to App Store proceeds, so you can see if your real IDs are working. It reads your AdMob data with a read-only Google sign-in and doesn't touch your ad setup.
Frequently asked questions
What is the AdMob test ad unit ID?
There isn't just one. Google publishes a demo ID per format and platform, such as ca-app-pub-3940256099942544/6300978111 for a fixed size banner on Android and ca-app-pub-3940256099942544/4411468910 for an interstitial on iOS. The table above has all of them.
Do I need to register an emulator as a test device?
No. Google says Android emulators and iOS simulators are automatically configured as test devices. Physical devices must be registered.
Can I click test ads?
Test ads are what Google recommends for checking that ads work. What you must not do is click live ads in your own app, which Google's policy prohibits, including for testing.
Why don't I see a test label?
Ads served through mediation from other networks don't show it. On Android the label needs SDK 11.6.0 or higher. If you get no ad at all, check logs for the error and try Ad Inspector.
How long until a new test device gets test ads?
Google says typically within 15 minutes, but it can take up to 24 hours.