Read More

Starting on July 1, 2018, all releases of the Google Ads API Client Library for Java will only be compatible with Java 8 (1.8) and higher.

Why this change is happening
The primary reasons for this change are:

• Java 7 was first introduced in July, 2011, and Oracle's support for Java 7 is approaching some key end dates.
• Maintaining support for Java 7 means code examples cannot leverage useful features of Java 8, such as lambda expressions, default methods, and stream API support for collections.
• Supporting Java 9 in the client library will require upgrading several dependencies to versions that may not support Java 7.
• Use of Java 7 among Google Ads API Java Client Library developers is declining, with most users on Java 8 or above.

Next steps
If you are using Java 8 or higher, no action is required.

If you are still using Java 7, you'll have to migrate your runtime to Java 8 or higher. Check out the Java 8 adoption guide from Oracle to get started.

Still have questions? Feel free to file an issue on the library's issues page or contact us via our Google+ page.
- Josh Radcliff, AdWords API Team

Read More

We have added support for AdWords API v201802 reports in AdWords scripts. The key changes in this release include:

• A new report type, LANDING_PAGE_REPORT, to provide performance stats for the pages that receive traffic from your ads.
• ConversionLagBucket field added to various reports to help you determine how long it takes customers to convert.
• New fields added to support Gmail ads.

Read the AdWords API release notes for complete details, including additional features not listed here.

If you use API versioning in your reports, you need to modify your code to use v201802:

var report = AdWordsApp.report(query, {
  apiVersion: 'v201802'
});

If you don't use API versioning, no code changes are required. We are updating the default reporting version to v201710 along with this change, and your reports will upgrade automatically.

If you have any questions about these changes or AdWords scripts in general, you can post them on our developer forum.
- Mike Cloonan, AdWords API Team

Read More

Today, we're announcing the ability to configure your local inventory ads (LIA) settings and link Google My Business (GMB) accounts via the Content API for Shopping. This allows you to onboard accounts for LIA programmatically, instead of needing to manually configure each account separately via the Merchant Center website.

The new Liasettings service lets you perform the following actions via the Content API:

• Set your target countries for LIA service and their About pages (if needed)
• Add and check the status of contacts for local inventory verification
• Request access to a GMB account
• Request available business accounts from a linked GMB account
• Request and check the status of local inventory verification

In addition, the new googleMyBusinessLink field in the Accounts resource states which business account should be linked. After setting this field, you can provide inventory information for the locations in that business account by uploading product and inventory information either through local product feeds and local product inventory feeds or through the Content API for Shopping with the channel field set to "local".

If you have any questions or feedback about these new features or any other questions about the Content API for Shopping, please let us know on the forum.
 - Stevie Strickland, Content API for Shopping Team

As previously announced, as of March 15th, 2018, the Google Media Framework (GMF) for Android is deprecated in favor of the IMA ExoPlayer plugin. All development and support for GMF has been halted. If you are a GMF Android user, we recommend you migrate to the IMA ExoPlayer plugin at your earliest convenience. Alternatively, to keep using GMF Android, you will have to fork and maintain it yourself.

Read More

As previously announced, as of March 15th, 2018, the Google Media Framework (GMF) for Android is deprecated in favor of the IMA ExoPlayer plugin. All development and support for GMF has been halted. If you are a GMF Android user, we recommend you migrate to the IMA ExoPlayer plugin at your earliest convenience. Alternatively, to keep using GMF Android, you will have to fork and maintain it yourself.

Note: We are NOT deprecating GMF for iOS.

If you have any questions, feel free to contact us via the IMA SDK developer forum.

 - Yury Pavlotsky, IMA SDK Team

Read More

The Ad Exchange Seller REST API is deprecated. Existing API clients should migrate to the DoubleClick for Publishers API before July 26, 2018. After this date, all requests to the Ad Exchange Seller REST API will return errors.

This migration guide provides instructions for getting started, as well as a mapping of each Ad Exchange reporting metric to its equivalent in the DFP API.

For more details about reporting in the DFP API, see the reporting guide.

For general assistance with the DFP API or your migration, reach out on our developer forum.

 - Chris Seeley, DFP API Team

Read More

Update May 8, 2018: Updated roll out month.
What's changing?
Beginning mid-May, 2018, once an AdWords account reaches 15 months without any spend, it will be canceled in order to speed up the AdWords experience and help users stay within the manager account limits. This also means that right now, if your account has reached 15 months without spend, it meets the criteria and will be canceled. After an account is canceled:

• get requests for ManagedCustomerService will no longer return the account.
• Any AdWords API request that specifies the account's customer ID in the clientCustomerId header will fail with an AuthorizationError.CUSTOMER_NOT_ACTIVE starting with v201802 and an OperationAccessDenied.ACTION_NOT_PERMITTED error for earlier versions of the AdWords API.
• Any unspent prepaid amount will be refunded back to the advertiser.
• All ads in your account will stop automatically within 24 hours.

Note: Test accounts will not be canceled.

What should you do?
If your application issues AdWords API requests against inactive accounts, make sure you download any relevant data for those accounts before the cancellation process starts. For example, you may want to run reports to gather historical stats for the date range where the account had activity.

If you are using an inactive account in order to test your integration with the AdWords API, consider creating a test account instead. Test accounts will not be canceled by the ongoing cancellation process.

To avoid issues once the cancellation process starts, you can proactively cancel accounts as follows:

• Log into your manager account.
• Go to the Accounts page, where you can adjust the date range and review the performance metrics for each account under the manager account to help you identify inactive accounts.
• Check the box next to each account you want to cancel.
• Select Edit -> Cancel account.

To reactivate an account, follow the instructions in the AdWords Help Center. If you are logged in as a manager account, you can show canceled accounts by adjusting the filter in the upper left corner as follows:

Note: If the account is under one or more manager accounts, you will only be able to reactivate the account if doing so will not exceed the manager account limits.

If you have any questions, please contact us via the forum.
- Josh Radcliff, AdWords API Team

Read More

Both AdWords API v201705 and v201708 will be sunset on March 28, 2018. After this date, all v201705 and v201708 API requests will begin to fail. If you haven't already migrated to v201710, we recommend that you skip v201710 and migrate directly to v201802. Please migrate prior to March 28, 2018 to ensure your API access is unaffected.

We've prepared the following resources to help you with the migration:

• v201802 migration guide
• v201710 migration guide
• v201708 migration guide (useful if you are migrating from v201705)
• Release notes

As always, if you have any questions about this migration, please contact us via the forum.
- Mike Cloonan, AdWords API Team