Developers will be migrated by default starting April 2024. Opt-in to FedCM (set boolean flag to true) to test and make any necessary changes to ensure a smooth transition.
If you need more time to verify FedCM functions properly on your site and make changes to your code, set the boolean flag to false. This will temporarily exempt your traffic from using FedCM. Regardless of the flag selection, starting on January 4, 2024, users that are part of Chrome’s Tracking Protection rollout will have limited access to third-party cookies, and unless FedCM is enabled, One Tap and Automatic sign-in will not be displayed to these users.
Developers will be migrated by default starting April 2024. Opt-in to FedCM (set boolean flag to true) to test and make any necessary changes to ensure a smooth transition.
Developers using Automatic Sign-in feature should migrate to FedCM as soon as possible to reduce any potential impact on conversion rates.
If you need more time to verify FedCM functions properly on your site and make changes to your code, set the boolean flag to false. This will temporarily exempt your traffic from using FedCM. Regardless of the flag selection, starting on January 4, 2024, users that are part of Chrome’s Tracking Protection rollout will have limited access to third-party cookies, and unless FedCM is enabled, One Tap and Automatic sign-in will not be displayed to these users.
Reviewing the required changes:https://developers.google.com/identity/gsi/web/guides/fedcm-migration#migrate_your_web_app I think that we will need at least a new property on https://developers.google.com/identity/gsi/web/reference/js-reference#IdConfiguration
I have used same value that for oneTapEnabled as both options are related