Content and preferences · Google LLC

Sign in with Google: cookies and consent

Sign-in with a Google account.

Spot it on your site

  1. Open your site in a private window, without clicking the banner.
  2. Developer tools › Application › Cookies.
  3. G_ENABLED_IDPS is already there? Sign in with Google fires before consent.

Block Sign in with Google until consent

When the scan finds Sign in with Google, Nodbar files it under “Content and preferences” and holds its scripts back until the visitor chooses. After the install, a new scan checks that nothing fires before consent any more.

Your banner in your colours, with Sign in with Google blocked until the visitor chooses.

Create my banner

FAQ

Is the G_ENABLED_IDPS cookie required?

No. Sign in with Google brings third-party content: it can stay hidden until the visitor agrees, with a button to turn it on.

Can I use Sign in with Google without a cookie banner?

Yes, if it stores nothing and does not contact its servers before the visitor uses it. Otherwise, you need their consent.

What happens if the visitor rejects it?

The Sign in with Google content stays hidden; the rest of the site must work normally.

Sources: Nodbar’s tracker database and Open Cookie Database, EDPB guidelines on the ePrivacy Directive. Updated on . This is not legal advice.