Google Ads Developer Blog

AdSense Management API v1.3 Released

2013-06-18T05:51:00.000-07:00

Version 1.3 of the AdSense Management API is now available and comes with new features to help you retrieve more publisher and reporting information.

Metadata for reporting dimensions and metrics
This is a highly requested feature that provides information on the list of available dimensions and metrics for the publishers, as well as their compatibility. This is useful to help developers avoid generating reports with invalid dimensions and metrics.

Alerts
You can now list the publisher’s current alerts, in their default language or in the one you specify.

Ad code
You can now programmatically fetch the code of an ad unit using getAdCode.

Remember to visit the AdSense API forums or our Google+ page if you need any help implementing these new features!

- Jose Alcérreca, AdSense API Team

Hobbyist game developers turn passion into business with Google AdMob

2013-06-12T09:14:00.000-07:00

Kunal Verma and William Ferguson never imagined that coding for fun would one day become more than just a pastime. Both developers now independently run their own app businesses, Verma’s XigXag Interactive is a full-time job in India and Ferguson’s XandarMob is a side gig.

Verma’s apps have reached 1.5 million downloads on Google Play, his most popular ones, such as Kids Musical Toys Set, are catered to children. AdMob’s ad content control options are particularly useful for the demographic he serves. Verma’s apps are 100% free with a steady 99.09% fill rate. With AdMob, he makes 3x more income than he would at a regular IT job in India.

Ferguson’s word scramble app, Lexathon, has been translated into 19 different languages and downloaded 430,000+ times by a loyal user base that spends an average of 10 minutes on the app per day. AdMob Mediation allows Ferguson to maximize his fill rate and leverage multiple ad networks to increase his total revenue.

Find out how these indie game developers used AdMob to make a living from their hobby. Download PDF versions of the XigXag case study and XandarMob case study.

Posted by Robin Lam, Mobile Ads Marketing

Optimization Series - Implementing Best Practices

2013-05-31T12:35:00.000-07:00

In our previous blog posts, we discussed post-filtered bids and disapproved ads. In those posts we recommended integrating tools such as the Creative REST API, Snippet Status Reports, and Publisher Settings File into your bidder as best practices to improve the efficiency of your application.

Today, we'd like to share how to integrate these tools into your setup.

Why implement these tools into your bidder?

As a recap, here are our suggested best practices and why we feel they are beneficial for your bidder:

The Creative REST API is a proactive measure that provides methods for submitting a creative for verification, for checking the status of a creative that you have submitted, and for retrieving a list of all your active creatives before bidding on the creative ad. By using the Creative REST API to submit and manage your campaign creatives, you’re able to ensure that your bidder is better prepared to bid with an approved creative.

If you are unable to implement the Creative REST API, the Snippet Status Report can also help you review and determine the exact reason for which your ad was disapproved. The snippet-status-report-proto.txt file lists all the issues described in the section of the report. The snippet status report will also show ads that are approved or have not yet been checked by our verification system.

Publisher Settings File is a list of exclusions set by AdX publishers that will block bids from winning the auction for their inventory. Buyers should take note of and adhere to these publisher requirements. By leveraging the Publisher Settings File, your bidder can ensure it does not bid on an ad that will be filtered out of the AdX auction due to an exclusion. By only bidding on eligible impressions, you can avoid wasting bids.

How to incorporate these tools into your bidder?

Below is a sample visual representation of how you can integrate the Creative Rest API, Snippet Status Report and Publisher Settings File into your bidder’s logic to maximize the efficiency of your bidder:

1. Upload creatives from your ad repository/server using the Creative REST API.

2. Use the Snippet Status Reports or Creative REST API to periodically find the creative status (APPROVED, DISAPPROVED, NOT_CHECKED). Update the creative status in your ad repository/server. To avoid wasted bid opportunities, ensure that your bidder only returns BidResponses with APPROVED creatives. Creatives with DISAPPROVED or NOT_CHECKED status will not be eligible to compete in auction. Read more about post-filtered bids.

3. Use categorization data from the Snippet Status Reports or Creative REST API to help match creatives during targeting and avoid getting post-filtered. We use two types of categories, product and sensitive.

