Thank you to the 100+ viewers from 30 different countries who joined our Google Ads API webinars on Tuesday, May 22! We had some great questions during the Q&A and hope it was helpful for everyone who attended.

For those who couldn’t attend the live events, and for anyone who would like a copy of the presentation, both the slides and a video recording of the event are available below.

• Webinar Video (May 22, 2018) [1 hr, 13 mins]
• Slide Deck

You can find out more about the Google Ads API in our documentation. Please contact us via the forum if you have any questions.

Adam Ohren, on behalf of the AdWords API Team

Using v201805 of the DFP API, publishers can now limit which line items are shown to users in the European Economic Area (EEA) by setting the LineItem.userConsentEligibility field. (Note: this field only takes effect if you have elected to “Limit line items” on the “EU user consent” page.) The userConsentEligibility field can be set to one of three values:

• NONE (default) - Don’t serve for any EEA ad requests
• CONSENTED_ONLY - Don’t serve for non-personalized ad requests
• CONSENTED_OR_NPA - Don’t limit serving

As always, if you have any questions or suggestions, feel free to reach out to us on our forum.

 - Donovan McMurray, DFP API Team

Today we're releasing v3.1 of the DCM/DFA Reporting and Trafficking API. Highlights of this release include:

• Support for in-stream audio creatives
• Landing page mobile deep link management

Details of these and all other changes are covered in our release notes.

Deprecation and sunset reminder In accordance with our deprecation schedule, this release marks the beginning of the deprecation period for v3.0, which will sunset on November 30, 2018. After this date, any requests made against v3.0 will begin returning errors.

As a reminder, API version 2.8 will be sunset on August 31, 2018. To avoid an interruption in service, all users are required to migrate to a newer version before the sunset date.

Learn More As with every new version of the DCM/DFA Reporting and Trafficking API, we encourage you to carefully review all changes in the release notes. For those of you looking to get going right away, updated client libraries are now available. If you're just starting out, the Get Started guide is a great reference to help you get up and running quickly.

Give it a try and let us know if you have any questions!

- Jonathon Imperiosi, DCM API Team

We're happy to announce that v201805 of the DFP API is available starting today. This release brings several new features for DFP Video advertising services, including a new service for DAI authentication and support for CdnConfigurationService actions.

This version also brings support for interstitial and native AdUnits.

For reporting users, v201805 adds support for filtering on many more AD_EXCHANGE dimensions. It also removes several deprecated dimensions and columns.

For a full list of API changes in v201805, see the release notes.

As always, if you have any questions, feel free to reach out to us on the DFP API forums.

 - Chris Seeley, DFP API Team

A few weeks ago, we announced the beta release of the Google Ads API. We're offering an introductory look into this new API, at two different times:

• Google Ads API Webinar, May 22, 2018 @ UTC 1:00 (9:00 AM (GMT+8))
• Google Ads API Webinar, May 22, 2018 @ UTC 13:00 (9:00 PM (GMT+8))

The presentation will cover the new API and its features. Topics include capabilities, architecture, set up, and your first API call.

Please submit your questions now so we can answer them in the webinar. We'd love to hear from you!

If you haven’t had a chance to sign up for the beta, you can still submit an application ahead of the webinar. Please contact us via the forum if you have any questions or need help.
Nadine Sundquist, on behalf of the AdWords API Team

Update (5/17): Starting October 30, 2018, parallel tracking will be required for all AdWords accounts. See the AdWords blog post for details.
AdWords now allows you to enable parallel tracking for all advertisers from frontend and API. People who click your ads will go directly to your landing page while their browser handles click measurement requests in the background. This helps reduce lost visits which can happen if a customer clicks on your ad but never sees your landing page because they navigate away before the redirect from your tracking URL completes.

All ads using third-party click measurement will begin using parallel tracking at a later date. However, you should start developing for compatibility as soon as possible to give yourself enough time for the migration. If you implement your own click measurement server or provide this service to your customers, refer to our newly published guide for help with implementation. If you are an advertiser who uses a third-party measurement solution, reach out to your service provider to prepare for the switch.

If you need additional support, please email us at ads-clicktracking-support@google.com.
 - Anash P. Oommen, AdWords API Team