Tag Archives: shopping

Changes to Content API request validation

What’s changing?

The Content API for Shopping will gradually roll out improvements to request validation from January 1, 2021 to February 15, 2021. These changes will be applied to a growing percentage of requests during that time, reaching 100% by February 15, 2021. The validation improvements will ensure that certain requests that are not in the proper format result in an error instead of having the Content API attempt to infer the request's intent. As long as you are submitting the proper type and structure for each field, you will not be affected by this change.

The following sections describe two examples of incorrectly formatted requests that may fail after January 1st, 2021. If your requests start to fail after January 1st, 2021, please refer to the error message returned and correct the formatting issue.

Example: Providing an invalid structure for a repeated field

This error applies to providing any invalid type for a repeated field, such as providing a list of objects instead of a list of strings, or vice versa.

Example invalid v2.1 request

The following request is invalid because the includedDestinations field requires a list of strings, not a list of objects:

{
"targetCountry": "US",
"offerId": "123",
"contentLanguage": "en",
"channel": "online",
"includedDestinations": [{"destinationName": "Shopping", "intention": "default"}]
}

Example valid v2.1 request

To correct this issue, change the list of objects to a list of strings:

{
"targetCountry": "US",
"offerId": "123",
"contentLanguage": "en",
"channel": "online",
"includedDestinations": ["Shopping", "SurfacesAcrossGoogle"]
}

Other common fields affected by this change

  • v2.1:
    • product.excluded_destinations (a common mistake is providing the v2 format of this field for requests to v2.1)
  • v2:
    • product.destinations (a common mistake is providing the v2.1 format of this field for requests to v2)
    • product.sizes
    • product.additional_image_links
    • product.shipping

Example: Submitting a string that represents a float instead of an integer

This error applies to providing a string containing a floating point number when an integer is required.

Example invalid v2.1 request

The following request is invalid because the sellOnGoogleQuantity requires a string in int64 format, but the string “100.0” is a float:

{
"targetCountry": "US",
"offerId": "123",
"contentLanguage": "en",
"channel": "online",
"sellOnGoogleQuantity": "100.0"
}

Example valid v2.1 request

To correct this issue, change the value to an integer:

{
"targetCountry": "US",
"offerId": "123",
"contentLanguage": "en",
"channel": "online",
"sellOnGoogleQuantity": "100"
}

Other common fields affected by this change

  • v2.1:
    • product.unit_pricing_base_measure.value
  • v2:
    • inventory.sell_on_google_quantity
    • product.unit_pricing_base_measure.value

What do I do?

We recommend that you address any incorrectly formatted requests before January 1st, 2021 to avoid any disruptions to your application.

If you are already submitting the proper type for each field as described in the Content API for Shopping reference docs, no action is required.

Need More Help?

If you have any questions or need assistance, please reach out to us on the forum.

Sunset approaching for v2 of the Content API for Shopping

We are writing to remind you that the Content API for Shopping v2 will sunset on March 29, 2021. On this date, all requests made against v2 of the Content API will fail. Please migrate to v2.1 as soon as possible to ensure your applications are unaffected.

To help with the migration to v2.1, we have prepared the following resources:

  • Migration guide -- Explains how to update your applications for v2.1.
  • Supplemental feeds guide — In v2.1, supplemental feeds replace the v2 inventory service for partial updates to online products.
  • Local inventory service guide — In v2.1, the local inventory service replaces the v2 inventory service for updates to local inventory.
  • Release notes -- Lists all changes and new features added in v2.1, organized by release date.

If you have questions about the migration or encounter challenges that prevent you from migrating, we want to hear from you. Please reach out to us on the forum so we can help.

Content API upgrading authorization scope to "sensitive"