Product categories (ex. Banking, Real Estate, or Sports) will be identified by a detected_product_category.
Sensitive categories (ex. Dating, Politics, or Religion) will be identified by a detected_sensitive_category.

If a publisher has category exclusions, they will appear in BidRequests within the excluded_product_category and excluded_sensitive_category fields. Your bidder should honor these category exclusions by ensuring that it only returns BidResponses with creatives that are not categorized in an excluded_product_category or an excluded_sensitive_category.

4. Periodically pull the Publisher Settings Files to incorporate publisher exclusions into your targeting engine to minimize the chance of returning creatives that will be blocked by publishers. It might not be feasible to load all publisher data, but you may consider concentrating on the top N publishers on which your creatives run or publishers that you explicitly target. Publisher Settings Files contain valuable information such as excluded_attribute, excluded_product_category, excluded_sensitive_category and excluded_url. See the complete proto file.

Note: In order to reduce the size of the bid request, BidRequests do not contain excluded_url. Therefore, the only way your bidder will know what advertiser URLs the publisher is excluding is through the Publisher Settings Files. Your bidder should honor URL exclusions by ensuring that it only returns BidResponses with creatives that declare click_through_url’s that are not excluded by the publisher.

Have questions or want to enable any of the tools mentioned? Reach out to your Ad Exchange account team.

Posted by the Ad Exchange Team

DFA Reporting API Version 1.2 Released

2013-05-30T12:10:00.000-07:00

We’re pleased to announce the newest DFA Reporting API release, version 1.2. This version’s main additions include paid search dimensions and a way to view all reports and files in your account, not just those that you own.

Paid Search

Paid search dimensions have been added to the API with this release. We also added support for these new dimensions to version 1.1, but only version 1.2 contains the new matchType field in the DimensionValue resource allowing you to filter paid search dimensions by one of the following:

EXACT
CONTAINS
BEGINS_WITH
WILDCARD_EXPRESSION

Report Sharing

We have added the ability to list all reports and files in your DFA account (in addition to those owned by you). You may also optionally list just those files that have been shared with you using the Files resource. You can find this option in the scope parameter in the input to the respective list methods.

Refer to the release notes in our developer documentation for more details. We’re always available to answer your questions on our forum, or you can reach out to us on our Google+ Page.

- Joseph DiLallo, the DFA API Team

AdWords API v201209 will sunset on July 22nd, 2013

2013-05-28T08:20:00.000-07:00

The sunset date for v201209 of the AdWords API has been extended to July 22, 2013. This will provide you with additional migration time while you are exploring the newly launched Enhanced Campaigns functionality.

Calls made to this version after July 22, 2013 will fail. It is therefore important that you migrate to AdWords API v201302 if you want your applications to continue to run without interruption.

If you have any questions about the sunset or need help with migration, please contact us on the forum. You can also reach out to us on Google+ page.

- Stan Grinberg, Ads Developer Relations Team

Recorded Ads sessions from Google I/O

2013-05-22T16:57:00.000-07:00

Last week at Google I/O, we had a Google Ads Track where we provided updates on our Google Ads products. We also made some product announcements, including the launch of a new AdMob to help you build your app business and Open Bidder to help you create real-time bidding applications.

If you weren’t able to attend these sessions in person or watch the live stream, we have recorded them for your convenience:

Share your thoughts on our Google+ page and tell us which session was your favorite!

- Eric Leichtenschlag, AdMob Team

‘Hill Climb Racing’ grows from an app into a business, using AdMob

2013-05-22T09:43:00.000-07:00

Toni Fingerroos, a games developer in Finland, became inspired to create a mobile app. He devoted 3 months to building it, often working 16 hour days. That idea became the hugely popular Hill Climb Racing, and the game has grown to be part of a successful app business called Fingersoft.

Hill Climb Racing has been downloaded in over 145 countries on both iOS and Android. AdMob consistently generates nearly 100% ad fill rates and enables Toni to monetize the game on a global scale. He uses AdMob house ads to promote his app too.

