Sign In With Google Release Notes

AI-generated Key Takeaways

• Google Identity Services JavaScript library now supports Federated Credential Management (FedCM) to improve automatic sign-in flows, though reconfirmation may be required initially for enhanced privacy.

• "Sign in with Google" button now supports Family Link and adheres to Google Workspace policies.

• AMP support has been removed when FedCM is enabled.

• Chrome users may need to reconfirm sign-in with Google Account in each instance for privacy reasons, with exceptions based on third-party cookie settings.

• Developers are encouraged to migrate to FedCM to minimize potential disruptions to automatic sign-in conversion rates.

This page contains a list of the new features and significant changes to the Google Identity Services JavaScript library.

2025-03-17

• Sign in with Google button supports Federated Credential Management (FedCM) and adhere to Google Workspace policies set by the organization's administrator.

2024-12-01

• Sign in with Google button supports Family Link and adhere to Google Workspace policies set by the organization's administrator.

2023-12-21

• Federated Credential Management (FedCM) Beta for Google Identity Services was launched in August 2023. Many developers tested the API and have provided valuable feedback.

  One response Google heard from developers is about the FedCM automatic sign-in flow user gesture requirement. For improved privacy, Chrome requires users to reconfirm that they want to sign in to the website with Google Account in each Chrome instance even if the user approved the website prior to the FedCM rollout. This one-time reconfirmation is achieved through a single click of the One Tap prompt to demonstrate user intent to sign-in. This change may cause an initial disruption in automatic sign-in conversion rates for some websites.

  Recently in M121, Chrome made a change to the FedCM automatic sign-in flow UX. The reconfirmation is only required when third-party cookies are restricted. This means:

  1. Before third-party cookie restrictions are ramped up to 100% (see Privacy Sandbox News and Update page for latest timeline), FedCM automatic sign-in does not require reconfirmation for returning users. If users reconfirm with FedCM UI, this reconfirmation will count toward the user gesture requirement.

  2. FedCM automatic sign-in will check the confirmation status when the third-party cookies are manually restricted by users today, or by default in future Chrome.

  With this change, we recommend all automatic sign-in developers migrate to FedCM as soon as possible, to reduce disruption to automatic sign-in conversion rates.

  For the automatic sign-in flow, GIS JavaScript won't trigger FedCM on an older Chrome (before M121), even if your website chooses to opt-in to FedCM.

2023-08-15

• Added support for the Federated Credential Management API (FedCM).
• Accelerated Mobile Pages is unsupported. AMP is not available when FedCM is enabled.

2022-04-12

• Upgraded One Tap UX on ITP browsers is supported.

2021-4-13

• Sign In With Google button is supported.

2021-03-17

• Accelerated Mobile Pages is supported.

2020-3-24

• Exponential Cool Down is supported.