DTC Wayne

Shopify has native Google sign-in. I did not need an app or a monthly fee

Wayne · 2026-05-07 · #shopify #independent-store #how-to

I kept seeing the same small detail while browsing independent stores abroad: a login page with a “Continue with Google” button. One click, and there was no email address or password to enter.

My first assumption was that it needed an expensive app or a pile of custom code. This source walkthrough showed something else: Shopify’s new customer account system had native support for it. I followed the setup myself in about 15 minutes, without installing an app or writing code.

Why spend those 15 minutes

For an independent store with member accounts and repeat buyers, the upside is practical:

  • Customers do not need to remember a new password or open an email verification link.
  • Support gets fewer “forgot my password” and “I did not receive the reset email” requests.
  • Returning customers can use their Google account instead of trying to remember which email they used last time.
  • A Google sign-in option can make a store feel more considered.

There is a limit. Guest checkout does not create an account, so Google sign-in does not turn guest shoppers into registered customers. This is a small improvement for members and repeat customers, not a conversion fix for every visitor.

The four-stage flow

Four-stage flow: check the new customer account system, collect Shopify values, create a Google Cloud OAuth app, then paste credentials back into Shopify and verify.

Check the account system, collect the values, create the OAuth client, then enable and verify the login.

The diagram keeps the original four stages in order. The text below retains the configuration details and all paths in readable form.

Let an AI guide you through it

If you would rather have an AI assistant pause after each action, copy this prompt into ChatGPT, Claude, Gemini, or another assistant. It should ask where you are stuck, then move one action at a time. You can paste an error message or share a screenshot when something goes wrong.

AI setup prompt
Show the full prompt 
You are a Shopify setup assistant. I want to enable "Sign in with Google" for my Shopify store. Guide me through it one action at a time. Do not give me every step at once.

Please interact with me this way:


    

  1. Ask which step I am on, or whether I have not started yet.
    2. 

  2. Give me one concrete action at a time. Wait until I say “done” before moving on.
    3. 

  3. When I paste an error message or screenshot, diagnose the cause before you suggest a fix.
    4. 

  4. Do not assume I know Google Cloud Console. Tell me exactly where to click for every menu and button.
    5. 



The overall process has four stages:


    

  1. Prerequisite check: confirm that Shopify Admin uses the new customer account system. Settings → Customer accounts → Login services must be present. If the store uses the old version, it must switch first.
    2. 

  2. Collect Shopify values: Settings → Customer accounts → Login services → Sign in with Google lists nine URLs: three JavaScript origins, three redirect URIs, and three deauthorize callbacks. It also has blank Client ID and Client Secret fields. Keep this page open.
    3. 

  3. Create the OAuth app in Google Cloud: open console.cloud.google.com, create a project, configure the OAuth consent screen with User Type set to External, and publish the app. Create an OAuth Client ID with Application type set to Web application. Copy Shopify’s six URLs into the origins and redirect URI fields. Google has no matching field for the deauthorize callbacks, so leave that third group out. Copy the Client ID and Client Secret.
    4. 

  4. Paste the values back and enable: paste both values into Shopify, switch Off to On, save, then use a private window to visit the account subdomain. Confirm that “Continue with Google” appears and sign-in works.
    5. 



Common mistakes: forgetting to publish the app, missing a redirect URI, testing in a normal browser window with cached sign-in state, or putting a deauthorize URL into Google’s redirect URI field.


Which step am I on?

Step-by-step setup

1. Check that the account system is the new version

The source tutorial describes Shopify’s 2024 customer-account upgrade as New Customer Accounts. In that setup, Google and Apple sign-in were native options. The older Classic version did not support them.

In Shopify Admin, go to Settings → Customer accounts.

  • If you see a Login services submenu with Google and Apple options, the store is on the new system.
  • If it is missing, the store uses the older system. Switch the account system first on the same page.
2. Collect the values in Shopify Admin

Open Settings → Customer accounts → Login services → Sign in with Google.

