Tag Archives: shopping

Reminder of upcoming Content API for Shopping v2.0 sunset date

In March of this year, we announced that beginning September 30, 2021, we will end support for the legacy v2.0 of the Content API for Shopping. We also recommended you migrate to using v2.1, which has been available since March 2019.

As of this announcement, there is now less than 1 month until support for v2.0 will end on September 30, 2021. Following this date, the legacy v2.0 of the Content API is no longer guaranteed to function. We will continue to provide support for your efforts to migrate to v2.1. To avoid disruption we strongly encourage you to migrate to v2.1 imminently.

What do I need to know?
To check your usage of Content API for Shopping, you can look it up: If your application uses a multi-client account (MCA) to make changes to sub-accounts, you should also check your API usage for that account. Please note that all API usage from Content API for Shopping v2.0, is no longer guaranteed to function after September 30, 2021.

Where do I get support?
We have a comprehensive migration guide to help you migrate your implementation including all the changes and new features available in v2.1.

For support migrating the Inventory.set method, see the release of partial product updates.

For support for Google Apps Script & Google Ads scripts, see the update of the default runtime to v2.1.

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.

Google Apps Script & Google Ads scripts now support Content API v2.1 by default

Going forward, if you use Content API for Shopping through Google Apps Script or Google Ads scripts, new scripts will use Content API v2.1 by default. This change is part of the deprecation of Content API for Shopping v2, scheduled for sunset on September 30th, 2021, after which scripts that depend on v2 features won’t work.

If you currently have a Google Apps script or Google Ads script that uses Content API for Shopping v2, then we strongly recommend you migrate to v2.1. Please note that some methods and fields in v2 are no longer supported in v2.1 (for example Inventory.set), so check the availability of methods and fields you use when you migrate. See the migration guide for more detail.

If you need help implementing this change, please visit the Content API for Shopping forum.

Phone Verification in Content API for Shopping

We are pleased to announce a new Content API interface developers can use to verify phone numbers for Merchant Center accounts. Phone verification is an important step in providing contact information for an account and can also help address account status issues such as PENDING_PHONE_VERIFICATION, which in some cases can enable the option for an account re-review. Prior to this release, this was only possible in the Merchant Center user interface.

Two new methods are provided in the 2-step verification process: Once verified, the phone number will appear in the Accounts.AccountBusinessInformation. The new methods replace the prior approach of setting a phone number directly. We strongly recommend you use these new methods to verify the phone numbers for all Merchant Center accounts to avoid future issues. See the Phone Verification guide for examples and more detail.

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

New ways to find deals and shop on Google

When it comes to shopping, people are increasingly looking for ways to save money. In fact, we’ve seen that searches for “discount code” have increased 50% since last year. With the back-to-school season upon us and the holiday season fast approaching, we know that consumers will be on the hunt for products that offer the best value, and businesses will be looking for ways to maximize exposure for their products with deals and promotions.

That’s why we’re rolling out new tools in the United States to bridge the connection between deal-seeking consumers and businesses looking to promote their products.

Making it easier for shoppers to find great deals

Starting today, we’re showcasing deals right on the Shopping tab found on Google. For instance, if you’re searching for “backpacks,” you may see a new section that will organize and show you  backpacks that are competitively priced or discounted from retailers across the web, all in one place.

A search for “backpack” on the Shopping tab shows “Deals related to your search”

Starting in October, people shopping on Google Search will be able to swipe through and discover the most popular deals for major retail sales moments like Black Friday and Cyber Monday. When people search for deals during major sales moments, like “Black Friday deals” or “Cyber Monday sales,” they will see a new section highlighting relevant deals, alongside other related sales information. 

When searching for “Black Friday deals,” a Deals section will show the most relevant deals based on the search

Making it free for merchants to list deals

Last year, we made it free for merchants to sell on Google. Now, promotions and deals uploaded in the Merchant Center will be automatically surfaced to deal-seeking shoppers on the Shopping tab, regardless of whether businesses advertise on Google. Deals will also begin to appear on the main Search results page in the coming months. Offers are shown based on factors such as the discount itself, how popular a product is, how popular the site it’s listed on is and more. 

