Tag Archives: sunset

Display & Video 360 API v1 will sunset on September 14, 2023

As announced in March 2023, Display & Video 360 (DV360) API v1 will sunset on September 14, 2023. Please migrate to DV360 API v2 before the sunset date to avoid an interruption of service.

You can read our release notes for more information about v2. Follow the steps in our v2 migration guide to help you migrate from v1 to v2.

If you run into issues or need help with your migration, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Removing support for PHP 7 in the Google Ad Manager SOAP API Client Library for PHP

In August 2023, the Google Ad Manager SOAP API Client Library for PHP will start requiring PHP version 8.0 or higher. The version of the client library that adds support for Google Ad Manager API v202305 will be the last version that supports PHP 7. We’ll still fix security issues for this client library version until Google Ad Manager API v202305 is sunset, but no new features will be added.

All PHP 7 versions reached their end of life in 2022. The PHP development team no longer provides security fixes for these versions, so we highly recommend migrating to newer versions as soon as possible.

Here are useful resources to help with the PHP migration:

If you have any questions regarding this change, feel free to comment directly on the GitHub issue.

Pierrick Voulet, Google Ads API Team

Ad Manager API v202205 sunset and v202202 extension

On Wednesday, May 31, 2023, in accordance with the deprecation schedule, v202205 of the Ad Manager API will sunset. At that time, any requests made to this version will return errors.

Additionally, support for Ad Manager API v202202 is being extended until the same date, May 31, 2023. We've heard from a number of users that they need additional time to complete the Ad Exchange Historical report migration. Note that v202202 is the last version with support for Ad Exchange Historical reports.

When you’re ready to upgrade, check the full release notes to identify any breaking changes. Here are a few examples of changes that may impact your applications:

  • v202211
    • Replaced the string field thirdPartyImpressionTrackingUrl with the list field thirdPartyImpressionTrackingUrls for multiple creative types including ImageCreative. Currently only a single URL may be provided in the list.
    • Removed support for OPTIMIZATION reporting columns.

As always, feel free to contact us on the developer forum with any questions.

- Chris Seeley, Ad Manager API Team

New Merchant IDs are now 64-bit in Content API for Shopping

In the Content API for Shopping, we informed you last June that new Merchant IDs were migrating from 32 bit to 64-bit signed integers.

Existing Merchant IDs haven’t changed. Beginning on March 13, 2023 new Merchant IDs created could be in the 64-bit signed range. Through a slow rollout over the next few months, a higher percentage of new Merchant IDs will be in the 64-bit signed range. By June 2023, all new Merchant IDs created will be in the 64-bit signed range.

To avoid any issues, please make sure your applications are fully compliant with IDs within a range of 64-bit signed integer values.

If you have any questions or concerns, please don't hesitate to contact us via the forum.
Benji Rothman, Content API for Shopping Team

Issues from all destinations to be included in Productstatuses Service by default in the Content API for Shopping

Starting on April 24, 2023, the Content API for Shopping methods productstatuses.list and productstatuses.get will include issues from all eligible destinations by default. This will likely increase the size of the response you get back from the same call.

Currently, the responses you get when using the productstatuses.list and productstatuses.get methods only include issues from Shopping Ads and don’t include issues from other destinations, for example free listings issues.

Including issues from all eligible destinations will let you provide your users with an overall better experience. This change will improve your issue visibility across all destinations. In turn, you will see an increase in the number of results, or the size of responses you’ll receive.

No action is needed from you as the free listing issues will now be included by default when using the Content API for Shopping methods productstatuses.list and productstatuses.get.

However, if you want to keep the calls to only display issues from Shopping Ads, we suggest setting the query parameter destinations[] in the productstatuses methods to Shopping.

Learn more about the changes to the product statuses methods in the Content API for Shopping Product statuses documentation.

If you have any questions or concerns, please don't hesitate to contact us via the forum.
Benji Rothman, Content API for Shopping Team

Deprecation of Display & Video 360 API v1

Today we are deprecating Display & Video 360 API v1. While deprecated, v1 will no longer be updated. We will sunset v1 on September 14, 2023. Migrate to v2 before the sunset date to avoid an interruption of service.

You can read our release notes for more information about new features available in v2, such as the ability to retrieve YouTube & Partners line items, ad groups, and ads. Follow the steps in our v2 migration guide to help you migrate from v1 to v2.

After supporting and regularly updating Display & Video 360 API v1 for over three years, we are excited to introduce new Display & Video 360 API features using a more consistent version release and sunset schedule. A projected schedule will be announced on this blog at a later date.

If you run into issues or need help with your migration, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Announcing the deprecation of Ad Exchange Buyer II API

The Ad Exchange Buyer II API is now deprecated, and the following resources will be sunset on September 29th, 2023:

Accessing the sunset resources will return an error response following the sunset date. Note that RTB Troubleshooting resources aren’t included in this list, and will continue to be supported until further notice.

To continue programmatically accessing your Client Access and Marketplace configurations, you should migrate to the Authorized Buyers Marketplace API. For more information, we recommend that you review the Marketplace guide and samples. If you have any questions or feedback, feel free to reach out to us via the Authorized Buyers API Forum.

- Mark Saniscalchi, Authorized Buyers Developer Relations

Removing support for PHP 7 in the Google Ads API client library for PHP

In July 2023, the Google Ads API client library for PHP will start requiring PHP version 8.0 or higher. The version of the client library that adds support for the Google Ads API v14 will be the last version that supports PHP 7. We’ll still fix security issues for this client library version until the Google Ads API v14 is sunset, but no new features will be added.

All PHP 7 versions reached their end of life in 2022. The PHP development team no longer provides security fixes for these versions, so we highly recommend migrating to newer versions as soon as possible.

Here are useful resources to help with the PHP migration: If you have any questions regarding this change, feel free to comment directly on the GitHub issue.
 - Thanet Knack Praneenararat, Google Ads API Team

Google Ads API v11 sunset reminder

Google Ads API v11 will sunset on March 29, 2023. After this date, all v11 API requests will begin to fail. Please migrate to a newer version prior to March 29, 2023 to ensure your API access is unaffected.

We've prepared various resources to help you with the migration: In addition, using the Google Cloud Console, you can view the list of methods and services to which your project recently submitted requests:
  1. Open the Dashboard page (found under APIs & Services) in the Google Cloud Console.
  2. Click on Google Ads API in the table.
  3. On the METRICS subtab, you should see your recent requests plotted on each graph. At the bottom of the page, you’ll see the Methods table, where you can see which methods you’ve sent requests to. The method name includes a Google Ads API version, a service, and a method name, e.g., google.ads.googleads.v11.services.GoogleAdsService.Mutate. In this way, you can see all versions that you’ve used recently.
  4. (Optional) Click on the time frame at the top right of the page if you need to change it.
If you have questions while you’re upgrading, please reach out to us on the forum or at [email protected].
 - Thanet Knack Praneenararat, Google Ads API Team

Bid Manager API v1.1 will sunset on April 27, 2023

The Bid Manager API v1.1 will sunset on April 27, 2023. The Bid Manager API v1.1 was deprecated in August 2022 and originally scheduled to sunset on February 28, 2023.

Please migrate to v2 before the sunset date to avoid an interruption of service.

You can read our release notes for more information about v2. Follow the steps in our v2 migration guide to help you migrate from v1.1 to v2.

If you run into issues or need help with your migration, please contact us using our support contact form.

- Trevor Mulchay, Display & Video 360 API Team