We understand the importance of documentation when navigating a system as complex as the AdWords API. For this reason, we would like to remind you about the reference materials available on our Developers site
First off, we’ve updated the Selector Fields page that provides information about the fields that can be used in generic selectors. This information is available on an object’s individual reference page, but we’ve collected it together across entire services for quicker lookups.
Next, we’ve added more columns to the Report Types page to include a field’s type, its behavior, and its XML and display names. The behavior of a field in the generated report describes its effect on zero impression rows as well as whether the field represents historical data or the latest object state.
Finally, we’ve added new tips to our Best Practices Guide on topics such as grouping batch job operations by ad groups and campaigns and using the partial failure feature. The guide is a great resource for developers starting an AdWords API project, but is also useful for established developers trying to increase the efficiency of their applications.
There is a feedback link on the top right hand corner of every page where you can report documentation issues. For technical help, visit our forum or office hours. You can also follow the Google Ads Developer page for all Ads-related updates.
- Eric Koleda and - Danial Klimkin, Ads Developer Relations Team.
Since releasing version 6.2.0 of our Android SDK on Tuesday, we have identified a high priority bug which causes apps to crash when our SDK returns certain types of ads. We’ve made a server-side fix which stops the crash-inducing ads, and are also issuing an SDK hotfix to prevent any similar issues from happening in the future.
Please download the new 6.2.1 SDK here and update your apps at your earliest convenience. And Happy Friday from AdMob!
Posted by Chrix Finne, Product Manager
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.
StoreKit
The Android AppEventListener interface has changed slightly to include the ad that fired the app event. The new interface definition is:
AppEventListener
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.
onAppEvent(String name, String info)
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:
destroy()
CustomEventBanner
public interface CustomEventBanner extends CustomEvent { void requestBannerAd(CustomEventBannerListener listener, Activity activity, String label, String serverParameter, AdSize size, MediationAdRequest mediationAdRequest, Object customEventExtra); void destroy();}
customEventExtra
CustomEventExtras
AdRequest
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().
CustomEventExtras.addExtra()
requestBannerAd
addExtra()
null
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.
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
With November on the horizon, we’d like to remind DFA API users of two important upcoming changes. Both of these changes were previously announced in August.
Java DART API Version Enforcement
To give you the best experience connecting to ReportCentral, it has become necessary to stop supporting older versions of the Java DART API. Starting November 3rd, 2012, we will only accept requests from the 3 latest versions, which are currently 13.4, 13.6, or 13.8. We have continued to improve our DFA Reporting API and still recommend all users switch to this new offering as soon as possible.
Removal of our Deprecation Policy
Also on November 3rd, 2012, our deprecation policy will no longer be in effect. Our commitment to our APIs and our users remains strong, and we will strive to announce all changes to our APIs long before they launch.
Please feel free to post any questions or concerns you may have on our forum.
- Joseph DiLallo, the DFA API Team
An authorization method is a scheme the client application uses to gain access to account information. AdWords, DoubleClick Ad Exchange Buyer and DFP APIs support several authorization methods including ClientLogin, OAuth1.0a and OAuth2.0. If you are still using an email address and a password to access the API, you are using the ClientLogin method which is now deprecated and is scheduled for sunset.
In a previous blog post we’ve covered general aspects of OAuth2.0 authorization and its benefits. To describe the process in more details, we’ve created a new article that shows how to use it with our official Ruby client library.
As always, please feel free to ask any questions regarding the client libraries or the AdWords API on our forum or during scheduled office hours. You can also follow the Google Ads Developer page for all Ads-related updates.
