Today, we are releasing AdMob iOS SDK v5.0.5 ( download here ). This SDK contains some important improvements to how the AdMob SDK supports interstitial ads.
In this release, we have added support for additional Rich Media interstitial ad formats for the iPhone and iPad. This update will be forward-compatible with all future interstitial formats. Be sure to get this update if your app relies on interstitial ads because after March 1, 2012, interstitial ads will not be supported on older versions of the SDK.
In addition to improved support for interstitial ads, this release contains two other noteworthy improvements. First, we have increased the accuracy of impression tracking for interstitial ads. Secondly, you’ll now receive the error message didFailToReceiveWithError: if you make any additional requests (after the initial request) from a single GADInterstitial object.
didFailToReceiveWithError:
If you have any questions please post them in our forum . Otherwise, check out AdMob iOS SDK v5.0.5 .
This week we released an addition to the v201109 version of the API, enabling one of the most commonly requested uses of the API: account creation. The CreateAccountService creates AdWords accounts without login emails (corresponding to the new optional-login feature available in the AdWords UI).
Let's dive right into some sample code using the Java client library . Notice that the only required parameters are currency, time zone, and descriptive name:
// Get the CreateAccountService. CreateAccountServiceInterface createAccountService = user.getService(AdWordsService.V201109.CREATE_ACCOUNT_SERVICE); Account account = new Account(); account.setCurrencyCode("EUR"); account.setDateTimeZone("Europe/London"); CreateAccountOperation operation = new CreateAccountOperation(); operation.setDescriptiveName("Account Created with CAS"); operation.setOperand(account); operation.setOperator(Operator.ADD); CreateAccountOperation[] operations = new CreateAccountOperation[] {operation}; Account[] accounts = createAccountService.mutate(operations);
We have a new Java client library available that includes CreateAccountService functionality and example code , and over the next few weeks we’ll be publishing updated libraries in other languages as well.
I hope this blog post will help you use this new feature effectively. As usual, If you have any questions about the AdWords API, check out our developer forum or ask us during our Google+ Hangout Office Hours .
- Nazmul Idris , AdWords API Team
Today we’d like to introduce you to the v201111 version of the DoubleClick for Publishers API. v201111 is one of our largest versions yet; it includes some highly-requested features such as full support for mobile ad serving, new creative types including templates, video player environment targeting, reporting updates, and suggested ad units. A full list of features can be found on our release notes page .
As part of our ongoing effort to expand our publishers’ networks to mobile platforms , we’ve made it easier than ever to create and target mobile inventory in the API. Starting in v201111, you’ll find the targetPlatform field on the AdUnit and LineItem objects. This field allows you to specify that an ad unit represents a piece of mobile inventory, or that a line item is only meant to serve to mobile ad units. If a line item is marked as mobile, you can also specify manufacturer , carrier , and device targeting . New examples for how to create mobile ad units and line items will be made available next to their web counterparts in the client library examples shortly.
In v201111, we’ve added a few new creative types, most importantly template creatives and custom creatives . Although both allow you to create richer advertisements, they differ in how you will want to use them in your solution. While custom creatives allow you to specify an arbitrary htmlSnippet with accompanying assets , creative templates allow you to reuse creative formats that will appear on the DFP user interface. Using creative templates, you can then create template creatives in which you can set variables to an already defined html snippet by the template.
We’ve also added the ability to view creatives as they would be served. To do this, pass the web page’s URL containing the appropriate ad tags, creative ID, and line item ID to the new LineItemCreativeAssociationService.getPreviewUrl() method.
Along with the new mobile support in the API, we’ve expanded our video capabilities. In v201108 , we added the ability to specify that a line item will serve to a video player environment . By enabling this setting, you can associate companion ads to run alongside the video. In v201111, as a DFP video publisher with a content feed, you can target individual videos within your content management source as well as positions within those videos .
We’ve also added the SuggestedAdUnit service . This premium-only service enables you to add a new ad unit to an ad tag before defining it in DFP. This allows you to run forecasts for it before traffickers can start targeting line items to it; this functionality is similar to auto-created zones in DART for Publishers. If the ad server receives at least 10 requests for an undefined ad unit, the SuggestedAdUnitService.getSuggestedAdUnitsByStatement method will return that suggested ad unit. The suggested ad units can then be approved using the ApproveSuggestedAdUnits action. You can find an example of how to do this in our client libraries. Please also make sure that you are a premium user and that you have enabled this feature in your account through the User Interface. For more information, see the premium inventory help page.
For v201111, we’ve added new columns and the feature to break down reports by dimension attributes . Whereas in the past you would have to manually correlate reports with objects fetched from services, this new feature allows you to include information such as a line item’s start time , an order’s trafficker , or an order’s external ID directly in the report to better integrate DFP reports with your system.
Over the next few weeks, you’ll have the chance to get to know all of the features a bit more in the Discover DFP v201111 series starting first with the updated features for the mobile platform. And as a final note, if you haven’t signed up for our first ever hangout yet, we’d love to see you there!
We’ve seen a lot of forum activity about how to migrate from v4.1.1 to v4.3.1 of the Google AdMob Ads SDK for Android, so we’d like to share three easy steps to get you up and running with the latest version.
target=android-13
project.properties
Don’t worry, you can still build your apps on all Android devices down to Android 1.5! Just set <uses-sdk android:minSdkVersion="3"/> in your AndroidManifest.xml file. You can read more about the uses-sdk element to help you configure the appropriate devices for your app.
<uses-sdk android:minSdkVersion="3"/>
AndroidManifest.xml
com.google.ads.AdActivity
<activity android:name="com.google.ads.AdActivity" android:configChanges="keyboard|keyboardHidden|orientation|screenLayout|uiMode|screenSize|smallestScreenSize"/>
That’s it! You should now be able to run your application using the latest SDK without any errors. Please post to our forum if you have any questions about the migration.