Social Login (Google / Apple)

You enter your own Google/Apple keys; the matching buttons then appear automatically on your storefront's login and register pages. A provider whose…

Where to find: Left menu → Integrations → Google Login / Apple Login Who it's for: Stores that want their customers to sign up and sign in with one tap using their Google or Apple account. In short: You enter your own Google/Apple keys; the matching buttons then appear automatically on your storefront's login and register pages. A provider whose keys you haven't entered simply won't show a button.

What does it do?

Social login lets a customer register and sign in with their Google or Apple account without typing an email and password. This is especially effective at improving sign-up completion on mobile.

Each store uses its own OAuth keys. That way your app name is what customers see on the consent screen, and customer data is handled through your own provider account. The Client Secret and Apple private key are stored encrypted and are never sent to the storefront; the code-to-token exchange happens server-side.

Note: For the buttons to appear on the storefront, you must save the integration with its keys and enable it. For connection steps, see Managing Integrations (List, Setup, Turning On/Off).

Redirect URLs

Google and Apple only return the user to an address you have pre-registered. In the provider's console, register the addresses below, replacing the placeholder with your store's short name (slug):

Google: https://api.treyza.co/api/<store-slug>/storefront/auth/social/google/callback
Apple: https://api.treyza.co/api/<store-slug>/storefront/auth/social/apple/callback

Tip: <store-slug> is your store's address segment (e.g. mystore). Enter the URL exactly — even a trailing slash or a difference in letter case will block sign-in.

For Google

In Google Cloud Console → APIs & Services → Credentials, create an OAuth client ID (application type: Web application).
Add the Google callback URL above to Authorized redirect URIs.
Copy the generated Client ID and Client Secret.
In Treyza, open Integrations → Google Login, paste both values, save, and enable the key.

For Apple

Unlike the others, Apple asks for a few pieces of information instead of a single "secret." You obtain them from your Apple Developer account:

Field	Where to get it
Services ID (Client ID)	Certificates, Identifiers & Profiles → Identifiers → Services IDs
Team ID	The team identifier at the top-right of your Apple Developer account
Key ID	The identifier of the key you create under Keys for Sign in with Apple
Private Key (.p8)	The contents of the `.p8` file downloaded once when you create that key

Add the Apple callback URL above to the Services ID's Return URLs, and verify your domain with Apple.
Create the Sign in with Apple key and download the .p8 file.
In Treyza, open Integrations → Apple Login, paste the Services ID, Team ID, Key ID and the entire contents of the .p8 file, save, and enable it.

Tip: With Apple's private relay option, the customer gives you an address like ...@privaterelay.appleid.com. This address forwards to a real inbox, so you can still email the customer through it.

What changes for the customer?

On the login and register pages, "Continue with Google" / "Continue with Apple" buttons appear based on the providers you enabled.
When the customer taps a button, they authenticate at the provider and return to your store.
If the provider's verified email matches an existing store account, it links to that account; if there's no match, a new customer account is created.

Note: If a customer previously registered with a password and their social email matches that account, the two methods merge into a single account. For security, only emails verified by the provider are linked to existing accounts.