The Google login app adds a Google button to the sign-in and registration pages of your storefront. A customer who selects it signs in on Google and comes back to your shop signed in, without a password of their own. If no customer has that email address yet, an account is created.
The app works on every plan and in every country. It is one of four sign-in apps, next to Discord login, Facebook login and Twitch login.
Before you start
- A Google account with access to the Google Cloud Console (console.cloud.google.com). You register your shop there as an OAuth client, and Google gives you an ID and a secret for it.
- The web address of your storefront, for example your own domain from Domains.
Set up Google login
In the Google Cloud Console, choose or create a project. Under APIs & Services, fill in the OAuth consent screen first if it is not set up yet: your shop's name, a support email address and your storefront domain.
Under APIs & Services → Credentials, create an OAuth client ID of type Web application.
In Poltura, open the App Store and open Google login. New stores have the app installed already. If you see Install, select it first. See App Store. The setup guide on the page shows the redirect URI you register in the next step.
Needs setup means the client ID and secret are not saved yet. The fields are under Settings, further down. Copy the redirect URI from the app's setup guide and add it under Authorized redirect URIs.
Save the client, then copy the client ID and the client secret Google shows.
Under Settings, fill in these two fields: Client ID and Client secret.
Select Save. If the app is off, select Turn on.
Wait about a minute, then open the sign-in page of your storefront. The Google button is below the sign-in form. Select it and sign in to check that you return to the shop signed in.
Settings
- Client ID (required): the OAuth client ID from the Google Cloud Console, such as
123-abc.apps.googleusercontent.com. - Client secret (required): the OAuth client secret. It is kept encrypted and never shown again once saved. After saving you only see that a value is saved, and you can replace it.
Client ID and Client secret must be set together. Until both are saved, the Google button stays off your storefront. Saved values take effect within about a minute.
What shoppers see on your storefront
While the app is on and both values are saved, the sign-in page and the registration page show a button with the Google logo under the form, together with the buttons of your other sign-in apps. Poltura asks Google for the customer's basic profile (name and picture) and email address. The first and last name of a new customer come from the Google account.
When a customer account with the same email address already exists, the customer first confirms the link between the two through a link sent by email. More about customer sign-in is in Customer accounts and sign-in.
If something goes wrong
- Google shows a redirect_uri_mismatch error. The address the storefront sent is not an authorized redirect URI of the client. Compare it with the redirect URI in the app's setup guide character by character.
- Sign-in comes back with an error after Google. The secret is wrong or was reset in the Google Cloud Console. Enter the current one and save.
- A customer cannot sign in although the button works for others. Google reports their email address as not verified. Poltura refuses such a sign-in, because customer accounts are matched by email. The customer verifies the address with Google and tries again.
- Only you and a few testers can sign in. The OAuth consent screen is still in testing, which lets in only the test users listed there. Publish the app on the consent screen in the Google Cloud Console.
- The button is not on the sign-in page. The app is off or not installed, or Client ID and Client secret are not both saved. Turn the app on in the App Store, see App Store, and fill in both values under Settings.