- Mobile bid modifiers are now supported in ad groups. You can use the setMobileBidModifier and getMobileBidModifier methods to manage this setting.
- You can now retrieve disapproval reasons for ads using the getDisapprovalReasons method if they have been disapproved.
Tag Archives: Developer
Announcing open sign-ups for the Ads API Workshops on Display
- DoubleClick for Publishers API
- DoubleClick Sales Manager API
- Interactive Media Ads (IMA) SDK
- Mobile Ads SDK
These workshops are a great way for you to meet with the display ads API team and ask questions in person. This is also a key occasion for members of the community to bring their feedback directly to us. Most of all, it's a great opportunity for you to exchange ideas and best practices with fellow developers.
We are inviting you to join us in the following cities:
- New York, Tuesday, June 17
- San Francisco, Monday, June 23
Please fill out this registration form if you're interested in attending one of these workshops. Due to limited space, we cannot guarantee admittance, but we’ll send a confirmation email in the coming weeks to let you know if you have a spot.
To receive announcements of upcoming Ads API Workshops on Display, please join this mailing list.
Hope to see you there!
Source: Google Ads Developer Blog
Announcing the DFP API Playground GitHub project
As many of you are well aware, the DFP API Playground is a great tool to explore the DFP API. With it, you can easily test PQL statements and examine the JSON equivalent of the objects you fetch. Best of all, it acts as a full reference implementation of how you should integrate the API with App Engine, touching on features such as OAuth2 authentication, task queues, and channels.
Now, we are announcing the new GitHub project for the DFP API Playground, featuring all the benefits of being hosted on GitHub, improved getting started instructions, and revamped project downloads.
Taking it for a spin
The first thing you’ll notice when visiting the project is that we’ve made it incredibly easy to get up and running.With Maven
If you are a Maven user, it’s as simple as modifying the appengine-web.xml file and running
mvn appengine:devserver
We’ve also included an m2e project so developing with Eclipse is easier than ever. Just import the extracted dfp-playground-maven-project download into Eclipse, modify the appengine-web.xml file (in the src/main/webapp/WEB-INF directory), and run the DevAppServer.launch profile in the eclipse-launch-profiles folder.
With Google Plugin for Eclipse
We also heard you loud and clear that not everyone uses Maven, so we’ve added a Google Plugin for Eclipse project download which includes all jar dependencies. As with the Maven project, just extract the dfp-playground-jars-and-google-eclipse-plugin-project download, import it into Eclipse, add Google App Engine functionality to the project, modify the appengine-web.xml file (in the war/WEB-INF directory), and run the project like any other App Engine project.
If you’d like to learn more, take a look at the README. As always, we are open to any feedback, so please don’t hesitate to leave us any feature requests in the issues section. Also, if you’d like to contribute to the project, we welcome any patches (just make sure you become an official contributor first).
In the coming months, we’ll be adding even more functionality to the application, so stay tuned and happy hacking!
Source: Google Ads Developer Blog
AdWords and DoubleClick Ad Exchange SOAP API users – Only two months left to migrate from ClientLogin to OAuth 2.0!
We have plenty of resources to help you migrate. It might take longer than expected to migrate to OAuth2, especially if you don't already use a single top-level MCC to manage your AdWords accounts or if you are a DoubleClick Ad Exchange customer.
Start your migration as soon as possible and reach out to us early on the AdWords API Forum or the DoubleClick Ad Exchange API Forum with any questions.
Source: Google Ads Developer Blog
Google Mobile Ads Unity Plugin 2.1 Adds Interstitial Support
Today, we’re delighted to announce the launch of the Google Mobile Ads Unity Plugin v2.1, now with interstitial ads. You can start playing around with the latest code by grabbing the v2.1 Unity package on GitHub.
Interstitial Ads
There are four steps required to integrate interstitial ads:
- Create a new InterstitialAd, specifying your interstitial ad unit ID
- Register for the ad events you care about
- Load the
InterstitialAd
with an AdRequest - Show the
InterstitialAd
at an appropriate place in your app
The first three steps can be performed at the same time, and can even live in its own helper function:
public InterstitialAd CreateAndLoadInterstitial() {
// Initialize an InterstitialAd.
InterstitialAd interstitial = new InterstitialAd("MY_AD_UNIT_ID");
// Register for ad events.
interstitial.AdLoaded += delegate(object sender, EventArgs args) {};
interstitial.AdFailedToLoad += delegate(object sender, AdFailToLoadEventArgs args) {};
interstitial.AdOpened += delegate(object sender, EventArgs args) {};
interstitial.AdClosing += delegate(object sender, EventArgs args) {};
interstitial.AdClosed += delegate(object sender, EventArgs args) {};
interstitial.AdLeftApplication += delegate(object sender, EventArgs args) {};
// Load the InterstitialAd with an AdRequest.
interstitial.LoadAd(new AdRequest.Builder().Build());
}
You should wait to show the interstitial until a good stopping point in your app, for example when the user finishes a level in your game. Remember to check that the interstitial has finished loading before you show it:
// Call this when a level finishes.
public void LevelFinished() {
if (interstitial.isLoaded()) {
interstitial.Show();
}
}
Keep in mind that an interstitial is a one-time use object. Once the interstitial is closed, you can dispose of the object and prepare another one. This can be implemented directly in the AdClosed
event.
interstitial.AdClosed += delegate(object sender, EventArgs args)
{
interstitial.Destroy();
interstitial = CreateAndLoadInterstitial();
};
Ad Events now use EventHandlers
In this release, we also changed our ad events to be of type EventHandler instead of Action for both BannerView
and InterstitialAd
. This means your callback methods now take an object
representing the event sender, and an EventArgs:
interstitial.AdLoaded = delegate(object sender, EventArgs args)
{
print(“Interstitial Loaded”);
};
The only event with special event args is AdFailedToLoad
. It passes an instance of AdFailedToLoadEventArgs with a Message
describing the error.
interstitial.AdFailedToLoad = delegate(object sender, AdFailedToLoadEventArgs args)
{
print("Interstitial Failed to load: " + args.Message);
};
The source code as well as a sample app for the plugin is available on our googleads-mobile-plugins GitHub repo. If you have any questions about Unity integration, you can reach us on our forum. Remember that you can also find us on Google+, where we have updates on all of our Google Ads developer products.
Labels: mobile_ads_sdk, unitySource: Google Ads Developer Blog
IMA SDK Moving Off of s0.2mdn.net
What is happening?
If you pay close attention to your network traffic, you’ve probably noticed that the IMA SDK is hosted on s0.2mdn.net. Last week we started migrating traffic from this domain to imasdk.googleapis.com. This will be a gradual migration - we will not move all traffic at once. Instead, we’ve started putting all HTML5 traffic on the new domain. Flash and native SDKs will follow shortly. For updates on our progress, check out the "Domain Migration Status” forum thread. The old domain will continue to work for the remainder of the year, but we encourage you to move early.
What this means for you
Flash publishers
Re-download the implementation swc from our downloads page, recompile your app, and re-deploy. This only needs to be done after the Flash migration starts - we’ll let you know when that will happen on the aforementioned forum thread.HTML5 publishers
Start loading the ima3.js file from the new domain (http://imasdk.googleapis.com/js/sdkloader/ima3.js).Native publishers (Android and iOS users)
You should not be affected by this change.As always, if you have any questions feel free to contact us via the support forum.
Source: Google Ads Developer Blog
Announcing New Google Mobile Ads SDKs: 4.4 for Google Play Services and 6.9.2 for iOS
Today, we’re excited to announce a new release to both our Android and iOS Google Mobile Ads SDKs. The key new features added in these releases are in-app purchase ads for both platforms and new mediation APIs for Android.
In-App Purchase Ads
In this release we’ve added SDK-level support (front-end support coming soon!) for running house ads that can initiate an in-app purchase. In-app purchase ads require that you set an in-app purchase listener on your interstitial ad. If an in-app purchase ad is shown, it will present the user with an option to buy one or more items that you have configured:
When the user clicks Buy now, the SDK will invoke your in-app purchase listener with the purchase information necessary to start a transaction for that product. You are responsible for implementing the in-app purchase flow from this point. Full implementation details can be found in our Android and iOS documentation.
Note: Front-end support for this feature is not available yet, but is coming soon.
New Mediation APIs
As part of our Google Play services API revamp, we’ve added new mediation APIs (which we’re calling mediation v2) to make it easier for ad networks to create mediation adapters.
Don’t worry! We’re still supporting mediation adapters written against mediation v1 APIs. This change won’t require any immediate updates to your apps.
If you previously passed extra parameters to third party networks, note that this process has changed for mediation v2. You’ll now pass a bundle to the ad network, keyed by its mediation v2 adapter class. Here is an example of passing extra parameters to AdMob:
Bundle adMobBundle = new Bundle();
adMobBundle.putString("color_bg", "AAAAFF");
AdRequest request = new AdRequest.Builder()
.addNetworkExtrasBundle(AdMobAdapter.class, adMobBundle)
.build();
You can also use this snippet to check for the existence of mediation v2 support. If this snippet compiles, then the adapter supports mediation v2. If there is a compilation error saying that the arguments don’t match the arguments for addNetworkExtrasBundle(Class extends MediationAdapter>, Bundle)
, then that adapter class does not support mediation v2.
See the documentation for more information on passing parameters to mediation v2.
Dropped Support for iOS 4.3
The 6.9.2 iOS SDK release has dropped support for iOS 4.3. By dropping iOS 4.3, the SDK can take advantage of automatic reference counting (ARC) weak references to provide a more stable release. The SDK still supports iOS 5.0 and above.
Check out the downloads page to grab the latest iOS release. A new Google Play services revision will soon be available in Android’s SDK Manager.
For a full list of SDK changes, see the release notes. If you have any technical questions about these changes, we’re available on the forum. Finally, stay tuned for an update on front-end support for in-app purchase ads on our Google+ page.Source: Google Ads Developer Blog
Introducing MCC Scripts: Efficient Management across Accounts
To get started with MCC scripts, log in to your My Client Center account, and navigate to My Client Center->Scripts.
Here are some of the ways you can save time with MCC scripts:
- High quality cross-account reports: Generate well-formatted custom reports in HTML, PDF or Google Spreadsheets for all your client accounts. You can save these reports to Google Drive, to an external server, or include them as an email attachment.
- Cross-account optimization: Analyze performance and adjust bids in all your client accounts at scale.
- Troubleshooting and maintenance tools: Scan your client accounts for potential issues like paused campaigns, broken URLs, capped budgets, conflicting negative keywords, etc.
- Getting started guide: Our getting started guide provides a technical overview of MCC scripts and how to use it.
- Reference docs: Refer to the technical reference for MccApp at https://developers.google.com/adwords/scripts/docs/reference/mccapp/index
- Code snippets: Not sure how to use a particular feature? You can click the “Show examples” button on the Scripts editor or refer to our code snippets page to view a list of code snippets for the most common use cases in AdWords scripts. We have expanded this section to include snippets that shows various features of MCC Scripts.
- Solutions: Looking for some ready-to-use scripts? Check out our solutions section, which we've just expanded to include solutions specifically tailored to MCC.
Source: Google Ads Developer Blog
AdWords scripts – New code snippets are now available!
We hope you find these new code snippets useful. If you wish to see more code snippets or have feedback about the new ones, let us know on our developer forum. You can also follow our Google+ page for updates about AdWords scripts.
Source: Google Ads Developer Blog
Changes to AdWords scripts execution logs
Starting May 15, 2014, we will only retain detailed execution logs for scripts that ran during the last 90 days. If you need to retrieve changes made by scripts from an earlier date, you can refer to your account’s change history.
If you have any questions about this change, let us know on the forum or on our Google Ads Developers Google+ page.