Google One Tap sign-in: where to show it and how it behaves
Short answer: Google One Tap shows a small "Sign in as …" prompt to visitors who are signed in to a Google account, so they can create an account or log in to your site with one tap. It can lift sign-ups on content sites, shops and SaaS trials, but only if you show it on the right pages, verify the ID token on your server, respect the cooldown when people close it, and plan for the browser-controlled FedCM prompt and the different experience on Safari and Firefox. Treat it as an addition to your normal sign-in options, not a replacement.
What One Tap is
One Tap is part of Google Identity Services for the web. When a visitor with a Google session lands on your page, a prompt offers to sign them in with that account. If they accept, Google sends your site an ID token, which your server verifies and uses to find or create the customer's account.
It's most useful where sign-in is a hurdle, for example saving a basket, commenting, getting a free trial or unlocking a guide. It's less useful on pages where visitors are focused on something else, such as checkout payment steps or support articles.
How the prompt behaves, and why visitors don't see it every time
Google's documentation explains several behaviours that matter for placement and expectations:
- Exponential cooldown. If the visitor closes the prompt with the close button, it's suppressed for a while in that browser. Without FedCM, the documented periods are two hours after the first close, one day after the second, one week after the third and four weeks after that. The cooldown resets after a successful sign-in through One Tap.
- FedCM cooldowns. When FedCM is enabled, the browser shows the prompt, and browser vendors may define their own cooldowns.
- Auto-dismissal on mobile. On mobile browsers without FedCM, One Tap closes automatically after about 90 seconds without interaction. Google notes this doesn't trigger a cooldown and doesn't happen on desktop or tablets.
- Different experience on Safari and Firefox. Because of Intelligent Tracking Prevention, the normal One Tap flow doesn't work on Chrome on iOS, Safari or Firefox. Google provides a different flow there, often starting with a welcome page and a pop-up window, and lets you disable it.
So One Tap won't appear for everyone: visitors without a Google session, those in cooldown and those whose browser settings block third-party sign-in prompts won't see it. Keep your normal "Sign in" button.
FedCM: the browser takes over the prompt
Browsers are moving sign-in prompts away from third-party cookies. Google's FedCM migration guide explains that with FedCM enabled, the browser displays the prompt and contacts the identity provider only after the user's consent. For your implementation, that means:
- You turn FedCM on with a flag in the One Tap initialisation.
- Custom positioning of the One Tap prompt on desktop isn't supported; the browser controls size and position.
- Several methods that reported whether and why the prompt was displayed are removed, so analytics that relied on "prompt shown" notifications need rethinking.
- If One Tap runs inside a cross-origin iframe, every parent iframe needs
allow="identity-credentials-get".
If your developer added One Tap some time ago, ask them to check the current migration guide.
Where to show it
Good places:
- Article pages where signing in unlocks something, like saving or commenting.
- Product pages, to offer saved baskets and wishlists.
- Free-trial landing pages.
Bad places:
- Checkout payment steps, where it distracts.
- Pages where visitors are already signed in. Don't initialise it for signed-in users.
- Every page on the first visit. Showing it repeatedly only triggers the cooldown.
Server side: verify, then link
When One Tap succeeds, your site receives an ID token. Your server must verify it with Google's libraries before trusting anything in it, and should use the token's subject ID as the stable identifier for that Google account. If the email matches an existing account created with a password, don't merge silently; ask the customer to confirm ownership first.
Also decide what happens for a brand-new visitor: create the account immediately, or show a short "complete your profile" step for anything else you need, such as delivery country.
Measure honestly
Because FedCM removes some display notifications, measure outcomes rather than impressions: sign-ups and logins completed via One Tap, compared with other methods, and whether those customers go on to buy or stay active.
Respect privacy expectations
One Tap shows the visitor's Google name and photo in the prompt, which some people find surprising on a site they've just opened. Explain in your privacy notice what you receive when someone signs in with Google and what you do with it, and ask only for the data you actually need. If your audience is wary, for example on a health or finance site, consider showing the standard button instead of an automatic prompt.
Test before launch
Check the prompt in Chrome on desktop and Android, Safari on iPhone and Mac, and Firefox; signed in and signed out of Google; as a new visitor and as an existing customer. Close the prompt and confirm it stays closed, and confirm signed-in customers never see it.
An illustrative example
A hypothetical Austin recipe-subscription site added One Tap to recipe pages, offering "save this recipe" with one tap. It initialised the prompt only for signed-out visitors, kept it off the checkout, verified tokens server-side and asked existing password users to confirm before linking Google. After enabling FedCM, the developer removed custom prompt positioning and the old display-moment tracking, and measured success by saved recipes and trial starts.
FAQ
Does One Tap replace "Sign in with Google" buttons?
No. Keep the button for visitors who don't see the prompt or prefer to choose.
Can I force the prompt to reappear after a visitor closes it?
No. The cooldown is deliberate; respect it.
Does it work on iPhones?
A different flow is used on Safari and Chrome on iOS because of tracking prevention. Test it there.
Is One Tap free to use?
Check Google's current terms for Identity Services before relying on it.
If you'd like Google sign-in, including One Tap, added to your site in a way that doesn't annoy visitors, tell us what visitors sign in to do.