Support

Page Summary

As of June 10, 2024, all Content API for Shopping support inquiries should be directed to the new Contact Us form, replacing the previous email and forum channels.
The Content API team provides email support with a 24-hour initial response time, focusing on technical issues related to the Content API for Shopping.
For general Merchant Center questions, users are guided to the Merchant Center Help Center, while Google Ads API inquiries are directed to their respective developer site and forum.
Additional resources include troubleshooting guides for common errors, API diagnostics, a status dashboard, and best practices for storebuilders.
Businesses seeking information about their data or access methods can utilize a dedicated data request form.

This support page provides several support contacts.

Contact the Content API for Shopping support team for technical support.

Content API team offers email-based support from Monday to Friday. You can expect a 24 hour turnaround time for the initial reply.

Answers to non-API questions about Merchant Center can be found in the Merchant Center Help Center.

To investigate the most common errors, see common errors.
If you're having issues with the Content API, check the Merchant Center status dashboard for outages.
You can check the API activity for your Merchant Center account on the API diagnostics page. Learn how to debug API errors using API Diagnostics.
Visit the Storebuilder Blueprint to learn about integration best practices for storebuilders.

For general information and to learn more about the Google Ads API, visit the Google Ads API developer site or the Google Ads API forum.

For any questions about the data available to you or how to access the data, fill this form.

If you need additional time to migrate from Content API for Shopping to Google Content API for Shopping, complete the application for extended access to Content API for Shopping.

Before requesting an extension, keep the following in mind:

Google Cloud project ID validity: This extension is valid only if you submit correct Google Cloud project IDs (for example, my-cloud-project-123456789). Don't submit project names or project numbers. Invalid IDs cannot be processed, which leads to service degradation and loss of API access after the sunset date. To find your project IDs, see Locate your Google Cloud project IDs.
Multiple project IDs: You can include multiple Google Cloud project IDs in a single request as a comma-separated list.
Approval with no email confirmation: Extension requests submitted through the form are approved upon submission, provided that the submitted Google Cloud project IDs are correct. Google does not send a separate email confirmation after processing your request.
Multiple submissions: You can submit the form multiple times. The most recent submission determines the expiration date for your Google Cloud projects.
Submissions after expiration: If your expiration date has passed and you are already receiving API errors, you can still submit the form to request an extension and restore access.