“Hill Climb Racing has over 60 million downloads. About 40% [of the revenue] comes from advertisements, and AdMob is our cornerstone,” says Toni. Hear more about Toni’s story in the video below.

Download the PDF version of the case study here.

Posted by Mike Schipper, Product Marketing Manager, AdMob

AdWords API: Upgrading your Ad Extensions

2013-05-20T16:30:00.000-07:00

We recently announced upgraded ad extensions that provide many new capabilities, including mobile-optimized settings, new scheduling features, and detailed reporting at the individual sitelink level. We’ll be helping all advertisers transition to these improved extensions over the coming months. Starting on September 23, 2013, the AdWords API will support only these upgraded extensions, including the 25-character sitelink limit, and we’ll begin automatically upgrading legacy extensions to the new format.

We recommend upgrading your extensions ahead of September 23, 2013 so you can take advantage of all the new features and customize specific settings. Most advertisers are upgrading their extensions as part of their overall upgrade to AdWords enhanced campaigns. To help make the process easy for you, we’ve put together a number of resources:

The feed services can help you create and retrieve upgraded ad extensions
Our upgrade guide as well as a complete code example in Java provide best practices
Our client libraries provide full support for various feed services and code examples that show how to use them
The AdWords API Required Minimum Functionality document is updated with information about how feed services can be used to create and manage upgraded ad extensions

As you are upgrading, you can create upgraded ad extensions while still keeping legacy ad extensions in the same campaign; however, only the upgraded extensions will be served. Beginning on September 23, if a campaign only has legacy extensions, we will auto-upgrade them to the new format. If a campaign has both legacy and upgraded extensions, we will only serve the new format, and legacy extensions will be marked as deleted.

If you have questions or need help with the upgrade, please visit us on the developer forum, or at one of the upcoming GDL Office Hours.

- Anash P. Oommen, AdWords API Team

Announcing Open Bidder [BETA]: A Platform for Real-Time Bidding Innovation

2013-05-20T05:56:00.000-07:00

Thursday at Google I/O 2013, we announced Open Bidder, a fully customizable toolkit for building real-time bidding applications. By combining the speed and flexibility of the Google Cloud Platform with DoubleClick’s expertise in real-time bidding, Open Bidder provides developers a robust platform to quickly create innovative RTB solutions.

Currently, companies interested in building their own real-time bidding technology face significant barriers to overcome, including:

Development and maintenance of a scalable and secure infrastructure for their bidder
Development of a robust system to apply bidding logic to incoming bid requests
Development of a bidder with sufficient latency at scale to meet real-time bidding requirements

Open Bidder removes these barriers by providing a customizable bidder toolkit with a reference implementation that developers can adapt to plug in their own bidding logic and data. Additionally, we provide an administration console for managing bidder and load balancer instances within Google Compute Engine. With Open Bidder buyers can significantly lower the latency of their bidders by leveraging Google Compute Engine’s scale, speed, and proximity to DoubleClick Ad Exchange. Now buyers can focus on developing new and innovative bidding logic instead of worrying about the complexity of scaling to over 250,000 qps while responding in under 100ms.

We’ve been working on Open Bidder for over a year, and over that time we’ve been fortunate to have some fantastic alpha testers that have helped us develop and improve the product. Going forward, we’re excited to see what brilliant ideas developers can bring to advertising through Open Bidder. If you’re interested in being a Beta tester, please submit an application here.

More details about Open Bidder can be found in our Beta documentation. To stay up to date on all of our ads-related technologies follow our Google Ads Developers Google+ page.

- The Open Bidder Team

Introducing a new AdMob: Improved tools to help app developers build their business

2013-05-16T09:18:00.000-07:00

We’re committed to helping app developers with discovery, distribution and monetization on all platforms so they can continue doing what they do best: creating awesome apps. Last year, we integrated our AdMob inventory into the AdWords system, giving mobile app developers access to many more new advertisers. And we’ve continued to invest in tools to help app developers succeed.

Today at I/O, we’re announcing that we’ve rebuilt AdMob, incorporating the best technology from our other ad platforms, like AdSense. It’s a particularly great tool to help small mobile app developers grow their business.

