We have a section on our community forum dedicated to helping users use this component effectively.
In addition, we recommend that app developers audience first before implementing ads both because it takes away from the user experience. Without a sufficient audience, you won't generate much revenue anyway. Google will also refund advertisers and invalidate accidental or fraudulent clicks and even disable an ad or an account where it detects there are.
AdMob offers two types of ads:
320 x 50 fixed ratio
Best suited for apps with linear user experiences with clear starts and stops. For a gaming app, a good time for an interstitial is after a level is complete. For a non-gaming app, interstitials may be effective after a number of actions have been completed
Works well with most apps but avoid placing in the middle of screen esp in between interactive content as this may reduce the likelihood of users to engage with the ad or lead to accidental clicks
There is a bit of set-up required to start making money with AdMob. The step that usually confuses users is the waiting period between when an account is created and when ads are ready to go live, which sometimes may take a day.
Go to AdMob and create an account
Add an existing app on Google Play or one that is not yet published
Create an ad unit and find your Ad Unit ID to copy into Thunkable
Set the Screen Size on Thunkable Screen1 to 'Responsive'
Once you have obtained consent, you can then set the property appropriately before loading your ads.
Loads your AdMob banner ad after the user has been in your app for 20 seconds. You can adjust the timer to vary the time before the ad loads but it may actually be both better for the user experience and for your earnings to wait a little bit of time before you trigger the ads to prevent app users from bouncing too quickly
Property / Event
Ad unit ID
ID retrieved from your AdMob account (see set-up above) after you create a new ad unit and select ad format
If 'true', ad clicks will not count. We recommend that you select 'true' when testing and then set to 'false' when you publish your app live
Loads the ad
If 'true', ad will be visible on the screen
We just added a block that should make it easier to understand why your AdMob ads may not be showing up on your built app.
Property / Event
Ad Failed to Load (
If AdMob ad fails to load, will return an
The Ad Unit ID is wrong or it is a new ID which could take hours to be activated
You have entered the App ID or the Publisher ID instead of the Ad Unit ID which begins with
Please check the mobile device internet connectivity or disable ad blockers on the mobile device
Your setup is correct. The issue is that AdMob does not always have an ad to return for every request. This may happen particularly if you have just registered your AdMob publisher ID, as it takes some time and multiple requests before the new ID starts returning ads
Here are other reasons your ad may not be showing up:
For Banner Ads, Screen set to 'Fixed'. Screen needs to be set to 'Responsive'
Load Ad block not called in Blocks Editor