Articles on: Users management

Google login

Let your users sign in with Google


Social login lets your marketplace visitors create an account and log in with one click, using their Google account — no password to remember, no activation email to wait for. This guide walks you through creating a Google OAuth application and enabling it on your marketplace.


What you'll need


  • Admin access to your marketplace (/admin)
  • A Google account to access the Google Cloud console
  • About 10 minutes


Good to know: each marketplace uses its own Google application. Your API credentials are never shared with other marketplaces, and you keep full control (branding on the consent screen, quotas, revocation).



Step 1 — Copy your callback URL from your admin


  1. In your marketplace admin, go to Settings → Social login (or press Cmd/Ctrl + K and type "social").
  2. In the Google section, copy the redirect URI shown in the blue box. It looks like:


      https://your-marketplace.com/auth/google/callback
  


   Keep this page open — you'll come back to it at the end.


[Screenshot: the Google section of Settings → Social login, with the redirect URI highlighted]


Step 2 — Create a project in the Google Cloud console


  1. Open console.cloud.google.com and sign in.
  2. Click the project selector in the top bar, then New project.
  3. Give it a recognizable name (e.g. the name of your marketplace) and click Create.


[Screenshot: Google Cloud "New project" dialog]



This is the screen your users will see when Google asks them to confirm the sign-in.


  1. In the left menu, go to APIs & Services → OAuth consent screen.
  2. Choose External as the user type, then Create.
  3. Fill in:
       - App name: your marketplace name (this is what users will see)
       - User support email: your support address
       - App logo (optional but recommended)
       - Authorized domains: your marketplace domain (e.g. your-marketplace.com)
       - Developer contact email
  4. On the Scopes step you don't need to add anything: the default email, profile and openid scopes are all Kreezalid uses.
  5. Save, then click Publish app so the app is available to all users (while in "Testing" mode, only test users you list can sign in).


[Screenshot: OAuth consent screen form with app name and authorized domain filled]


Step 4 — Create the OAuth client ID


  1. Go to APIs & Services → Credentials.
  2. Click Create credentials → OAuth client ID.
  3. Choose Web application as the application type.
  4. Under Authorized redirect URIs, click Add URI and paste the callback URL you copied in Step 1.
  5. Click Create. Google shows you two values:
       - Client ID (ends with .apps.googleusercontent.com)
       - Client secret


   Copy both — the secret is only shown here.


[Screenshot: "OAuth client created" dialog showing the Client ID and Client secret]


Custom domain? If your marketplace is reachable on several domains (e.g. mymarket.kreezalid.com and www.mymarket.com), add one redirect URI per domain, each ending in /auth/google/callback.


Step 5 — Enable Google login on your marketplace


  1. Back in your admin, on Settings → Social login:
       - Toggle Enable Google login on
       - Paste the Client ID
       - Paste the Client secret
  2. Save.


[Screenshot: Google section filled in, toggle on]


That's it! A Continue with Google button now appears on your /login and /register pages.



How it works for your users


  • New visitor: clicking the button creates their account instantly — it is activated right away (no confirmation email needed, Google already verified their address) and they receive your welcome email.
  • Existing user: if the Google email matches an existing account, they are simply logged in.
  • If your signup form requires extra information (custom fields, company name…), the user is asked to complete their profile right after their first sign-in.


Troubleshooting


Problem

Likely cause

The button doesn't appear on /login

The toggle is off, or the Client ID / secret is empty. All three are required.

Google shows redirect_uri_mismatch

The redirect URI in the Google console doesn't exactly match the one in your admin (check https://, the domain, and the /auth/google/callback path).

"This app isn't verified" warning

Your OAuth consent screen is still in Testing mode — publish it (Step 3.5), or complete Google's verification if you request extra scopes.

Users are asked to complete their profile

Expected: your default user group has required signup fields that Google can't provide.

Updated on: 21/07/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!