Thanks to everyone who was able to make it to the recent Ad Manager API Workshop in New York. As always, it was great to connect with the developers who use our API. If you are interested in the content that we covered, you can now access the combined slide deck from the workshop talks.




We’ve already begun planning for our 2019 workshops, so be sure to check this blog for more updates. If you have general API questions or comments, please reach out to us on the Ad Manager API forums.

A huge thank you to the 300+ viewers from 44 different countries who joined recent Google Ads API: Roadmap and migration webinar on Tuesday, Dec 11. Also, a special mention to the great YouTube chat group in the second webinar who helped us sort out some technical issues at the start of the live stream!

We had tons of good questions to answer in the Q&A and hope the event proved helpful to everyone.

For those who couldn’t attend the live stream and anyone wanting a copy of the presentation, we’ve provided links to both the slide deck and YouTube recording of the 9am (GMT+8) webinar: Please visit the Google Ads API developer site for technical docs, migration guides, or to give feedback.

And, as always, don’t hesitate to contact us via the forum if you have any questions.

AdWords API v201802 will be sunset on January 30, 2019. After this date, all v201802 API requests will begin to fail. We recommend that you skip v201806 and migrate directly to v201809. Please migrate prior to January 30, 2019 to ensure your API access is unaffected.

We've prepared various resources to help you with the migration: If you have questions while you’re upgrading, please reach out to us on the forum.

Starting on Jan 8, 2019 you will be able to target and generate reports for a new device category via the AdWords API - connected TV. The connected TV platform, (or “TV screens,” as it’s referred to in the new Google Ads experience), is a new Platform type similar to desktop, tablet, and mobile. It targets devices such as smart TVs, gaming consoles and standalone connected devices including Chromecast, Roku, and AppleTV.

Since connected TV shares the same functionality as the three existing platforms, you can target or exclude it using bid modifiers for Display/Video ad campaigns; the new criterion will have a platformName of “ConnectedTv” and an ID of 30004. You can also isolate it in reports using a Device segment named CONNECTED_TV. Note that even though bidding will only be supported for Display and Video ads, some residual traffic may appear in other kinds of reports so you should still pull the new segment for non Display/Video ad reports.

The new connected TV device segment will be available anywhere Device-level or Device-segmented reporting is available. Currently any reporting data related to this platform is consolidated under the Desktop platform.

For more background on device targeting see the Help Center.

If you have questions, please reach out to us on the AdWords API forum.

Last week we announced the v0_6 beta release of Google Ads API, a major milestone for the beta program that makes many core Required Minimum Functionality (RMF) features available in the new API. To complement this release, we’re holding a live stream webinar on the following dates and times. The presentation will cover the following topics:
  • Recap of the Key Advantages of the Google Ads API
  • Latest beta program updates
  • Future roadmap of both the Google Ads API and the AdWords API
  • Tour of key new features
  • Migration strategies
You can submit any questions ahead of time so that we can answer them during the webinar. We want to make sure we answer all of your questions!

As always, please contact us via the forum if you have any questions or need help.