Tag Archives: sunset

Partial product updates now available in v2.1 of the Content API for Shopping

Today we are launching a new feature in Content API for Shopping v2.1: products.update.
The products.update method allows you to submit a subset of changes for a given product using the Products API. It works similarly to products.insert, but only requires the fields you would like to modify.

Users of inventory.set in Content API v2, will be familiar with the ability to provide updates to price, availability and other limited fields. The products.update method goes one step further and allows you to modify any fields that are mutable with products.insert. Users that are migrating from v2 to v2.1 ahead of the September 30, 2021 sunset date, might find this new functionality useful.

Products.update utilizes the HTTP PATCH method. Here is an example of updating the salePrice using REST:

HTTP request:

PATCH https://shoppingcontent.googleapis.com/content/v2.1/{merchantId}/products/{productId}


Example request body:

{
  "salePrice": {
    "value": "17.99",
    "currency": "USD"
  }
}

You can also provide product update operations as part of a products.custombatch request. For more examples and use-cases, see the products.update guide in the documentation.

If you require further support using this feature, please visit the Content API for Shopping forum.


Ian Ballantyne, Content API for Shopping Team

Partial product updates now available in v2.1 of the Content API for Shopping

Today we are launching a new feature in Content API for Shopping v2.1: products.update.
The products.update method allows you to submit a subset of changes for a given product using the Products API. It works similarly to products.insert, but only requires the fields you would like to modify.

Users of inventory.set in Content API v2, will be familiar with the ability to provide updates to price, availability and other limited fields. The products.update method goes one step further and allows you to modify any fields that are mutable with products.insert. Users that are migrating from v2 to v2.1 ahead of the September 30, 2021 sunset date, might find this new functionality useful.

Products.update utilizes the HTTP PATCH method. Here is an example of updating the salePrice using REST:

HTTP request:

PATCH https://shoppingcontent.googleapis.com/content/v2.1/{merchantId}/products/{productId}


Example request body:

{
  "salePrice": {
    "value": "17.99",
    "currency": "USD"
  }
}

You can also provide product update operations as part of a products.custombatch request. For more examples and use-cases, see the products.update guide in the documentation.

If you require further support using this feature, please visit the Content API for Shopping forum.


Ian Ballantyne, Content API for Shopping Team

Reminder: Ad Exchange Buyer API Sunset

As announced previously, the Ad Exchange Buyer API is set to sunset by the end of Q2, 2021. We will begin the process of phasing the API out on June 1st, where a small percentage of API requests will begin to return an API error response that includes details about the impending sunset. You can expect API errors to progressively increase leading up to the sunset date. Note that this sunset does not include the Ad Exchange Buyer II API, which is not deprecated at this time.

The Real-time Bidding API is the replacement for the Ad Exchange Buyer API, and we encourage you to migrate before the sunset date in order to avoid interruptions to your integration. To learn more about the Real-time Bidding API, you can read the migration guide, reference documentation, and the new resource guides. Additionally, samples for several programming languages are available to assist you with your migrations.

If you encounter any issues, or have any questions we can assist with, please contact us via our support forums.

- Mark Saniscalchi, Authorized Buyers Developer Relations

Feed-based Extensions Sunset in Google Ads APIs

Google Ads has recently introduced Asset-based extensions. This new paradigm reduces the complexity of managing extensions when compared to the existing Feed-based extensions. Asset-based extensions will only be supported in Google Ads API.

Asset-based extensions will replace the current Feed-based extensions. All existing Feed-based extensions will automatically migrate in two batches. Other services that use Feeds, such as Location extensions, Dynamic Ads, and Page Feeds, will be discussed in future announcements.

Extension
Type 		Asset
Available to
Test
Accounts 		Asset
Available to
Production
Accounts 		Auto
Migration
Date 		Feeds
Sunset
Date
Lead Form Google Ads API v6 Google Ads API v6 October 20, 2021 February 15, 2022
Promotion Google Ads API v7 Google Ads API v7 October 20, 2021 February 15, 2022
Callout
Sitelink
Structured Snippet		 Google Ads API v7 Google Ads API v8
(tentative)		 October 20, 2021 February 15, 2022
App
Call
Hotel Callout
Image
Price		 Google Ads API v9
(tentative)		 Google Ads API v9
(tentative)		 February 15, 2022 April 8, 2022


What do I need to do?
You should migrate any Feed-based extensions and related code that you intend to continue to use to Asset-based extensions as soon as is feasible. You should remove Feed-based extensions after migrating; for a given extension type, any Asset-based extensions will serve instead of Feed-based extensions. See our extensions migration guide for details. Consider developing and testing your Asset-based extension implementation using a test account so as to access all the currently available Asset types.

After the automatic migration dates, you will no longer be able to create or mutate Feed-based extensions in the AdWords API or the Google Ads API. Feed-based extensions will no longer generate new data. You will still be able to issue Feed-related report queries until August 2022; thereafter all Feed-based extension data will be removed and report queries will return errors.

What if the October date is too soon?
You can request to opt individual accounts out of the October auto migration; the process for doing so will be announced in a subsequent blog post. Note that the Feed-based extensions in the first batch will still become unavailable for all accounts in February 2022.