Starting today, we’ll begin rolling out the new AdMob to our developers. We expect it to be available for all of our developers globally in the coming months. If you’re an AdMob developer, you’ll see a notice in your account asking you to upgrade to the new AdMob.

With the new AdMob, some of the features available are:

Smarter app promotion: Conversion Optimizer helps many AdWords advertisers increase conversions while decreasing cost per acquisition. We’re now bringing Conversion Optimizer to app developers using AdMob to promote their apps, so they can get the best possible number of installs for their budget. Choose a target cost per acquisition for each download, and Conversion Optimizer will show ads when they are most likely to lead to an install.
Robust ad filters: Ensuring that your app is showing quality, relevant ads is important for app developers. Now, developers will have more control over which ads appear in their apps, by blocking sensitive categories, so they can increase relevancy and protect their brand.
Maximized earnings: If developers want to show ads in their apps from more than one ad network, they can use AdMob Mediation with a new, simplified setup.
Local payments: We’re introducing local currency payments, so developers don’t need to spend time calculating currency conversions and organizing money transfers.
Intelligent reports: The new reporting interface enables app developers to slice the data in many ways with multi-dimensional reports that help them identify opportunities to grow. They can break down their reports over time by app or ad unit, platform, country, bid type, and more.

If a developer is just starting out, AdMob can connect them to more than a million advertisers globally, providing a consistent source of advertising revenue which can grow as their downloads take off.

We want AdMob to open up opportunities for many more app developers worldwide to help them build successful businesses. Join us at Google I/O at 11:15 AM PST today or watch a livestream of our talk: Build a Great App Business with AdMob, and see new demos.

Posted by Vishay Nihalani, Product Manager, AdMob

Announcing the recorded talks for the AdWords API Workshops 2013

2013-05-14T09:24:00.000-07:00

We’re pleased to announce that the recorded talks for the AdWords API Workshops are now available. The talks are from the workshop in New York, but we had the same agenda for all other locations. The major topics include

Enhanced Campaigns and New Extensions Support
New & Improved MCC Services
OAuth2 authentication
New Bidding & Budgeting
Account Performance Tracking & Optimization (and introducing a new tool - Kratu)

We have made available all presentation slides used in the workshop. We hope this is useful for those who attended other locations or didn’t attend the event in person.

- Takeshi Hagikura, AdWords API Team

We’re going live from Google I/O

2013-05-09T09:09:00.000-07:00

Editor's note: repost from Developers Blog, --Stan Grinberg

At Google I/O 2013, we will share the future of our platforms with you. Developers from all over the world are the key innovators of powerful, breakthrough technologies, and that’s why we challenged ourselves to make the Google I/O experience available to every developer, everywhere.

Watch Google I/O live
From the comfort of your own home, office, secret lair, or anywhere you have a reliable Internet connection, you can stream Google I/O May 15-16 live. Brought to you by Google Developers Live (GDL), the Google I/O homepage will become the GDL at I/O live streaming hub starting on May 15th at 9:00 AM PT (16:00 UTC). From this page, you can:

Stream 4 channels of technical content on your computer, tablet, or phone. You’ll feel like you’re right there in the keynote and session rooms, listening to product announcements straight from the source. Live streaming will run on developers.google.com/io from 9 AM PT (16:00 UTC) to 7 PM PT (2:00 UTC) on May 15 and 16.
Watch exclusive interviews with the Googlers behind the latest product announcements. This year, GDL will be on site, broadcasting one-on-one product deep dives, executive interviews, and Sandbox walkthroughs from the GDL stage.
Get the latest news in real-time. We’ll be posting official announcements during I/O. You’ll be able to see the feed on the Google I/O homepage, in the I/O mobile app (coming soon), and on +Google Developers.
Never miss a session. All Google I/O technical sessions will be recorded and posted toGDL and the Google Developers YouTube channel. Subscribe to our YouTube channel for archived session updates.

Live blog the keynote
Grab our live blogging gadget to add the keynote live stream to your own site or blog. Customize the gadget with your site or blog name, live blog alongside real-time Google announcements, and share a dynamic Google I/O experience with your readers. Have questions? For more info, check out our live blogging gadget FAQ.