Beginning October 1, 2020, any new Google Cloud app with a unique OAuth 2.0 Client ID used to obtain credentials for the Google Content API scope (https://www.googleapis.com/auth/content) in its projects will need to undergo a Google OAuth verification to avoid an unverified app screen for its users. Users of unverified apps that access the Content API will see warnings and the apps will have limited functionality.

There is no cost for app verification and the process typically takes 3 to 5 business days. For more information about how app verification fits into the broader process of authorizing requests, see our Using OAuth guide.

Apps already using the Content API scope prior to October 1, 2020 are not currently affected by this policy. However, this policy will be applied to all apps at a later date in 2021, and we recommend that all apps undergo the Google OAuth verification process at their earliest convenience to avoid any business interruptions.

For more information about app verification, see OAuth API verification FAQs. If you have any questions or need additional help, please reach out to us on the forum.

Sunset of v2 for the Content API for Shopping

The Content API for Shopping v2 will sunset on March 29, 2021. On this date, all requests made against v2 of the Content API for Shopping will fail. Please migrate to v2.1 as soon as possible to ensure your applications are unaffected.

To help with the migration to v2.1, we have prepared the following resources:
  • Migration guide -- Explains how to update your applications for v2.1
  • Supplemental feeds guide — In v2.1, supplemental feeds replace the v2 inventory service for partial updates to online products.
  • Local inventory service guide — In v2.1, the local inventory service replaces the v2 inventory service for updates to local inventory.
  • Release notes -- Lists all changes and new features added in v2.1, organized by release date.
If you have questions about migration, please reach out to us on the forum.

Gmail on standard Shopping campaigns

Beginning the week of Mar 4th, 2020, Shopping ads (both Product Shopping ads and Showcase Shopping ads) in your standard Shopping campaigns that target the Google Display Network will be eligible to appear on Gmail in addition to YouTube and Google Discover. This means that reporting information will include Gmail in addition to YouTube and Google Discover for the following configurations: To allow your advertisers to opt-in/opt-out of Gmail, YouTube and Google Discover for standard Shopping campaigns, you will need to enable or disable the following setting:
  • Google Ads API - Modify the NetworkSettings of the standard Shopping campaign and set target_content_network to true (opt-in) or false (opt-out).
  • AdWords API - Modify the NetworkSetting of the standard Shopping campaign and set targetContentNetwork to true or false.
If you have any questions or need help, please contact us via the forum.

Shopping on Google brings new features to connect more users to retailers

https://lh3.googleusercontent.com/ESxE2TPcnaVUmmvFIIEI2cOkZCZX3GMP5EFAkI-L1UBi3FyyXvyj499d1rdmAOBB2d8R2bCMP7FVQcXqZlcudkSAL_a1fReM32Emy7go42CHw49EYjoAWZjmnubNXeVNUrJHiWmW
Last year we announced a new shopping experience on Search -- a frictionless way for Indian shoppers to discover new products on Google. We also enabled online merchants to list their products for free in the Merchant Center, along with auto feeds that made the process quick and easy.  

We’ve witnessed incredible momentum since then. Indian shoppers engage with this shopping experience more often, and for longer periods of time compared to other markets, and there are now over 200 million offers available on Google Shopping. Not only that, share of clicks on listings that direct to small and medium business websites have increased by 30 percent! We’re committed to helping small and medium sized businesses succeed in India and are excited to announce new tools to help them connect with shoppers, online and off.



Getting local stores online with Google My Business

Although online shopping in India continues to grow in popularity, about 96 percent of shopping still happens offline. Soon, any local retailer will be able to create an online store through Google My Business and connect with the millions of shoppers searching for their products online. When they post photos of their in-store products, they will automatically be surfaced as product listings on Search and in the Google Shopping tab. We’re excited to welcome the 20,000 local businesses that are already on Google My Business in India into the Shopping experience when it launches early next year. 

Shopping in Indian languages

The rate at which Indian language users are coming online cannot be overstated -- 9 out of every 10 new users coming online are Indian language users (largely using their mobile phones, from tier 2 and 3 cities.) And these users are searching online more than ever: at Google For India earlier this year, we announced that 20 percent of Search queries in India are in Hindi.

So we are glad to share that we are extending the power of Google Translate to the Shopping tab as well as the Shopping home page for Indian languages.



Hindi
Telugu
Gujarati

Over the next two to three years, approximately 500 million non-English speaking users will be online in India, and we hope that this step will enable them to more easily find products in their own language. And on the merchant side, it requires no extra effort -- the products that will be showcased to online shoppers in India will seamlessly be displayed in their preferred Indian language. This feature will also be available to shoppers in India early next year.

As we shared when we launched Shopping on Search in India last year, our endeavor is to enable India’s small and medium retailers to grow and thrive, and to open a world of new online experiences for Indian shoppers. With the integration of Google My Business and Google Translate, we are excited to bring the full power of Google to Shopping. 
Posted by Surojit Chatterjee, Vice President - Product Management, Google Shopping

Expanding your Shopping ads to additional Google platforms

YouTube and Google Discover power visually rich experiences and play a part of millions of users’ shopping journeys. Soon your Standard Shopping campaigns will be able to reach users who discover and continue their shopping journey on these additional Google platforms.

We’re excited to announce that Shopping ads (both Product Shopping ads and Showcase Shopping ads) in your standard Shopping campaigns will be eligible to appear on YouTube and Google Discover beginning the week of July 15th, 2019. Shopping ads served on YouTube and Google Discover will be reported under the Google Display Network.

In preparation for this change, standard Shopping campaigns that are enabled for Search Network will be automatically enabled for YouTube and Discover, beginning the week of June 17th, 2019. This means that any standard Shopping campaigns that target the Search Network will automatically enabled to target the Content Network. After this process, developers using the Google Ads API or the AdWords API can give users the ability to opt-in/opt-out. They can do this by changing the campaign target network as follows:
  • Google Ads API - Modify the NetworkSettings of the standard Shopping campaign to set target_content_network to true or false.
  • AdWords API - Modify the NetworkSetting of the standard Shopping campaign to set targetContentNetwork to true or false.
Ads with these settings will only be eligible to appear on YouTube and Google Discover from the week of July 15th, 2019. During that week, you may start seeing new metrics as part of your reporting data. Depending on which API you are using you can access the metrics by doing the following: Note: If you would like to upgrade to the Google Ads API from the AdWords API, please see more information our blog.

If you have any questions or need help, please contact us via the forum.

Announcing v2.1 of the Content API for Shopping

Today we're announcing the release of v2.1 of the Content API for Shopping. This version has been available as an experimental version since late last year and is now ready for production use by all Content API users.

Highlights
You can find a complete list of changes in the release notes and accompanying migration guide, but here are some highlights:
  • A more consistent product validation experience. Product insert requests no longer report non-fatal warnings or errors. This allows you to insert products and make subsequent updates to resolve issues via feed rules in the Merchant Center UI, just as you would with feeds maintained outside the API.
  • A better experience for managing Shopping Actions. Multiple improvements have been made to the Orders API based on feedback from beta users.
  • More features are on the way! Today's release contains many improvements, but more are on the way, including new ways to supply local inventory data and features to support supplemental feeds.
  • Continued v2 support. While we strongly encourage you to migrate to v2.1, support for v2 will continue at least through the first quarter of 2020. Subscribe to this blog to ensure you receive important updates on Content API releases and deprecations.
Updated client libraries
Updated client libraries with support for v2.1 are now available in multiple languages.

Learn more
Check out the v2.1 API reference documentation to explore the new version of the API, and read through the list of behavior changes and deprecations in the migration guide to help plan your upgrade to v2.1.

If you have any questions or need help with migration, please head over to our support forum.

Sunset of XML support in the Content API for Shopping

What's changing?
Starting September 1, 2019, the Content API for Shopping will no longer support requests or responses with XML payloads. All requests with an XML payload will fail after the sunset date.

Why is this change happening?
Version 2 of the Content API for Shopping changed the default request and response format from XML to JSON, and version 2.1 of the API (currently marked experimental) will not support XML. The majority of API requests now use JSON, so we've decided to sunset XML support and instead focus on enriching our JSON APIs with new features and functionality.

What should you do?
Prior to the sunset date, identify the components of your application that are using XML payloads for any of the following impacted services: For each case, modify your application to:
  • Send the request body as JSON.
  • Ensure you have removed the alt=xml parameter from the request.
  • Process the response as JSON.
  • Test your updated application using a separate test account.
Tip: The client libraries for .NET, Dart, Go, Java, JavaScript, Node.js, Objective-C, PHP, Python, and Ruby will send JSON requests and parse JSON responses for you. We strongly recommend that you use one of the libraries so you won't have to write marshalling and unmarshalling code in your application.

When converting a given request, you can use the JSON and XML tabs in the Request body section of the documentation for the method. For example, here's a partial screenshot of the XML tab for Inventory.set:

The corresponding JSON tab for that method is:

Compare the two tabs and use that as a guide when converting your request from XML to JSON.

You can find similar JSON and XML information for the response in one of the following locations:
  • Directly in the Response section for the method.
    Example: The productsCustomBatchResponse for Products.custombatch.
  • In the Resource representations section of the documentation for the resource returned in the response.
    Example: The products resource for Products.insert.
If you have any questions or feedback about this change, or any other questions about the Content API for Shopping, please let us know on the forum.

Update on issue reporting changes in the Content API for Shopping

In August, 2018, we announced that we would stop populating the dataQualityIssues field in Productstatus and Accountstatus resources in December of last year. Due to the recent holiday season, we decided to hold off on that change, but it will now be made starting February 25, 2019.

Please review the previous blog post for important details, including how to use the new and improved itemLevelIssues field in your platform's integration with the Content API for Shopping.

If you have any questions or feedback about this change, or any other questions about the Content API for Shopping, please let us know on the forum.