If you have any questions, concerns, or feedback, please contact us via our forum.
Andrew Burke, Google Ads API Team

Sunset of the Ad Manager API v202005

On Tuesday, June 1, 2021, in accordance with the deprecation schedule, v202005 of the Ad Manager API will sunset. At that time, any requests made to this version will return errors.

If you’re still using v202005, now is the time to upgrade to a newer release and take advantage of additional functionality. For example, in v202102 we added support for AudioCreative types.

When you’re ready to upgrade, check the full release notes to identify any breaking changes. For instance, starting in v202008, we replaced the singular LineItem.viewabilityProviderCompanyId field with viewabilityProviderCompanyIds for specifying a list of IDs.

As always, don't hesitate to reach out to us on the developer forum with any questions.
 - Donovan McMurray, Ad Manager API Team

Reminder to migrate to the AdMob API

Starting on October 12, 2021, developers will no longer be able to retrieve AdMob data from the AdSense Management API v1.4. Please start to migrate to the AdMob API which is generally available.

Where can I get my AdMob data?

After October 12th, 2021, using the AdMob API will be the only way you can access your AdMob data programmatically. The AdMob API helps app developers retrieve:

  • metrics that are consistent with the AdMob UI definitions and calculations
  • mediation reports that are not available through the AdSense API

What do I need to do?

Start migrating from the AdSense API to the AdMob API as soon as possible. If you do not complete the migration by October 12th, 2021, you will lose access to AdMob data through the AdSense API, which may impact your ability to make data-driven business decisions.

Follow the instructions in the migration guide to migrate your API workflow. Review these additional resources to support your migration:

Feel free to reach out to us via the AdMob API forum if you have questions or feedback regarding the AdMob API.

 - Amira Badreldin, AdMob API team

Reminder to migrate to the AdMob API

Starting on October 12, 2021, developers will no longer be able to retrieve AdMob data from the AdSense Management API v1.4. Please start to migrate to the AdMob API which is generally available.

Where can I get my AdMob data?

After October 12th, 2021, using the AdMob API will be the only way you can access your AdMob data programmatically. The AdMob API helps app developers retrieve:

  • metrics that are consistent with the AdMob UI definitions and calculations
  • mediation reports that are not available through the AdSense API

What do I need to do?

Start migrating from the AdSense API to the AdMob API as soon as possible. If you do not complete the migration by October 12th, 2021, you will lose access to AdMob data through the AdSense API, which may impact your ability to make data-driven business decisions.

Follow the instructions in the migration guide to migrate your API workflow. Review these additional resources to support your migration:

Feel free to reach out to us via the AdMob API forum if you have questions or feedback regarding the AdMob API.

 - Amira Badreldin, AdMob API team

Google Ads API v4 and v5 sunset reminder

The Google Ads API v4 and v5 will sunset on June 23, 2021. After this date, all v4 and v5 API requests will begin to fail. Please migrate to a newer version prior to June 23, 2021 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 or at [email protected].
 - , Google Ads API Team

Upgrade to the Google Ads API from the AdWords API by April 27, 2022

If you are a developer currently using the AdWords API, you need to upgrade to the Google Ads API by April 27, 2022. On that date, the AdWords API will sunset and requests to the AdWords API will fail. With Google Ads API v7, we reached feature parity with the AdWords API making it possible for all developers to upgrade with a few exceptions listed at the top of the Migrating Features guide.

With the Google Ads API, you’ll see faster rollouts of new features and updates for tools like recommendations, asset management, and new ad types. We’ve also made improvements to existing features like Keyword Planner, change history, and billing. This provides more features to manage your campaigns and increases overall productivity.

Where do I start?
Any developers applying for a new developer token after today will only be given access to the Google Ads API. The following are useful resources for new API users: Existing AdWords API developers should start upgrading. Here are some resources to get started: Where can I get support?
If you have questions while you’re upgrading, please reach out to us on the forum or at [email protected].
Nadine Wang, on behalf of the Google Ads API Team

Reminder: Using v2.0 of the Content API for Shopping with new accounts ends on April 30, 2021

In March, we announced that beginning April 30, 2021 we will no longer allow new merchant accounts onto v2.0 of the Content API for Shopping as part of the sunset process. With less than two weeks to go until the April deadline, here is a quick reminder of the details.

What do I need to know?
  • This account restriction will not impact users accessing new sub-accounts via an existing multi-client account (MCA), provided that MCA has been actively making v2.0 requests.
  • New accounts using v2.1 of the Content API for Shopping will not be affected.
  • The sunset date for existing merchant accounts actively using v2.0 is September 30, 2021.
What do I need to do?
  • Migrate to v2.1 of the Content API for Shopping in order to continue interacting with new merchant accounts after April 30, 2021.
  • If you are concerned you won’t be able to meet the April deadline, please fill out this form to request an exemption.
If you have any questions or issues during migration, contact your Google representative for Merchant Center programs, or ask questions in the Content API for Shopping forum.
Ian Ballantyne, Content API for Shopping Team