Get together locally
Experience Google I/O with your local developer community by hosting or attending an I/O Extended event. If you’re hosting, register here and learn how to hold a totally epic event with our handy Organizer Guide. Otherwise, with over 400 sites in 90+ countries, chances are good that there is an I/O Extended event near you. Find an event now!

And before I/O, tune in to Google Developers Live programming to connect with Google engineers, prep for this year’s event, and browse our archived content. For official conference updates, add +Google Developers to your Circles, follow #io13 for big announcements, join the Google I/O community, and keep an eye on the Google I/O site.

--Mike Winton, Director of Developer Relations

Visual representations of the IMA SDK / Video Player integration are now available

2013-05-07T11:42:00.000-07:00

We recently created two visual representations, the Basic SDK Interaction Diagram and the SDK-Player Interaction Diagram, that illustrate the actions that occur once your video player is fully integrated with the v3 IMA SDK. These diagrams outline both:

the high level interactions that take place among the IMA SDK, DoubleClick for Publishers (DFP), AdSense for Video (AFV), Ad Exchange (AdX) and any third party ad servers
the more detailed communications that take place between the IMA SDK and your video player

The diagrams are meant to assist you when integrating your video player with the v3 IMA SDK. They can help to visualize the interactions that are taking place when video content and ads are being played (as well as the sequence in which these actions are occurring). Both diagrams are available within the left-hand navigation of the IMA SDK documentation under Resources and are linked to directly from within the IMA HTML5 SDK and IMA Flash SDK Working with Ads pages.

Feel free to contact us on the forum if you have any questions about these new learning tools and if you found them useful (or use the Feedback on this document link on the page). You can also reach out to us on our Google+ page.

- Joe Roepcke, IMA SDK Team

Localized documentation for IMA SDK v3 is now available

2013-05-06T07:57:00.000-07:00

We are pleased to announce that updated localized editions of the IMA SDK v3 documentation are now available for the following languages:

Spanish
Japanese
Korean
Brazilian Portuguese
Russian
Chinese (Simplified)
Chinese (Traditional)

To view the localized edition of the latest documentation, be sure to select the desired language from the menu in the footer of any page.

Let us know on the forum if you have any questions about our localized content (or use the “Feedback on this document” link in the upper right-hand corner of any page). You can also reach out to us on Google+ page.

- Joe Roepcke, IMA SDK Team

AdMob eCPM Floor Beta: Best Practices

2013-05-02T14:10:00.000-07:00

We recently announced the ability to set an eCPM floor when making requests to the AdMob network. This post will show you how to set up this new feature to get the maximum benefit from the AdMob network.

First of all, we highly recommend that you create a new AdMob publisher ID on admob.com for each Mediation Placement you want to configure with AdMob eCPM floor. By creating a unique publisher ID, you’ll get fine grained reporting on how eCPM floor is performing on each of your placements.

Next, select Add Ad Network on your mediation placement, and add the AdMob eCPM Floor Beta network. In the Ad Network Configuration Settings, point this network to your newly created eCPM floor publisher ID.

Note: If you didn’t previously have a mediation placement, you’ll need to create a mediation placement on mediation.admob.com, and use the mediation placement ID in your application in place of your AdMob publisher ID.

Finally, you need to update your allocation to give the AdMob eCPM Floor Beta network an eCPM value. A suitable value for the eCPM floor is a value higher than the highest eCPM you’re getting from other networks.

In the sample below, Ad Network A is getting $0.37 eCPM. By setting AdMob eCPM Floor Beta slightly higher at $0.40, AdMob Mediation will first try to fetch an ad worth $0.40 eCPM from the AdMob Network. If it can’t fill that request, Mediation will try Ad network A, followed by Ad network B. If neither of those networks can fill the request, Mediation will come back to the AdMob network to fetch an ad without the eCPM floor restriction.

This new configuration will increase your ad revenue for requests fulfilled by AdMob eCPM Floor Beta, while still maintaining the same revenue from the rest of your requests where AdMob cannot fill the eCPM Floor request. You can also track your eCPM Floor performance by viewing sites and apps reporting for your newly created eCPM floor publisher ID.

If you have any questions about eCPM Floor or AdMob in general, please direct them to our forum. You can also follow us on our Google+ page to get updates on all Google ads developer products.

- Eric Leichtenschlag, AdMob Team

Ad group mobile bid adjustments are now available within AdWords API

2013-05-01T13:09:00.000-07:00

To provide more control and precision over bids in enhanced campaigns, we’ve now made ad group level mobile bid adjustments available in the AdWords API, as previously announced.

While the majority of advertisers will still see the most value in using the existing campaign level bid adjustments, this new feature will be useful for those who wish to set different mobile bid adjustments within an enhanced campaign. The functionality is accessible via the new AdGroupBidModifierService for all currently available AdWords API versions. It is not required to migrate to a different version of the API to use this new service. Please refer to this guide covering technical aspects of the release.

The new feature is only available for enhanced campaigns, so if you haven’t upgraded yet, now would be a good time. As a reminder, we will begin automatically upgrading all AdWords campaigns to enhanced campaigns starting on July 22, 2013.

If you have any questions regarding this new feature or enhanced campaigns, feel free to ask us on the forum, during office hours or via the Plus page.

- Danial Klimkin, Ads Developer Relations Team.

Announcing v1.20 of the DFA API

2013-04-23T09:14:00.000-07:00

We’re pleased to announce the availability of version v1.20 of the DFA API. This latest release exposes many new properties on the objects in our API. These new fields are useful for customers interested in generating match tables. A full listing of these additions can be found in our release notes page.

Version v1.20 can be thought of as an optional release. Since v1.20 is an optional release, it and v1.19 will both remain usable once your account is upgraded to use DDMM. If you don’t require access to the new fields exposed in this version, you do not need to update your application at this time. Please remember that v1.18 has been sunsetted.

Questions or comments about this release, performing updates, or anything else related to using our API are always welcome on our forum.

- Joseph DiLallo, the DFA API Team

Google AdMob SDK v6.4.1 Released for Android and iOS

2013-04-18T16:57:00.000-07:00

We have just released version 6.4.1 of the Google AdMob SDK for both Android and iOS. The Android release includes:

The ability to resize a DfpAdView using dfpAdView.resize(AdSize)
A fix for the ANR errors seen in v6.3

The iOS release fixes a crash that occurs if the Advertising Identifier is nil.

You can get the latest SDKs from our downloads page. Find us on the forum if have questions about the new Google AdMob SDKs. You can also check out our Google+ page for ads-related updates.

- Eric Leichtenschlag, AdMob Team

AdMob SDK for iOS v6.4.0

2013-04-08T16:15:00.000-07:00

Today we’re releasing version 6.4.0 of the Google AdMob SDK for iOS developers. In addition to the maintenance and bug fixes listed below, this version of the SDK completes the transition away from UDID, which began with version 6.2, in compliance with relevant Apple policies.

There are a number of maintenance updates and bug fixes including:

No longer accesses the UDID
Fix for GADInterstitial crash that occurs when app is running in the background
Fix for GADMRAIDInterceptor threading crash
Renaming symbols to prevent duplicate symbol errors
Support for receiving test ads when using AdMob through mediation
Test ads are only available on devices running iOS 6 and above

Check out the release notes for a full list of updates. You can download the latest SDK from our downloads page. If you’ve got questions or concerns about using the new AdMob SDK, please post to the forum or check out our G+ page.

- Raj Parameswaran, AdMob Team

Polygon targets are sunset - A reminder

2013-04-08T08:43:00.000-07:00

Polygon Criterion, (also referred to as custom shapes, multi-point or polygon targets) was deprecated in 2011. They are now sunset in AdWords as we had previously announced. Until recently, developers were able to retrieve and individually delete any old polygon targets, using Adwords API.

As of now, all the polygon targets in Adwords campaigns have been deleted. You can continue to retrieve any accumulated stats of previous polygon targets using Geo Performance Report.

Please use other location targeting features available in Adwords for your campaigns.
As always, please feel free to ask any questions regarding AdWords API on our forum for AdWords API. You can also follow the Google Ads Developer page for all Ads-related updates.

