[null,null,["最后更新时间 (UTC):2024-02-28。"],[[["\u003cp\u003eThis guide explains the One Tap user experience, including when it's displayed and user session behaviors.\u003c/p\u003e\n"],["\u003cp\u003eUsers can globally opt out of One Tap by disabling Google Account sign-in prompts in their account settings.\u003c/p\u003e\n"],["\u003cp\u003eOne Tap has cooldown periods where it won't display after being manually closed by the user, with varying durations.\u003c/p\u003e\n"],["\u003cp\u003eOn mobile browsers, One Tap automatically closes after 90 seconds of inactivity without triggering a cooldown.\u003c/p\u003e\n"],["\u003cp\u003eA different One Tap user experience is provided for ITP browsers like Chrome on iOS, Safari, and Firefox.\u003c/p\u003e\n"]]],[],null,["This guide contains detailed descriptions of the One Tap user experience,\nincluding when One Tap is or is not displayed and user session behaviors.\n\nGlobally opt out\n\nUsers can opt out of One Tap if they disable the Google Account sign-in prompts\nflag in the [Apps with access to your account](https://myaccount.google.com/permissions) page. The opted-out sessions\naren't shown in One Tap. If all Google sessions are opted out, One Tap doesn't\ndisplay.\n\nIf a user disables third-party sign-in on browsers with [FedCM enabled](/identity/gsi/web/guides/overview#federated_credential_manager_fedcm), One\nTap is not displayed. In Chrome settings under the Privacy and Security section\nusers control the display of [third-party sign-in](https://support.google.com/chrome/answer/14264742) prompts either globally\nor for individual sites.\n\nExponential cooldown\n\nIf the user closes the One Tap prompt manually, the One Tap prompt is\nsuppressed. A user closes One Tap when they tap **Close**\nclose in the\ntop-right corner of the prompt, after which One Tap wouldn't display in the\nsame browser or the last website visited for a period of time.\n\nThe following exponential time periods are used for cooldowns when FedCM is\n**not** enabled:\n\n| Consecutive times closed | Time period that One Tap is disabled |\n|--------------------------|--------------------------------------|\n| 1 | Two hours |\n| 2 | One day |\n| 3 | One week |\n| 4+ | Four weeks |\n\nThe cooldown status resets after a successful sign-in using One Tap or the Sign\nin with Google button.\n\nWhen FedCM is enabled, browser vendors may define their own, different, cooldown\ntime periods.\n| **Note:** When FedCM is enabled, Chrome users can reset cooldown status by clicking on the lock icon in the address bar and clicking the *Reset Permission* button.\n\nAuto-dismissal on mobile browsers\n\nOn **mobile** browsers, and when FedCM is not enabled, Google One Tap closes\nautomatically after a short time period unless the user directly interacts with\nthe One Tap UI.\n\nThe threshold for auto-dismissal is 90 seconds. This is subject to change.\n| **Note:** Auto-dismissal doesn't trigger a cooldown. Auto-dismissal doesn't happen on desktop, iPad, and tablet browsers.\n\nShow a dialog to prevent unintended clicks **Objective:** It's important that users understand the purpose of One Tap. They should be fully aware of the call to action when they give their consent to create an account, since they must share some personal information, such as their first name, last name, email, and profile picture.\n\nOne Tap now comes with different security measures to enforce the integrity of\nthe dialog, but some browsers don't support these capabilities. Unsupported\nbrowsers include non-Chromium-based ones or those before v75. In these cases, or\nif the dialog is covered with other content, a pop-up window is displayed that\nrequests the user's consent to create an account.\n\nUpgraded UX on ITP browsers\n\nDue to\n[Intelligent Tracking Prevention](https://webkit.org/blog/9521/intelligent-tracking-prevention-2-3/) (ITP), the\nnormal One Tap UX doesn't work on Chrome on iOS, Safari, or Firefox. A different\nUX is provided instead on these browsers. You have the option to disable this UX\non ITP browsers by setting the [`data-itp_support`](/identity/gsi/web/reference/html-reference#data-itp_support) attribute.\n\nThe upgraded One Tap UX on ITP browsers begins with a welcome page as shown\nbelow. After the user selects Continue, a pop-up window is opened. The UX in the\npop-up window is very similar to normal One Tap.\n\nWhen there is no Google session, after the 'Continue' button is clicked, users\nmust first sign in to their Google Account. See\n[One Tap support on ITP browsers](/identity/gsi/web/guides/itp) for more details.\n| **Note:** To avoid the flashing pop-up issue, auto sign in isn't supported.\n\nKey user journeys **Note:** Refer to [Automatic sign-in key user journeys](/identity/gsi/web/guides/automatic-sign-in-sign-out#key_user_journeys) for the UX flow when automatic sign-in is enabled.\n\nThe user journeys vary based on the following statuses.\n\n- Session status on Google websites. The following terms are used to indicate\n different Google session status when the user journey starts.\n\n - Single-session: There is exactly one active session on Google websites.\n - Multiple-session: There are more than one active sessions on Google websites.\n\n | **Key Point:** One Tap is not shown if there is no active session on Google websites.\n- Whether the selected Google Account has approved your website when the user\n journey starts. The following terms are used to indicate different approval\n status.\n\n - New user: The selected account hasn't approved your website.\n - Returning user: The selected account has approved your website before.\n\nSingle-session new user journey\n\n1. The new user consent page.\n\n2. The second confirmation dialog in a pop-up window for non-Chromium browsers.\n\n3. After users confirm, an ID token is shared with your website.\n\nSingle-session returning user journey\n\n1. The returning user page.\n\n2. After users click the button, an ID token is shared with your website.\n\nMultiple-session new user journey\n\n1. The account chooser page.\n\n2. The consent page.\n\n For non-Chromium browsers, this confirmation dialog is displayed in a\n pop-up window:\n\n3. After user consent, an ID token is shared with your website.\n\nMultiple-session returning user journey\n\n1. The account chooser page.\n\n2. After users select a returning account, an ID token is shared with your\n website."]]