Skip to main content
Docs

<GoogleOneTap /> component

Important

To use Google One Tap with Clerk, you must enable Google as a social connection in the Clerk Dashboard and make sure to use custom credentials.

The <GoogleOneTap /> component renders the Google One Tap UI so that users can use a single button to sign-up or sign-in to your Clerk application with their Google accounts.

By default, this component will redirect users back to the page where the authentication flow started. However, you can override this with force redirect URL props or force redirect URL environment variables.

GoogleOneTapProps

  • Name
    cancelOnTapOutside?
    Type
    boolean
    Description

    If true, the One Tap prompt closes automatically if the user clicks outside of the prompt. Default: true.

  • Name
    itpSupport?
    Type
    boolean
    Description

    If true, enables the ITP-specific UX when One Tap is rendered on ITP browsers such as Chrome on iOS, Safari, and FireFox. Default: true.

  • Name
    fedCmSupport?
    Type
    boolean
    Description

    If true, enables Google One Tap to use the FedCM API to sign users in. See Google's docs on best practices when disabling FedCM support. Default: true

  • Name
    signInForceRedirectUrl?
    Type
    string
    Description

    Useful if you want to redirect to a path specific to Google One Tap users. If provided, this URL will always be redirected to after the user signs in, overriding any <ClerkProvider> redirect URL props or redirect URL environment variables.

  • Name
    signUpForceRedirectUrl?
    Type
    string
    Description

    Useful if you want to redirect to a path specific to Google One Tap users. If provided, this URL will always be redirected to after the user signs up, overriding any <ClerkProvider> redirect URL props or redirect URL environment variables.

Usage with frameworks

The following example includes basic implementation of the <GoogleOneTap /> component. You can use this as a starting point for your own implementation.

Note

<GoogleOneTap> does not render if the user is already signed into your Clerk application, so there's no need to manually check if a user is signed in yourself before rendering it.

Note

This component can be used in Expo Web projects, but won't work in native environments (iOS or Android). For native apps, use the supported native components instead.

/app/sign-in-google.web.tsx
import { GoogleOneTap } from '@clerk/clerk-expo/web'

export default function Page() {
  return <GoogleOneTap />
}

Limitations

  • If your application will use the Google API on behalf of your users, the <GoogleOneTap> component is not recommended, as Google does not provide Clerk with an access or refresh token that you can use.
  • Users with the 1Password browser extension may not be able to render the Google One Tap UI. They must disable this extension.
  • When testing in development, if you select the X button to close the Google One Tap UI, you may encounter a cooldown that prevents you from rendering it again for a period of time. To bypass the cooldown, remove the g_state cookie.

Feedback

What did you think of this content?
Edit this page on GitHub

Last updated on