This change means that businesses will have a greater opportunity to move inventory, drive sales, attract new customers and build brand loyalty during important shopping events and peak holiday season. 

Bringing you more ways to shop

Helping merchants and consumers connect around promotions and deals is just one part of the equation. We’re also exploring ways for creators and consumers to more easily connect — especially when it comes to product reviews. 

As announced earlier this year, we’ve been beta-testing an integrated shopping experience that allows viewers to tap into the credibility and knowledge of trusted creators to make informed purchases on YouTube. This test was first available on videos on demand, and we’re now piloting this experience on livestreams with a handful of creators and brands. So if you’re watching a supported livestream on YouTube, you can browse and shop products in real time, without interruption. Stay tuned for further updates later this year.

In just a few clicks, GoDaddy merchants can show up across Google

Shoppers get the most choice when they can easily discover businesses and their unique products. And when those products get discovered, businesses can connect with more customers. We see it as a win-win, which is why we’re working hard to make commerce more open online. One way we’re doing this is by teaming up with eCommerce platforms like GoDaddy.

Starting today, we welcome GoDaddy online store customers to more easily integrate their product inventory across Google at no additional cost. This means that GoDaddy merchants can now get discovered across Search, Shopping, Image Search and YouTube in just a few clicks. With this integration, GoDaddy merchants can upload their products to Google, create free listings and ad campaigns and review performance metrics — all without leaving GoDaddy’s Online Store.

By teaming up with platforms like GoDaddy, we are able to help even more businesses make more connections with shoppers who are eager to discover new brands.

Important changes to Google Contact Policy for Merchant Center

Following feedback from our merchants, we are relaxing our contact policy website requirements for merchants. Currently we require merchants to publicly display on their website at least two methods of contact information (such as an email, business address, or phone number).

To give merchants more flexibility in the information they share with customers, beginning August 2, 2021, we will require merchants to provide on their website a minimum of one form of customer-facing contact information, for example:
  • A “contact us” form
  • A link to a social media business profile
  • An email address
  • A phone number
In addition to this change, all new merchants will be required to provide their business address and phone number on creation of their Merchant Center account, as well as for any existing accounts that require a review. This private contact information can be entered manually in the Merchant Center user interface or via Content API for Shopping.

To update the private contact information using Content API for Shopping, provide both the address and phoneNumber fields via the AccountBusinessInformation object (nested under the Account object) using the following methods: Important: Take care when updating existing accounts. Any fields that are not provided to Accounts.update will be deleted from the resource.

Note: If you have made contact information changes to an existing Merchant Center account that has an account-level disapproval, you may need to request an account re-review. See the following article on Understanding account-level enforcement for product data quality violations to find the steps to make the request.
If you require further support implementing this change, please visit the Content API for Shopping forum.

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.


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.


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.

Sunset grace period for existing v2 users of the Content API for Shopping

As we’ve previously announced, we will stop supporting legacy v2.0 of the Content API for Shopping in favor of v2.1, which has been available since March 2019.

As this has been a difficult year for all of us, in order to provide you ample time to migrate to v2.1 we will be extending the sunset date for existing merchant accounts actively using v2.0 to September 30, 2021. However, we will not allow new merchant accounts onto v2.0 after April 30, 2021. The account restrictions 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.

We will publish another blog post in the coming weeks with a process for requesting an exemption to add new accounts to your v2.0 integration after April 30, 2021.

Throughout this grace period, we will continue to provide support for your efforts to migrate to v2.1. We strongly encourage you to migrate to v2.1 as soon as possible.

What do I need to know?
In March 2019, we released version 2.1 of the Content API for Shopping with major improvements to the API management experience for Merchant Center programs, including: See the complete list of changes in the release notes and the migration guide to help with the transition.

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.

What do I need to do?
Migrate to v2.1 of the Content API as soon as possible.