How to get help

Issues with AMP and AMP for Email

If you have questions or need support with AMP itself, refer to the AMP support page, which lists resources and channels for assistance.

AMP for Email Working Group

An AMP Working Group is a segment of the community with knowledge and interest in specific areas of AMP recognized by the AMP Technical Steering Committee (TSC).

The Working Group responsible for the AMP for Email specification is wg-amp4email. You can reach out to the Working Group using the following channels:

Reach out to the Working Group if you have questions or issues related to the AMP for Email specification.

Issues with AMP specific to Gmail

Review the following options to find the best way to get developer support for Google Workspace APIs and tools.

Questions & advice

We use the popular programming Q&A website Stack Overflow to field technical questions. Google doesn't own or manage this site, but you can sign in with your Google Account.

Developers use the tag [amp-email] to mark questions relevant to this service. You can search existing questions or ask a new question:

Ask a new question

Refer to the Google Workspace developer community page for additional resources, discussion forums, and chat channels.

Developer product feedback

If you have feedback about developer product features or functionality, search our Issue Tracker to see if others have already submitted the same feedback. If you find an existing feedback report, click the star next to the issue number to express your agreement and help us prioritize it.

If no one else has submitted similar feedback, you can submit a new feedback report.

Submit bug Submit feature request

Contact Google Workspace support

If you are a Google Workspace customer, your administrator can email a Google Workspace developer support specialist for direct assistance.

Make sure you include the following information when you contact us:

  • A description of the problem, and the behavior you expected instead.
  • A list of steps and a small snippet of sample code that can be used to reproduce the problem.
  • A description of the output you expect and what actually occurred. Include any error messages you receive.
  • Information about your development environment, including programming language, library versions, etc.