AdMob and the General Data Protection Regulation (GDPR). __Look for the PersonalizedAd property and blocks in the AdMob components. It is up to you, the developer, to obtain the user’s consent by displaying a screen/dialog asking the user whether they want to see personalized or non-personalized ads. You would then use that information to set the PersonalizedAd property on your ads before loading them.
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:
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.
- 2.Add an existing app on Google Play or one that is not yet published
- 3.Create an ad unit and find your Ad Unit ID to copy into Thunkable
- 4.Set the Screen Size on Thunkable Screen1 to 'Responsive'
The recent EU Protection Regulation (GDPR) requires developers to obtain the user's consent by displaying a screen / dialog to ask the user if they want to see personalized or non-personalized ads.
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
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.
Here are other reasons your ad may not be showing up: