Google Ads Developer Blog: ad_exchange

Ads Client Libraries: What's on your Mind?

Tuesday, August 5, 2014

Do you use any of these products?

Then here’s your chance to tell us what you think about the corresponding client libraries, even if you don’t use one of them! Your feedback is very important for us and it helps us to prioritize the most wanted features. If you have any suggestions, feature requests or ideas—it's a great time to let us know!

- Danial Klimkin, AdWords API Team.

Changes to Pretargeting for Ad Exchange Buyer RTB Campaigns

Tuesday, July 8, 2014

DoubleClick Ad Exchange is improving its pretargeting system by creating a new user interface and API resource to configure the inventory your bidder sees. These changes will only impact your RTB campaigns; non-RTB campaigns will continue to be managed as they were before.

Upgrades will begin in mid-July 2014 and all accounts will be upgraded by the end of September 2014. The new functionality has been added to the v1.3 REST API but will be read-only until your account has been upgraded. For additional information, please review the new resource reference and pretargeting guide.

Note that once your account has been upgraded you will still have access to the SOAP API for reporting, budgeting and non-RTB campaigns, but you will no longer be able to use it for pretargeting. If you need the ability to manage your pretargeting settings via the API, then you must use the latest AdX REST API.

If you have questions about these upcoming changes please contact your account manager. For questions about the Ad Exchange Buyer API, check out the Ad Exchange Buyer API forum. Follow our Google+ page for other announcements and updates.

Dean Lukies, DoubleClick Ad Exchange Buyer API Team

AdWords and DoubleClick Ad Exchange SOAP API users - Only two months left to migrate from ClientLogin to OAuth 2.0!

Monday, May 12, 2014

ClientLogin authentication support for the AdWords API and the DoubleClick Ad Exchange SOAP API will sunset along with v201309 on July 21st, 2014. You only have two months left to migrate - don’t wait until the last minute!

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.

- Ray Tsang, AdWords API Team

Reminder: AdWords API v201306 and Ad Exchange Buyer SOAP API v201306 will sunset on March 31st, 2014

Thursday, January 30, 2014

We’d like to remind you that v201306 of the AdWords API and Ad Exchange Buyer SOAP API are scheduled to be sunset on March 31st, 2014. Start your migration to v201309 now to avoid having your API calls fail on the sunset date. If you are still using ClientLogin, we strongly recommend that you also migrate to OAuth2.

The following will help you to migrate to v201309:

Announcement blog post for v201309 — includes highlights of v201309
Release notes — lists every API change and version diffs
Migration guide — includes a listing of breaking changes between v201306 and v201309
Client libraries and samples page — updated official client libraries

ClientLogin to OAuth2 migration

For migration help, contact us on the AdWords API forum or Ad Exchange Buyer API forum. Our Google+ page is also a great resource for keeping up-to-date with the latest announcements and communicating with us.

Mark Saniscalchi, Ads Developer Relations Team

Upcoming extended AdWords API/Scripts, Ad Exchange, and DFP API Downtime

Monday, September 10, 2012

Update: Ad Exchange will be affected by the downtime as well. Please see below for details.

As previously mentioned, we have an upcoming AdWords, Ad Exchange, and DFP service outage. This will occur on Saturday, September 22 -- AdWords, Ad Exchange, and DFP systems will be unavailable from approximately 10:00 am to 8:00 pm Pacific Time (17:00 Saturday to 03:00 Sunday GMT) due to system maintenance.

AdWords
During this time, your campaigns will continue to run as usual (with the settings you established as of 10am PST), but you won’t be able to make SOAP API calls or download reports. Requests to the AdWords API will fail with an HTTP 50x error during the maintenance window. Please also keep in mind that any automated rules scheduled during this time will not run and AdWords scripts will not execute during this period. We encourage you to verify your campaign settings prior to the outage.

Ad Exchange
During this time, your ad serving will continue to run per changes made prior to downtime period, but you will not be able to make API calls to Ad Exchange Buyer SOAP API. On Ad Exchange Buyer REST API, only the Direct Deals related API calls will be affected. For the Ad Exchange Real-Time Bidding Protocol, you will not be able to make changes to pre-targeting settings, everything else should continue to run as usual.

DFP
As mentioned above, ad serving will continue to run per changes made prior to the downtime period. If you use the audience feature in your network, any API call to the AudienceSegmentService service will fail with a SegmentError.UNEXPECTED_ERROR error. Also, if you target any audience segments in your line items, any calls to LineItemService, ForecastService, or LineItemCreativeAssociationService that involve those line items will fail.

We apologize for any inconvenience, and appreciate your patience as our engineers work to keep AdWords, Ad Exchange, and DFP running smoothly.

- Kevin Winter, Ads Developer Relations Team

OAuth in Ads APIs

Tuesday, August 21, 2012

- Kevin Winter, AdWords API Team

Authorization is an important concern when writing software that interacts with Google’s Ads APIs. We’ve recently improved our documentation and published resources documenting how to use OAuth2 with many of our Ads APIs.

OAuth2 is an authorization flow that allows you to direct a user to a specially crafted Google URL where they grant permissions to your software to make changes to their account. With an authorized access token, you can make requests to Ads APIs on the user’s behalf. Benefits include:

Users don’t need to provide a username and password - they just log into Google.
No CAPTCHA challenges.
Limited scope - the user will only be prompted to grant access to a specific part of their account. For example, they could grant access to AdWords without the application being able to see their email or calendar.

OAuth2 is supported by:

The Ads API client libraries supported by Google have built-in support for OAuth2. We’ve included examples demonstrating how to use this feature in all client libraries. See your respective product and language product sites for more information on OAuth2.

We’re also hosting a Google Developers Live event covering how to use OAuth2 on August 23rd. This will be recorded if you can’t make it. If you have any questions about OAuth2, please post on the respective product API forums.

- Kevin Winter, AdWords API Team

Ad Exchange Buyer SOAP API v201109_1 - features available more quickly in dot releases

Friday, May 11, 2012

The Ad Exchange Team is pleased to announce the launch of v201109_1 of the Ad Exchange Buyer SOAP API, a dot release which includes the following services that are relevant to Ad Exchange Developers:

Moving forward, we will use dot releases which will allow us to launch features more quickly; v201109_1 does not start the sunset on prior versions.

The full set of release notes is available here. If you have any questions please reach out to us in the DoubleClick Ad Exchange forum.

- David Torres, AdWords API Team

Announcing new Ad Exchange developer resources

Thursday, March 29, 2012

The Ad Exchange Team is excited to make this set of resources available to our developer community. Below you’ll find new and better ways to work with the Ad Exchange. If you have any questions or feedback, please contact us via the forum.

New website

Built on top of Google’s new developers platform developers.google.com, we’ve created a new site for our community. There you’ll find docs for the real-time bidding (RTB) protocol, the REST API and the SOAP API. Plus, we’ve revamped the docs to make them easier to use and understand.

Access to the Ad Exchange REST API

This API gives you the ability to manage your RTB account configurations, submit creatives and list direct deals. Contact your technical account representative to set up access to the API. Then, try it out before you write a line of code, using the API explorer.

Client library support and code examples in major programming languages

Trying out the client libraries first might save you a lot of time compared to coding directly against the APIs. Also, check out our code examples in your preferred programming language for both the SOAP and REST APIs.

Access to the Ad Exchange Buyer API’s Forum

The Ad Exchange Buyer APIs Forum is a Google-monitored environment for public discussions where you can ask - and, if you like, answer - questions regarding the REST and SOAP APIs.

- David Torres, Ad Exchange Team

Ads Developer Blog

DoubleClick Ad Exchange SOAP API sunset