Configure social logins for the Webstore
Enable Sign in with Facebook and Sign in with Google on the Webstore so guests can sign up or sign in using their existing consumer social accounts. Social sign-in reduces sign-up friction and is one of the highest-conversion authentication paths for guests under 45 β the primary spa/salon demographic.
Audience: Zenoti administrators configuring authentication options for the Webstore.
On this page
- Before you begin
- Where these credentials are configured
- Steps to configure Facebook social login
- Steps to configure Google social login
- Consumer Google OAuth vs. Enterprise SSO β they are not the same thing
- Tips
- Troubleshooting
- Cache propagation
- Related articles
Before you begin
- You need configuration access in the Zenoti admin portal.
- Decide which social providers you want to enable (one or both).
- For Facebook: you need a developer account in Facebook for developers (developers.facebook.com).
- For Google: you need a Google Cloud project (free tier is sufficient).
Note: Apple Sign-In is not supported on the Webstore. Do not attempt to configure it.
Where these credentials are configured
Social-login OAuth credentials are stored at the org-settings level and consumed by the Webstore at SDK initialization. They are entered in the Social Login Settings block under WEBSTORE V2 SETTINGS on the combined Online booking settings form β the form that opens from the CX V3 tile and applies to Webstore V2 and CX V3 together.
Navigate to Configuration > Online booking > Online booking settings > CX V3, scroll to WEBSTORE V2 SETTINGS, and turn on Enable Social Login under Social Login Settings; the credential fields (Facebook App ID, Facebook App Secret, Google App ID, Google App Secret) appear below the toggle. Social login can only be enabled for organizations whose guest uniqueness is set to email.
Important: Do not place social-login OAuth credentials in the CX V3 template. The Webstore reads the Facebook App ID and Google App ID from the Social Login Settings of the combined Online booking settings form. The CX V3 template controls cross-channel customer experience (announcement banner, button colors, dark mode); social-login OAuth is separate.
Steps to configure Facebook social login
Follow these steps to set up Facebook as a social login option on the Webstore.
1. Create a Facebook App
- Sign in to Facebook for developers (developers.facebook.com).
- Go to My apps and select Create app.
- Follow the Select an app type prompt and choose the type that matches your business.
- Complete Add an app name and enter your App contact email. Optionally link a Business account.
- After creation, note the App ID and the App Secret. The App Secret is shown once β store it securely.
2. Add Facebook Login for Business to your app
- In the app dashboard, go to Add products to your app.
- Find Facebook login for business and select Set up.
- Choose Web as the platform when prompted by Quickstart.
- Complete the Tell us about your Website step by entering your Webstore URL.
- Work through the remaining Quickstart steps (Set up the Facebook SDK for Javascript, Check login status, Add the Facebook login button) as instructed by the Meta console. These steps configure the app on the Meta side; the Webstore handles the SDK initialization automatically once you enter the App ID in Zenoti.
3. Configure the app's redirect URIs and allowed domains
- In the Facebook App dashboard, go to Settings > Basic.
- Under App domains, add your Webstore domain.
- In the Facebook login for business product settings, add the Webstore's redirect URI(s) to Allowed domains for the JavaScript SDK and to the valid OAuth redirect URIs list. Your Zenoti account team can provide the exact redirect URI for your tenant's environment.
- Save changes.
4. Enter the credentials in the Webstore admin
- Navigate to Configuration > Online booking > Online booking settings > CX V3 and scroll to
WEBSTORE V2 SETTINGS. - Under Social Login Settings, turn on Enable Social Login.
- Enter the App ID and App Secret obtained in step 1 in the Facebook App ID and Facebook App Secret fields.
- Select Save.
- Select Save.
5. Verify
After the cache propagation delay (up to 30 minutes):
- Open the Webstore in a clean browser session.
- Navigate to the sign-in or sign-up screen.
- Verify the Sign In screen displays the Or continue with section and that the Facebook option appears.
- Select the button and complete the OAuth handshake. Confirm you are signed in to a guest profile.
If the button does not appear, check that the combined Online booking settings form was saved with Enable Social Login turned on.
Worked example: A spa named "Serenity Spa" creates a Facebook App named "Serenity Spa Webstore" with App ID
1234567890123456and App Secretabc123def456.... They addserenityspa.comto App domains and enter the Zenoti-provided redirect URIhttps://serenityspa.zenoti.com/webstoreNew/auth/callbackto the allowed redirect URIs list. After entering both values under Social Login Settings on the combined Online booking settings form (Configuration > Online booking > Online booking settings > CX V3) and selecting Save, the Sign In screen on their Webstore shows the Facebook sign-in option within 30 minutes.
Steps to configure Google social login
Follow these steps to set up Google as a social login option on the Webstore.
1. Create a Google Cloud project and OAuth consent screen
- Sign in to Google API Console (console.cloud.google.com).
- Select Create a New Project from the New Project dialog.
- Enter a Project Name (for example, your business name), select an Organization if applicable, and choose a Location.
- After the project is created, navigate to APIs & Services > OAuth consent screen.
- Set User Type to External (for consumer
gmail.comaccounts). - Complete the consent screen form: enter the app name, user support email, home page URL (your Webstore URL), privacy policy URL, and developer contact email.
- Under Authorized Domains, add your Webstore domain. You can also use Edit App later to update this.
- Save and continue through the remaining consent screen steps.
2. Create OAuth 2.0 client credentials
- In the Google API Console, navigate to APIs & Services > Credentials.
- Select Create Credentials > OAuth client ID.
- Set Application Type to Web Application.
- Under Authorized Javascript Origins URL, add your Webstore's root domain (for example,
https://serenityspa.zenoti.com). - Add the Webstore's redirect URI(s) to the authorized redirect URIs list. Your Zenoti account team can provide the exact redirect URI for your tenant.
- Select Create. Note the Client ID and Client Secret displayed.
3. Enter the credentials in the Webstore admin
- Navigate to Configuration > Online booking > Online booking settings > CX V3 and scroll to
WEBSTORE V2 SETTINGS. - Under Social Login Settings, turn on Enable Social Login.
- Enter the OAuth client ID and client secret from step 2 in the Google App ID and Google App Secret fields.
- Select Save.
- Select Save.
4. Verify
- Open the Webstore in a clean browser session.
- Navigate to the sign-in or sign-up screen.
- Verify the Sign In screen displays the Or continue with section and that the Google option appears.
- Select the button and complete the Google sign-in flow. Confirm you are signed in to a guest profile.
Worked example: A wellness center creates a Google Cloud project named "Wellness Center Webstore". They set User Type to External, add
wellnesscenter.comto Authorized Domains, and create an OAuth client ID with Application Type set to Web Application. They addhttps://wellnesscenter.zenoti.comas the Authorized Javascript Origins URL and the Zenoti-provided redirect URI to the authorized redirect URIs list. After entering the resulting Client ID (987654321-abc.apps.googleusercontent.com) and Client Secret in the Google App ID and Google App Secret fields under Social Login Settings on the combined Online booking settings form (Configuration > Online booking > Online booking settings > CX V3) and selecting Save, the Google sign-in option appears on their Webstore within 30 minutes.
Consumer Google OAuth vs. Enterprise SSO β they are not the same thing
The Sign in with Google flow described above uses consumer Google OAuth β appropriate for guests signing in with personal gmail.com accounts. It is not enterprise SAML SSO.
| Sign-in method | Target users | Authentication backend | Where it's configured |
|---|---|---|---|
| Sign in with Google (consumer OAuth) | Personal gmail.com accounts |
Google App ID / Client Secret | This article β Webstore V2 Authentication |
| Enterprise SSO | Organization Google Workspace, Microsoft Entra (Azure AD), Okta, and similar identity providers | SAML 2.0 | SSO redirect configuration (separate from Webstore V2 Authentication) |
If your business is a corporate wellness customer where employees should sign in with their corporate identity provider, configure Enterprise SSO instead. Do not use the consumer Google OAuth fields above for SAML SSO β the mechanisms are different and the configuration would not work.
Tips
- Enable both providers for maximum reach. Facebook and Google OAuth can be active simultaneously. Guests see both options on the sign-in screen under Or continue with and can choose whichever account they prefer.
- Use a dedicated business developer account. Create the Facebook App and Google Cloud project under a shared business account rather than a personal developer account. This prevents access loss if an individual employee leaves.
- Verify your Webstore domain in both consoles. Adding your Webstore domain to App domains (Facebook) and Authorized Domains (Google) before entering credentials in Zenoti reduces the chance of OAuth errors at runtime.
- Store App Secrets and Client Secrets securely. These values grant access to your OAuth app. Use a password manager or secrets vault β do not store them in plain text documents or share them over email.
- Test in a clean browser session. Cached sign-in state from a previous session can mask whether the social-login button is actually appearing for new guests. Always test in a private/incognito window.
Troubleshooting
The Sign in with Facebook or Sign in with Google button does not appear after saving. Confirm that the Facebook App ID or Google App ID was entered correctly under Social Login Settings on the combined Online booking settings form (Configuration > Online booking > Online booking settings > CX V3) and that Enable Social Login is turned on. Changes take up to 30 minutes to propagate due to cache invalidation β wait the full interval before concluding there is a problem.
Guests receive an OAuth error when tapping the social sign-in button. The most common cause is a mismatch between the redirect URI configured in the Meta or Google developer console and the URI the Webstore sends during the OAuth handshake. Verify that the redirect URI provided by your Zenoti account team is entered exactly β including protocol, subdomain, and path β in the Valid OAuth Redirect URIs (Facebook) or authorized redirect URIs list (Google). A trailing slash difference or HTTP vs HTTPS mismatch will cause the OAuth flow to fail.
The social sign-in button appears but guests cannot complete sign-in β they see a domain error. Check that your Webstore domain is listed in App domains (Facebook Settings > Basic) and in Authorized Domains (Google OAuth consent screen). If the domain was added after the App or project was created, use Edit App (Google) or the Basic settings tab (Facebook) to add it, then save.
Guests are prompted to sign in with Google but are taken to a corporate SSO page instead of a personal Google account. This occurs when the guest's browser or device is enrolled in a Google Workspace domain that intercepts the OAuth flow. Consumer Google OAuth targets personal
gmail.comaccounts. If your guests are corporate employees who should use their work identity, configure Enterprise SSO rather than consumer Google OAuth.
Cache propagation
Note: Changes to authentication settings may take up to 30 minutes to propagate to the Webstore due to cache invalidation.