Google Sign-In
Your clients enter with the Google account their browser is already signed in to. Google shows its own prompt, the client taps once, and they are in. No password, no registration form, no confirmation email.
What it gives you
The most expensive moment in a booking is the form. Someone has picked their time, sees “name, phone, email” and leaves. Google Sign-In removes that step for people who have been to you before: a returning client taps once and lands in their own account, with their bookings, their balance and their personal discount, exactly as if they had typed a password.
A new visitor gets no account. Their name and email are simply filled into the booking form, and an account appears when they actually book. Nothing is created behind anybody’s back.
Who it is for
The add-on earns its place where clients have accounts: a regular customer base, balances, a loyalty programme, personal discounts, booking history in a client area. If your bookings are one-off and nobody registers, it will do nothing for you.
Where to buy it
The add-on is sold separately and is included in the Elite plan.
From inside the plugin. In WordPress go to Baza Booking, then Features, find the Google Sign-In card and press Unlock. Payment is handled by Stripe. The add-on switches on the moment the payment goes through. No plugin update, no plan change, nothing to re-install.
From your Baza account. You can also buy it there alongside your other add-ons. It attaches to the licence key this site already uses, so nothing has to be entered twice.
Once it is active, the card on the Features screen says Unlocked and shows when the subscription started and when the next payment is due.
What you need before you start
A Google Cloud project with an OAuth Client ID. It is free, it takes about five minutes, and you do it once. Everything else is already in the plugin.
Getting a Client ID
The plugin walks you through this on the settings page itself, and it prints the one value that is easy to get wrong. You do not have to work out your site’s origin: it is shown there, ready to copy.
- Open Google Cloud Console.
- Create a new project or select an existing one.
- Go to OAuth consent screen and fill it in. Choose “External” for a public booking site. This is the screen your clients will see, so use your real business name and logo.
- Go to the Credentials page and click “CREATE CREDENTIALS”, then “OAuth client ID”.
- Select “Web application” as the type.
- Under “Authorised JavaScript origins” add your site address. The plugin prints it for you on the Google Sign-In settings page, click it to copy.
- Leave “Authorised redirect URIs” empty. The sign-in happens in the browser and never leaves your site.
- Copy the Client ID. It ends in
.apps.googleusercontent.com
Turning it on
In WordPress go to Baza Booking, then Integrations, then Google Sign-In.
Paste the Client ID into its field and tick Enable Google Sign-In. Save. That is the whole of the setup, and the same steps are printed under the form so you do not need to keep this page open.
Then open your booking page in a private window. The prompt is never shown to someone already signed in to your site, so testing while logged in will always look as if nothing happened.
Both fields stay disabled until the add-on is active on your licence, so if they are greyed out, the licence is what to check first.
Everything is also in the plugin
The Google Sign-In settings page carries the same setup steps and the same list of common problems, in your own language. It also prints your exact origin, so the step people get wrong most often is one click instead of one guess.
What your clients see
The prompt appears only for visitors who are not already signed in to your site. What happens after they choose an account depends on whether you know them.
A returning client. If the address Google confirms belongs to a client account on your site, they are signed straight in, with their bookings, their balance and their personal or loyalty discount.
Someone new. No account is created. Their name and email go into the booking form, into empty fields only, so nothing they have already typed is overwritten. An account appears when they place the booking, exactly as it does without this add-on.
Security
The credential Google issues is verified by Google itself, so its signature and expiry are checked by the party that signed them.
The plugin then checks that the credential was issued for your Client ID. A token minted for another site is a perfectly valid token and is refused here.
Signing in requires an address Google marks as verified. An unverified address is refused.
Nothing is kept from Google beyond signing the person in. No tokens are stored and no Google data is written to your site.
If the prompt does not appear
You are signed in to this site. The prompt is only shown to logged out visitors. Try a private window.
The origin does not match. The address in Authorised JavaScript origins must match your site exactly. To Google, https and http are different origins, and so are www and no www. Copy the value the plugin prints rather than typing it.
The visitor is not signed in to Google, or has dismissed the prompt before. Google remembers a dismissal for a while and will not ask again straight away.
The add-on is not active, or the setting is off, or the Client ID is empty. In any of those cases nothing is requested from Google at all, and no Google script is loaded on your pages.
Privacy
While the add-on is switched off, or the Client ID is empty, or the licence does not include it, your site does not contact Google and loads nothing from it. Once it is on, Google’s sign-in script runs on pages that show the booking form, and Google sees that a visitor was there, as it does with any Google service embedded in a page. Mention it in your privacy policy alongside your other integrations.