That page lists nine URLs:

  • Authorized JavaScript origins: three URLs
  • Authorized redirect URIs: three URLs
  • Deauthorize callback URIs: three URLs

Keep the page open. You will copy the URLs into Google Cloud Console one by one.

The bottom of the page has empty Client ID and Client Secret fields. Leave them empty for now. Google will provide those values.

3. Create an OAuth app in Google Cloud Console

Open console.cloud.google.com.

Create a project. Use the project picker at the top, choose New Project, give it a name, and select Create.

The source page noted that a “Free trial $300 credit” banner may appear. OAuth sign-in was described as free in this historical setup, with no credit consumption or dependency on the trial. This is historical guidance, not a statement about current platform terms.

Configure the OAuth consent screen. Go to APIs & Services → OAuth consent screen. In the newer interface it may appear as Google Auth Platform.

  • Set User Type to External.
  • Set App name to the store name. Use your email for Support email and Developer contact.
  • Add the store domain and shopify.com under Authorized domains.
  • Finish the flow, return to the main page, and select Publish App.

Without publishing, only manually added test users can sign in. Other visitors are rejected. The source says basic login scopes did not require Google review before publishing.

Create the OAuth Client ID. Go to Credentials → + Create Credentials → OAuth client ID.

  • Set Application type to Web application.
  • Copy Shopify’s three Authorized JavaScript origins into Google’s matching field.
  • Copy Shopify’s three Authorized redirect URIs into Google’s matching field.
  • Google has no matching field for Shopify’s Deauthorize callback URIs, so leave that third group out.

Select Create. The dialog shows the Client ID and Client Secret. The source warns that the secret appears only once, so copy it immediately.

4. Paste the credentials into Shopify, enable, and verify

Return to the Shopify page you kept open. Paste the Client ID and Client Secret into the fields at the bottom. Switch Off → On, then save.

Test in a private browser window. A regular window can carry cached sign-in state and make a broken setup look correct.

Visit https://account.<your-domain>/. The login page should show Continue with Google. Select it, choose a Google account, and confirm that the store signs you in after the redirect.

  • redirect_uri_mismatch usually means that a Google redirect URI is missing. Add the omitted URI.
  • Access blocked: This app's request is invalid usually means that the OAuth consent screen was not published.

A few gotchas worth keeping

  1. Publish the app. Testing mode only allows whitelisted accounts, and the error shown to everyone else can be confusing.
  2. Add all three redirect URIs. The myshopify.com entry is easy to miss, and a missing value can cause intermittent sign-in failures.
  3. Use a private window for the test. An existing Google session in a normal window can hide a problem.
  4. The Google Cloud credit banner is separate from this flow. The source treats OAuth sign-in as free and unrelated to the trial period.
  5. You do not need an app for the native setup described here. The source cites Google sign-in plugins in the Shopify App Store at $5 to $20 per month, while this native path was sufficient for the case covered.

FAQ

What about Sign in with Apple?

The same page also listed Sign in with Apple. The source describes a similar configuration flow, but it requires an Apple Developer Program account at $99 per year.

If you do not have that account, this source recommends leaving it for later. Its judgment was that iPhone and Mac users also have Google accounts, so the absence of Apple sign-in alone should not make them abandon an order.

The source’s closing judgment was simple: this was a small, low-effort improvement that did not disrupt the existing experience. If a customer used it, the login path became shorter. Its suggestion was to set aside 15 minutes and configure it.

Source-era boundary

This is a translation of a May 2026 source tutorial. It preserves its paths, cost statements, estimated time, and platform behavior as historical instructions. Check the current Shopify and Google Cloud interfaces before changing a live customer-account flow.

The handoff in the original article pointed to a Shopify multilingual product-page fallback diagnosis. That source link is retained as-is rather than replaced with an invented English destination.

The original author also wrote two practical independent-store posts per month and offered RSS and email for readers who wanted the next one.

← Back to home