We’re excited to announce the release of the AdMob SDK v6.2.0 for Android and v6.2.1 for iOS. The iOS update is mostly a bugfix release, but now requires you to link against the StoreKit framework, which will allow us to experiment with innovative ad experiences. The Android release includes changes to DFP App Events and Custom Events that we’ll discuss below.
DFP App Events
The Android AppEventListener interface has changed slightly to include the ad that fired the app event. The new interface definition is:
public interface AppEventListener {
void onAppEvent(Ad ad, String name, String info);
}
If you previously implemented onAppEvent(String name, String info), you’ll have to update this method signature when upgrading to v6.2.0.
Custom Events
Due to popular demand, we’ve added the ability to pass information to your custom event. We’ve also added a destroy() method so you can clean up your custom event. The new CustomEventBanner interface definition is:
public interface CustomEventBanner extends CustomEvent {
void requestBannerAd(CustomEventBannerListener listener,
Activity activity,
String label,
String serverParameter,
AdSize size,
MediationAdRequest mediationAdRequest,
Object customEventExtra);
void destroy();
}
The customEventExtra object is sent to your custom event by creating an instance of CustomEventExtras and passing it to the AdRequest. The following example sends the string “hello custom event” to your custom event class:
final String CUSTOM_EVENT_LABEL = “MyCustomEventLabel”; AdRequest adRequest = new AdRequest(); CustomEventExtras extras = new CustomEventExtras(); extras.addExtra(CUSTOM_EVENT_LABEL, "hello custom event"); adRequest.setNetworkExtras(extras);
When calling CustomEventExtras.addExtra(), make sure the key is the same as the label of the custom event you defined in the AdMob UI. The AdMob SDK searches CustomEventExtras for the object corresponding to the label of the custom event, and invokes requestBannerAd on your custom event class with that object. You can call addExtra() for each custom event class you have, and AdMob Mediation will send the appropriate object to the custom event it invokes. If AdMob can’t find an object for your custom event label, it will pass null to requestBannerAd().
A destroy() method has also been added to the custom event interface so you can perform any necessary cleanup. The AdMob Mediation framework will invoke destroy() when it refreshes the AdView.
Check out the release notes for the full list of changes in this version. If you have any questions about the latest AdMob SDK, please reach out to us on the forum or join us for AdMob office hours. You can also follow us on the Google Ads Developer plus page for AdMob-related updates.
- Eric Leichtenschlag, AdMob Team