- Takeshi Hagikura, AdWords API Team

Clarification on running sell through reports in the DFP API

2013-04-01T14:42:00.000-07:00

In the recent DFP v201302 release, we announced that the ability to run sell through reports (STRs) is now available via the API. This has led to a bit of confusion as some developers who are able to run STRs through the web UI received a ReportError.COLUMN_VIEW_NOT_ALLOWED message when using these new dimensions through the API. We would like to clarify how you’ll be able to access STRs.

We are in the process of updating STRs for networks that have them enabled. The current version of STRs isn’t accessible via the API. Once updated, you will be able to run STRs through the API right away as the columns already exist in the report service. Please speak with your account manager about when your network will be updated.

- Vincent Tsao, DFP API Team

Announcing v1.2 of the Ad Exchange Buyer Rest API

2013-03-29T06:14:00.000-07:00

We’re pleased to announce that version 1.2 of the Ad Exchange Buyer REST API is now available. This release provides one of the most requested features— detailed creative disapproval reasons. Additionally, it also provides a new field for creatives that can be used to identify the agency providing the creative and a new field for direct deals that can be used to determine whether a deal originated from a private auction. You may view a more specific listing of the changes implemented in v1.2 in our release notes.

Detailed Creative Disapproval Reasons

The Creatives resource now has an improved disapprovalReasons field. Previously, this field provided a list of strings that described the reason for disapproval in a broad context that may have been somewhat ambiguous. Each element of disapprovalReasons now provides two additional fields— reason and details. One can use disapprovalReasons.reason in order to access a categorized reason for disapproval, or use disapprovalReasons.details to retrieve a list of strings describing the disapproval reason in detail.

Identify Where Your Ads Came From

Publishers now have greater control over their inventory— e.g. with the new inventory management system, they may set rules that could offer special pricing or limit access to a specific set of creative agencies. With the new agencyId field, you can identify the creative agency that produced the ad with one of the IDs listed in agencies.txt, and consequently gain access to publisher inventory that utilizes these features.

Determine Your Eligibility for Private Auction Deals

We’ve given publishers the ability to create private auction deals, which you can read more about in our help center. You can now determine whether you have a fixed price deal or private auction deal by checking the private_exchange_min_cpm field— if it is set instead of the fixed_cpm field, you have a private auction deal. When you bid on ad slots from the publisher offering this deal, you are expected to offer at least the amount provided by this field.

You can read more about the new features in the Buyer REST v1.2 documentation. As always, we welcome you to join us on our forum to discuss and ask questions about these changes. To keep informed on all of our ads-related technologies, follow our Google Ads Developers Google+ page.

- Mark Saniscalchi, Ad Exchange Buyer Team

Introducing the AdMob eCPM Floor Beta

2013-03-27T13:42:00.000-07:00

Today, we’re giving AdMob developers more control over the value of ad impressions served to their apps. The AdMob eCPM Floor beta allows developers to set a minimum CPM they’d like to receive for each ad. The beta is available to AdMob developers who are using AdMob Mediation.

How does this work? Advertisers bid to show their ads on apps in the AdMob network, and an auction is run for every impression to determine the winner. We predict what the ‘expected CPM’ (eCPM) of that ad impression will be. The developer sets a minimum eCPM and we will only serve ads to their app that meet or exceed that level. For example, if a floor of $1.25 is set, we’ll only show ads with an eCPM of $1.25 or more. When choosing a floor value it’s important for developers to look at their own reporting and determine a value that’s relevant to them.

Here are a few details to know when taking part in the beta:

Make sure the eCPMs that are set for other ad networks are accurate.
We don’t guarantee the final value of the eCPM, since we don’t know if a user will click on the ad.

Developers who use the beta have the option of setting just one network line item in their mediation stack which uses the eCPM floor. Or, they can have two network line items, one that uses the eCPM floor and one without, so they can continue to fill impressions at their current fill rate. Setting the eCPM floor at a very high value will likely lead to a decrease in the fill rate.

Find setup instructions in the AdMob Help Center here under the article titled ‘Allocate traffic by eCPM’.

