AdMob
Google AdMob is Google's mobile ad network. Connect it and the apps you build with Appsanic can earn revenue from ads: a banner along the bottom of a screen, a full-screen interstitial between levels or articles, or a rewarded ad the user opts into for an in-app perk. AdMob is the most common way to monetise a free app, and the agent wires the placements for you once the connector is in place.
What you get by connecting it
With AdMob connected, the agent can:
- Add banner ads to any screen, sized and positioned where you ask.
- Add interstitial ads that fill the screen at natural break points, with the load-then-show logic handled for you.
- Add rewarded ads that grant an in-app reward once the user finishes watching.
For each placement the agent wires the ad component into the screen and writes the load and show logic so the right ad is ready at the right moment.
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. Create one ad unit per placement you want (a banner, an interstitial, a rewarded unit, and so on).
Paste the IDs into Dashboard then Connectors then AdMob. Connect once and every project in your account can use it. Saved values show as dots rather than the raw text, and the page has a Test connection control to re-check them and a Disconnect control to remove them.
Keys and security
AdMob is a just connect connector. App IDs and ad-unit IDs are public by design - they are meant to be embedded in the app you publish, and they identify your account to Google rather than authorising spending. There is no server-side relay and no account access toggle: the agent simply embeds the IDs where the app needs them.
Even though these IDs are public, Appsanic still stores them encrypted at rest with AES-256-GCM. The browser only ever sees that a value exists, and the agent never asks you for an ID in chat - it reads it from the connector.
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.