FAQ and troubleshooting for using AdMob with Firebase

This page provides troubleshooting help and answers to frequently asked questions about using AdMob with Firebase. If you can't find what you're looking for or need additional help, contact Firebase support.

Can I link my Windows apps to Firebase?

No, Windows apps aren't supported.

Why can't I link my app to AdMob from the Firebase console?

You can link an AdMob app to a Firebase app using the AdMob console. Learn how.

What permissions or access do I need to link a Firebase app to an AdMob app?

To do this linking, you need the following access:

AdMob: You need to be an AdMob Admin.
Firebase: You must have the firebase.links.create permission, which is included in the Owner role and the Firebase Admin role.
Google Analytics: You must have the Edit role or Manage Users role for the property associated with the Firebase project. Learn more.

Can multiple users in the same AdMob account link AdMob apps and Firebase apps?

For multi-user AdMob accounts, the user who created the first Firebase link and accepted the Firebase Terms of Service is the only user who can create new links between AdMob apps and Firebase apps.

To use AdMob, which SDKs should I use?

To use AdMob, always use the Google Mobile Ads SDK as described in this FAQ. If you want to collect user metrics for AdMob, include the Firebase SDK for Google Analytics in your app.

For iOS projects:
Import the Google Mobile Ads SDK by following the instructions in the AdMob iOS documentation.
For Android projects:
Add the dependency for the Google Mobile Ads SDK to your build.gradle file:
implementation 'com.google.android.gms:play-services-ads:25.4.0'
For C++ projects and Unity projects: Follow the instructions in the respective documentation.

To use AdMob, always use the Google Mobile Ads SDK as described earlier in this FAQ.

We're making the following changes in September 2024 to give you more control over the dependencies that you add to your apps.

For Android: Firebase SDKs aren't going to be published for AdMob (firebase-ads or firebase-ads-lite); instead, use the Google Mobile Ads SDK as described earlier in this FAQ.
These artifacts didn't supply their own binary and were only a wrapper around their dependencies, specifically the Google Mobile Ads SDK and the Firebase SDK for Google Analytics. So, if your app calls any Google Analytics APIs and you switch to using the Google Mobile Ads SDK, make sure that you explicitly add the dependency for the Firebase SDK for Google Analytics (com.google.firebase:firebase-analytics) to your app's build.gradle file.

Even after these artifacts stop being published, any existing versions will continue to work. However, to get bug fixes and new features, you'll need to migrate to use the SDKs as described earlier in this FAQ.
For iOS: You can no longer add Google-Mobile-Ads-SDK from the Firebase zip distribution or FirebaseAdMob from Carthage; instead, import the Google Mobile Ads SDK as described earlier in this FAQ. Note that the FirebaseAdMob binary is functionally equivalent to Google-Mobile-Ads-SDK.
Even after Firebase ceases these binary distributions, any existing versions of the Firebase zip distributions will continue to be available. However, to get bug fixes and new features, you'll need to migrate to use the pod as described earlier in this FAQ.

FAQ and troubleshooting for using AdMob with Firebase Stay organized with collections Save and categorize content based on your preferences.