Posted by: Vishay Nihalani, Product Manager, Google

Changes to Content Bidding

2013-03-21T18:21:00.000-07:00

We’re changing the way that bidding works for the display network, by removing implicit ordering and introducing something more simplistic. You can migrate your AdGroups now or allow them to be automatically migrated for you. But before we can explain the new system, let’s take a look at what we’ve got now.

Historically, bidding on the display network has relied on implicit priority orders to determine how to use the criteria added to an AdGroup.

In the current system, criteria-level bid overrides an AdGroup default bid. But since the display network supports up to 6 dimensions of targeting, we often need to pick one of many possible bids to use for a given impression. To do so, we use the following order:

Placement (most specific)
Age
Gender
Topic
Interests and remarketing list
Display Network (AdGroup-level)
Keyword
Default AdGroup Bid (least specific)

to choose which value to use. If a matching placement has a bid, we use that. If not, we look for a matching Age bid, etc. If we get to User Lists/Interests and still have not found a bid override, we look for an AdGroup-level “Display Network Bid”. If that also doesn’t exist, then we take a Keyword bid if there is one. Finally, if we still haven’t found a bid to use, we use the default AdGroup bid.

For further information, see how bids are used on the display network.

Explicit Content Bid Dimension
We will be replacing the implicit order with a single display bid override dimension per AdGroup. Ads serving on the display network will honor bids from that dimension and ignore any bids that may exist on other dimensions. We will use this same override dimension for URL overrides - serving will honor urls from the display override dimension, and ignore urls from any other dimension.

In the new implementation, you will be able to explicitly specify which bid dimension will be used per AdGroup. You can set this by using the new object: BiddingStrategyConfiguration, and the new attribute on the AdGroup object: contentBidCriterionType, both are modified through the AdGroupService. For more information on the new implemenation, please see this guide on Bidding.

Migration
With the introduction of AdWords API version v201302 you’ll be able to manually migrate your AdGroups to take effect as you have been used to with the existing implementation. If you chose not to set these on existing AdGroups, however, for the duration of the migration period, things will continue with the existing order. After the migration period, we will automatically select the most appropriate dimension for each of your AdGroups.

To manually migrate your AdGroups, or to configure new AdGroups, you need to set the contentBidCriterionTypeGroup to the desired CriterionTypeGroup. You can then add new Bids using the BiddingStrategyConfiguration, that can then be selected at a later time.

Please note, by setting the contentBidCriterionType, the AdGroup will be marked as migrated.

Once the manual migration period has ended, those AdGroups that have not been migrated will be automatically migrated to the new structure. The automatic migration will select the contentBidCriterionTypeGroup, for un-migrated AdGroups, based on the existing method of prioritization. All automatically migrated AdGroups can continue to be edited through the API.

Once the automatic migration is complete, the old system of bidding will be retired and all AdGroups will honour the new bid dimension system. Also, once an AdGroup has a contentBidCriterionType, all subsequent changes to the effective bid dimension should be done through the same field.

Reports
With these changes, comes a new report, the PLACEMENT_PERFORMANCE_REPORT which will contain all the information about manual placements. We strongly recommend using this report for queries regarding placement performance, moving forward.

There will also be changes to the AUTOMATIC_PLACEMENTS_PERFORMANCE_REPORT and URL_PERFORMANCE_REPORT to better match the AdWords website.

- Paul Matthews, AdWords API Team

4 days left to migrate out of AdWords API v201206

2013-03-21T14:31:00.000-07:00

On March 25, 2013, we will be sunsetting version v201206 of the AdWords API.

Calls made using this version will not longer work after March 25th. It is therefore critical that you migrate to a newer version for your applications to run without interruption.

We encourage you to use the following resources for a successful migration:

Review the v201302 release notes.
Make sure you’ve made the essential changes laid out in the v201209 and v201302 migration guides.
Review the resources in the AdWords API client libraries.
Attend the office hours sessions, to get face-to-face Q & A sessions.
Make sure your contact information is up to date in your My Client Center account.
Post questions on the forum.
Subscribe to our Google Plus page for news and announcements.

- David Torres, AdWords API Team