App Open Ads
This guide is intended for publishers integrating app open ads using Google Mobile Ads SDK.
App open ads are a special ad format intended for publishers wishing to monetize their app load screens. App open ads can be closed at any time, and are designed to be shown when your users bring your app to the foreground.
Note
Specific ad formats may vary by region.
App open ads automatically show a small branding area so users know they're in your app. Here is an example of what an app open ad looks like:

Prerequisites
Before you continue, do the following:
- Complete the Get started guide.
Always test with test ads
The following table contains an ad unit ID which you can use to request test ads. It's been specially configured to return test ads rather than production ads for every request, making it safe to use.
However, after you've registered an app in the AdMob web interface and created your own ad unit IDs for use in your app, explicitly configure your device as a test device during development.
Implementation
The main steps to integrate app open ads are:
- Create a utility class
- Load the app open ad
- Listen to app open ad events
- Consider ad expiration
- Listen to app state events
- Show the app open ad
- Clean up the app open ad
- Preload the next app open ad
Create a utility class
Create a new class (e.g., AppOpenAdManager) to load the ad. This class controls an instance variable to keep track of a loaded ad and the ad unit ID for each platform.
Tip
While not strictly required, adding this script as an Autoload (Singleton) is highly recommended. This ensures the manager survives scene changes and remains persistent in the scene tree—providing a seamless global state monitor identical to the automated systems used by Google in other platforms.
Load the app open ad
Loading an app open ad is accomplished using the load() method on the AppOpenAdLoader class. The load method requires an ad unit ID, an AdRequest object, and a completion handler which gets called when ad loading succeeds or fails. The loaded AppOpenAd object is provided as a parameter in the completion handler.
Warning
Attempting to load a new ad from the ad request completion block when an ad failed to load is strongly discouraged. If you must load an ad from the ad request completion block, limit ad load retries to avoid continuous failed ad requests in situations such as limited network connectivity.
Listen to app open ad events
To further customize the behavior of your ad, you can hook into a number of events in the ad's lifecycle: opening, closing, and so on. Listen for these events by registering a delegate as shown below.
Consider ad expiration
Key Point
App open ads will time out after four hours. Ads rendered more than four hours after request time will no longer be valid and may not earn revenue.
To ensure you don't show an expired ad, add a method to the AppOpenAdManager that checks how long it has been since your ad loaded. Then, use that method to check if the ad is still valid.
The app open ad has a 4 hour timeout. Cache the load time in the _expire_time variable.
Listen to app state events
Use Godot's focus notifications to listen to application foreground and background events.
Show the app open ad
To show a loaded app open ad, call the show() method on the AppOpenAd instance.
Note
App open ads should be displayed during natural pauses in the flow of an app. Between levels of a game is a good example, or after the user completes a task.
Clean up the app open ad
When you are finished with a AppOpenAd, make sure to call the destroy() method before dropping your reference to it:
This notifies the plugin that the object is no longer used and the memory it occupies can be reclaimed. Failure to call this method results in memory leaks.
Preload the next app open ad
AppOpenAd is a one-time-use object. This means once an app open ad is shown, the object can't be used again. To request another app open ad, you'll need to create a new AppOpenAd object.
To prepare an app open ad for the next impression opportunity, preload the app open ad once the on_ad_dismissed_full_screen_content or on_ad_failed_to_show_full_screen_content event is raised.
Cold starts and loading screens
The documentation thus far assumes that you only show app open ads when users foreground your app when it is suspended in memory. "Cold starts" occur when your app is launched but was not previously suspended in memory.
An example of a cold start is when a user opens your app for the first time. With cold starts, you won't have a previously loaded app open ad that is ready to be shown immediately. The delay between when you request an ad and receive an ad back can create a situation where users are able to briefly use your app before being surprised by an ad. This should be avoided because it is a bad user experience.
The preferred way to use app open ads on cold starts is to use a loading screen to load your game or app assets, and only show the ad from the loading screen. If your app has completed loading and has sent the user to the main content of your app, do not show the ad.
Key Point
In order to continue loading app assets while the app open ad is being displayed, always load assets in a background thread.
Best practices
App open ads help you monetize your app loading screen when the app first launches and during app switches, but it's important to keep the following best practices in mind so that your users enjoy using your app.
- Show your first app open ad after your users have used your app a few times.
- Show app open ads during times when your users would otherwise be waiting for your app to load.
- If you have a loading screen under the app open ad and your loading screen completes loading before the ad is dismissed, dismiss your loading screen in the
on_ad_dismissed_full_screen_contentevent handler. - Ensure your
AppOpenAdManager(the node that implements the app state listener) is present in the scene tree. Life cycle notifications such asNOTIFICATION_APPLICATION_FOCUS_INare required for events to fire, so don't remove this node; events stop firing if the node is removed from the tree.
Additional resources
- Sample Project: A minimal implementation of all ad formats.