AdMob
Google AdMob is Google's mobile ad network. The Appsanic connector stores the public App IDs plus banner and interstitial ad-unit IDs. The agent can design those placements as honest preview placeholders and leave native setup instructions for after export.
What you get by connecting it
With AdMob connected, the agent can:
- Place banner placeholders on the screens you choose.
- Mark natural interstitial breaks without pretending an ad can load in preview.
- Generate a commented
SETUP REQUIREDblock for the native ads package, consent, test units, and a development build.
The connector does not currently collect a rewarded-ad unit. Ask for rewarded ads only after export and treat that as additional native implementation work.
One thing to know up front: real ads only render in a development or production build. In the Expo Go preview you see clearly labelled placeholders where the ads will sit, so you can lay out the screen without waiting on a build. While you are developing, use Google's test ad-unit IDs rather than your live ones - tapping your own live ads can get the account flagged.
Connecting it
You need two kinds of public identifier from AdMob:
- An App ID for each platform (one for iOS, one for Android).
- One ad-unit ID per placement (each begins with
ca-app-pub-).
Find both in the AdMob console: App IDs live under Apps, and ad-unit IDs under Ad units for each app. The current form accepts banner and interstitial units.
Open the project build, select Connectors, choose AdMob, and enter the IDs. The connection applies only to that project. These values remain visible because they are public app configuration. The connector surface also has Test now and Disconnect controls.
Keys and security
AdMob is a just connect connector. App IDs and ad-unit IDs are public by design - they identify placements rather than authorising Google-account access. There is no server-side relay or Account access toggle.
AdMob provides no credential this form can use for a live account probe, so Test now validates ID shape only. It does not confirm the app exists, that an ad unit belongs to it, that policy review passed, or that ads can serve. Real and Google demo ads both require native package setup and a development build; neither runs in the browser preview or Expo Go.
Useful links
- AdMob developer docs: https://developers.google.com/admob
- Appsanic guide: Ads and monetisation
Next
Read Ads and monetisation for the full picture of earning revenue from ads in your app.