Understand the One Tap user experience

Globally opt out

Users can opt out of One Tap if they disable the Google Account sign-in prompts flag in the Apps with access to your account page. The opted-out sessions aren't shown in One Tap. If all Google sessions are opted out, One Tap doesn't display.

Exponential cool-down

If the user closes the One Tap prompt manually, the One Tap prompt is suppressed. A user closes One Tap when they tap Close in the top-right corner of the prompt. One Tap won't display in the same browser or the last website visited for a period of time.

The following exponential time periods are used for cool-downs:

Consecutive times closed	Time period that One Tap is disabled
1	Two hours
2	One day
3	One week
4+	Four weeks

The cool-down status resets after a successful sign-in using One Tap or the Sign in with Google button.

Auto-dismissal on mobile browsers

On mobile browsers, Google One Tap closes automatically after a short time period unless the user directly interacts with the One Tap UI.

Currently, the threshold for auto-dismissal is 90 seconds. We might adjust it in the future.

Note: Auto-dismissal doesn't trigger a cool-down. Auto-dismissal doesn't happen on desktop, iPad, and tablet browsers.

Show 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.

One Tap now comes with different security measures to enforce the integrity of the dialog box, but some browsers don't support these capabilities. Unsupported browsers include non-Chromium-based ones or those before v75. In these cases, or if the dialog is covered with other content, a pop-up window is displayed that requests the user's consent to create an account.

Figure 3. Sign-in dialog box

Upgraded UX on ITP browsers

Due to Intelligent Tracking Prevention (ITP), the normal One Tap UX doesn't work on Chrome on iOS, Safari, or Firefox. A different UX is provided instead on these browsers. You have the option to disable this UX on ITP browsers by setting the data-itp_support attribute.

The upgraded One Tap UX on ITP browsers will start with a welcome page as below. Once the user chooses to continue, a pop-up window will be opened. The UX in the pop-up window is quite similar to normal One Tap.

Figure 4. Welcome Page

When there is no Google session, after the 'Continue' button is clicked, users must first sign in to their Google account. See One Tap support on ITP browsers for more details.

Note: To avoid the flashing pop-up issue, auto sign in isn't supported.

Key user journeys

Note: Please refer to Automatic sign-in key user journeys for the UX flow when automatic sign-in is enabled.

The user journeys vary based on the following statuses.

• Session status on Google websites. The following terms are used to indicate different Google session status when the user journey starts.

  • Single-session: There is exactly one active session on Google websites.
  • Multiple-session: There are more than one active sessions on Google websites.
  Key Point: One Tap won't display if there is no active session on Google websites.

• Whether the selected Google account has approved your website when the user journey starts. The following terms are used to indicate different approval status.

  • New user: The selected account hasn't approved your website.
  • Returning user: The selected account has approved your website before.

Single-session new user journey

1. The new user consent page.

   

2. The second confirmation dialog in a pop-up window for non-Chromium browsers, or if One Tap is covered by other content.

   

   Key Point: This step can be skipped on Chrome 75+ and if One Tap UI is not covered by other content.

3. After users confirm, an ID token is shared with your website.

Single-session returning user journey

1. The returning user page.

   

2. After users click the button, an ID token is shared with your website.

Multiple-session new user journey

1. The account chooser page.

   

2. The consent page on Chrome 75+.

   

   For non-Chromium browsers, or if One Tap is covered by other content, users will see the confirmation dialog below in a pop-up window.

   

   Key Point: Normally users only see one of the above pages. However it's possible that users see both on Chrome 75+, if the account chooser page is not covered by other content but the consent page is covered.

3. After user consent, an ID token is shared with your website.

Multiple-session returning user journey

1. The account chooser page.

   

2. After users select a returning account, an ID token is shared with your website.