Tag Archives: content_api

Merchant IDs as 64-bit in Content API for Shopping

In the Content API for Shopping, Merchant IDs are now 64-bit signed integers. Applications that integrate with the Content API must be able to handle ID values in that range.

Historically, Merchant IDs in the Content API for Shopping were within the maximum value of a 32-bit signed integer, but have recently exceeded this range. In order 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.

Upcoming enforcement of custom batch limits in Content API for Shopping

Beginning May 31, 2022 we will enforce the following limits for custom batch methods in the Content API for Shopping:
  • Maximum entries per request: 10,000
  • Maximum transfer size per request: 32Mb (The payload received from the client)
We’re introducing these limits to enable the fair and stable use of Content API for Shopping. The limits will apply to the following endpoints: After May 31, 2022, calls to any of these endpoints that exceed these limits will begin to fail with the following error:
  • request_too_large
Visit our batching guide to learn more about methods for reducing your batch size. If you are looking for a reasonable batch size to implement, we recommend 1,000 entries per request for each endpoint. Following this means you are unlikely to encounter the limits even if your batch size temporarily increases.

If you have any questions about implementing this change, please visit the Content API for Shopping forum.

Introducing the new Merchant Center Status Dashboard

At Google, we strive to provide the highest level of service possible to our users. Still, from time to time, unexpected service disruptions do occur. When your team experiences an outage or other technical challenge, one of the first evaluations they need to make is whether the issue is with a third-party service provider or in-house. As part of our commitment to transparency and speed when communicating the status of our products, and incidents when they happen to occur, we’re pleased to roll out the Merchant Center Status Dashboard.

Check the status of a service
A look at the Merchant Center Status Dashboard

If a major incident is identified, we will generally post an outage notice on the Dashboard and provide updates when the issue is resolved. If the dot is green, it means there are no issues. The Merchant Center Status Dashboard provides status information on the Content API for Shopping, Merchant Center, and Feeds.

You can check the dashboard to view the current status of any of those services. All incidents are first verified by our support engineers, so there may be a slight delay from the time they actually occurred. More information can be found on the Merchant Center Help Center.

Subscribe to the Status Dashboard RSS or JSON feeds
To get the fastest outage alerts, we recommend subscribing to the Status Dashboard RSS feed:
  1. Go to the Status Dashboard.
  2. At the bottom, click RSS Feed and copy the feed URL.
  3. In your RSS reader, paste the URL to add the Status Dashboard feed.
  4. If you want programmatic access to the Status Dashboard, for example to integrate it into your monitoring system, at the bottom, click JSON History.
Learn more
More information about the Status dashboard can be found on the Merchant Center Help Center.

To investigate the most common errors regarding the Content API for Shopping, check this page on our Developers site. For other errors or for general Content API support, visit the forum.

Ads API apps must complete OAuth verification

Last year, the OAuth scopes used by the following Ads APIs were classified as sensitive, requiring developers to complete the OAuth verification process for their Google Cloud projects:
  • Google Ads API & AdWords API
    • https://www.googleapis.com/auth/adwords
  • Content API for Shopping
    • https://www.googleapis.com/auth/content
  • DoubleClick Bid Manager API
    • https://www.googleapis.com/auth/doubleclickbidmanager
Any remaining OAuth clients using the above scopes that remain unverified may have their existing credentials revoked and lose access to the above APIs if they do not complete the OAuth verification process as soon as possible.

Certain apps may qualify for one of the exceptions for app verification. If your application meets any one of those exceptions, follow the steps listed for the appropriate use case. If not, you must complete OAuth verification to continue using these Ads APIs.

If you have any questions or need additional help, contact us using any of the following support options:

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.

Performance reporting now available in the Content API for Shopping

We're excited to announce that performance reporting is now available in v2.1 of the Content API for Shopping. With the search method of the Reports service, you can programmatically retrieve all of the performance data that's available in the Merchant Center.

Requests to the Reports service use the new Merchant Center Query Language, which gives you control over which metrics to download, how to segment/group your data, and which criteria to apply for selecting the result set. If you also use the reporting features of the Google Ads API, you’ll find that many of these concepts are familiar.

For example, the following query will result in a report of impressions, clicks, and clickthrough rate (CTR) over the last 30 days, summarized by date, brand, and offer ID.

SELECT
segments.date,
segments.brand,
segments.offer_id,
metrics.impressions,
metrics.clicks,
metrics.ctr
FROM MerchantPerformanceView
WHERE segments.date DURING LAST_30_DAYS
AND segments.category_l2 IN ('Clothing', 'Shoes')

For more details, check out the Reporting guides, which include an overview, a quick example to get you started, and an explanation of key concepts, including how to compose queries in the Merchant Center Query Language.

If you have any questions or need help with the new reporting service, please contact us through the Content API for Shopping forum.

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.