Get Started

This guide is for publishers who want to monetize a C++ app with AdMob, without using Firebase. If you plan to include Firebase in your app—or if you're considering it—see the AdMob with Firebase version of this guide instead.

Integrating the Google Mobile Ads C++ SDK into an app is the first step toward displaying ads and earning revenue. Once you've integrated the SDK, you can choose an ad format, such as interstitial or rewarded, and follow the steps to implement it.

The Google Mobile Ads C++ SDK wraps the Google Mobile Ads iOS and Android SDKs, and is only available on those platforms. The Google Mobile Ads C++ SDK makes use of Firebase C++ constructs to support asynchronous operations, so it resides in the firebase::gma namespace.

If this is your first time going through this guide, we recommend that you download and follow along using the Google Mobile Ads C++ test app.

Prerequisites

Set up your app in your AdMob account

Register your app as an AdMob app by completing the following steps:

1. Sign in to or sign up for an AdMob account.

2. Register your app with AdMob. This step creates an AdMob app with a unique AdMob app ID that is needed later in this guide.

Install the Google Mobile Ads C++ SDK

Since the Google Mobile Ads C++ SDK resides in the firebase::gma namespace, download the Firebase C++ SDK, and then unzip it to a directory of your choice.

The Firebase C++ SDK is not platform-specific, but it does require platform-specific library configurations.

You're all set! Your C++ app is configured to use the Google Mobile Ads C++ SDK without any other Firebase services.

Configure your app's AdMob app ID

Initialize the Google Mobile Ads SDK

Before loading ads, have your app initialize the Google Mobile Ads C++ SDK by calling firebase::gma::Initialize() which initializes the SDK and completes a firebase::Future once initialization is complete (or after a 30-second timeout). This needs to be done only once, ideally at app launch.

Ads may be preloaded by the Google Mobile Ads C++ SDK or mediation partner SDKs upon calling Initialize(). If you need to obtain consent from users in the European Economic Area (EEA), set any request-specific flags (such as tag_for_child_directed_treatment or tag_for_under_age_of_consent), or otherwise take action before loading ads, ensure you do so by invoking firebase::gma::SetRequestConfiguration() before initializing the Google Mobile Ads C++ SDK. For more information see our Targeting guide.

Here's an example of how to call Initialize():

// Initialize the Google Mobile Ads library
firebase::InitResult result;
Future<AdapterInitializationStatus> future =
  firebase::gma::Initialize(jni_env, j_activity, &result);

if (result != kInitResultSuccess) {
  // Initialization immediately failed, most likely due to a missing
  // dependency. Check the device logs for more information.
  return;
}

// Monitor the status of the future.
// See "Use a Future to monitor the completion status of a method call" below.
if (future.status() == firebase::kFutureStatusComplete &&
    future.error() == firebase::gma::kAdErrorCodeNone) {
  // Initialization completed.
} else {
  // Initialization on-going, or an error has occurred.
}

// Initialize the Google Mobile Ads library.
firebase::InitResult result;
Future<AdapterInitializationStatus> future =
  firebase::gma::Initialize(&result);

if (result != kInitResultSuccess) {
  // Initialization immediately failed, most likely due to a missing
  // dependency. Check the device logs for more information.
  return;
}

// Monitor the status of the future.
// See "Use a Future to monitor the completion status of a method call" below.
if (future.status() == firebase::kFutureStatusComplete &&
    future.error() == firebase::gma::kAdErrorCodeNone) {
  // Initialization completed.
} else {
  // Initialization on-going, or an error has occurred.
}

Use a Future to monitor the completion status of a method call

A Future provides you a way to determine the completion status of your asynchronous method calls.

For example, when your app calls firebase::gma::Initialize(), a new firebase::Future is created and returned. Your app can then poll the status() of the Future to determine when the initialization has completed. Once complete, your app can invoke result() to obtain the resulting AdapterInitializationStatus.

Methods that return a Future have a corresponding "last result" method that apps can use to retrieve the most recent Future for a given action. For example, firebase::gma::Initialize() has a corresponding method called firebase::gma::InitializeLastResult(), which returns a Future that your app can use to check the status of the last call to firebase::gma::Initialize().

If the status of the Future is complete and its error code is firebase::gma::kAdErrorCodeNone, then the operation has completed successfully.

You can also register callbacks to be invoked when a Future is completed. In some cases, the callback will be running in a different thread, so make sure your code is thread-safe. This code snippet uses a function pointer for the callback:

// Registers the OnCompletion callback. user_data is a pointer that is passed verbatim
// to the callback as a void*. This allows you to pass any custom data to the callback
// handler. In this case, the app has no data, so you must pass nullptr.
firebase::gma::InitializeLastResult().OnCompletion(OnCompletionCallback,
  /*user_data=*/nullptr);

// The OnCompletion callback function.
static void OnCompletionCallback(
  const firebase::Future<AdapterInitializationStatus>& future, void* user_data) {
  // Called when the Future is completed for the last call to firebase::gma::Initialize().
  // If the error code is firebase::gma::kAdErrorCodeNone,
  // then the SDK has been successfully initialized.
  if (future.error() == firebase::gma::kAdErrorCodeNone) {
    // success!
  } else {
    // failure.
  }
}

Select an ad format

The Google Mobile Ads C++ SDK is now imported and you're ready to implement an ad. AdMob offers a number of different ad formats, so you can choose the one that best fits your app's user experience.

Banner

Rectangular ads that appear at the top or bottom of the device screen. Banner ads stay on screen while users are interacting with the app, and can refresh automatically after a certain period of time. If you're new to mobile advertising, they're a great place to start.

Implement banner ads

Interstitial

Full-screen ads that cover the interface of an app until closed by the user. They're best used at natural pauses in the flow of an app's execution, such as between levels of a game or just after a task is completed.

Implement interstitial ads

Rewarded

Ads that reward users for watching short videos and interacting with playable ads and surveys. Used for monetizing free-to-play apps.

Implement rewarded ads