The AMP One Tap component wouldn't be supported after Chrome third-party cookie deprecation starting with 1 percent of third-party cookies in Q1 2024, and expanding to 100 percent of Chrome users in H2 2024. This means that new web apps shouldn't use this component, and developers of the existing apps should follow the migration guide to make necessary changes in order to avoid negative impacts for user sign-in to their websites.

Display One Tap in AMP pages

To add One Tap to your Accelerated Mobile Pages,

Add One Tap into an intermediate Iframe hosted by your own website.
Embed the intermediate iframe, instead of One Tap, into your AMP pages using the <amp-onetap-google> component.

Place the following code snippet into any AMP pages that you want Google One Tap to display:

<script custom-element="amp-onetap-google" src="https://cdn.ampproject.org/v0/amp-onetap-google-0.1.js" async></script>
<amp-onetap-google
  layout="nodisplay"
  data-src="https://example.com/onetap_iframe.html">
</amp-onetap-google>

Set the data-src attribute to the URI of your intermediate iframe.