We use necessary cookies to make this site work. With your permission we also use Google Analytics to understand how the site is used and Google Ads cookies to measure which of our ads lead to purchases. You can accept all cookies, reject the optional ones or choose which ones to allow. Cookie policy
Choose which cookies you allow. Necessary cookies are always on because the shop cannot work without them. You can change your choice at any time with the "Cookie settings" link.
Needed for the basket, checkout, login and security. They do not track you.
Google Analytics: how many people visit, which pages they read and how they found the site. It sets the _ga cookies and sends usage data to Google.
Google Ads: measures which of our ads lead to a purchase. It sets the cookies _gcl_au and _gcl_aw (90 days) and, when you buy, sends Google the order details and a hashed form of your contact details for matching. See our cookie and privacy policies.
Let shoppers sign in and register with the accounts they already use — on your sign-in page and at checkout.
Free
No payment needed, with 12 months of updates.
Add it to your cart and complete the free checkout. Your ZIP downloads and Composer access will be in your account.
No subscription or automatic renewal. Keep using the versions included in your update period. Update and licence details
Composer package commercegears/module-social-login
Every extra form field costs you customers. Social Login lets shoppers sign in and create an account with Google, Facebook or X in one click: on the sign-in page, the registration page, the checkout and anywhere else you place the buttons.
It is built for production stores: no third-party SDKs, every ID token fully validated, PKCE where the provider supports it, and careful rules for linking an existing account so a social sign-in can never be used to take over someone else's account. It works on Luma and Hyvä, per website and store view, and stores nothing but the link between the customer and the provider.
Shoppers use the account they already have. No form to fill in and no new password to remember.
The buttons sit in the checkout sign-in popup and above the email field, right where shoppers decide.
Every ID token is validated and accounts are only linked when the email address can be trusted.
All features
Feature tour
01 / 07
Buttons above the sign-in and registration forms. Icon and text or icon only, light or dark, in the order you choose.
02 / 07
The "Sign In" popup on the checkout page and the authentication popup show the same buttons, so returning customers check out faster.
03 / 07
Alpine.js and Tailwind templates for Hyvä 1.3+, picked automatically. Luma, Blank and their child themes work out of the box.
04 / 07
Buttons stack into full-width rows on phones, where typing an email address and a password is hardest.
05 / 07
My Account › Connected Accounts lists the linked providers. Customers connect another one or disconnect one, but never the last way to sign in.
06 / 07
Choose where the buttons appear, how they look, what happens after sign-in and which customer group new accounts join.
07 / 07
Each provider shows the callback URL to register for the current store view, with short setup steps. Secrets are stored encrypted.
Live demo
A full Magento store with the module installed, on Luma and on Hyvä. The admin demo signs you in with one click.
Compatibility
| Magento | 2.4.6 – 2.4.9 |
|---|---|
| Platforms | Magento Open Source and Adobe Commerce |
| Storefront themes | Luma Blank Hyvä |
| PHP | 8.2 – 8.5 |
| Latest version | 2.0.3 |
| composer.json requires | php ~8.2.0||~8.3.0||~8.4.0||~8.5.0 ext-json * ext-openssl * magento/framework ~103.0.6 commercegears/module-core ^2.0 free, installed by Composer with this module magento/module-backend * magento/module-checkout * magento/module-config * magento/module-customer * magento/module-store * magento/module-ui * magento/module-widget * |
Installation
Get it free, create a Composer key in your account, then in the root of your Magento project:
01Add the repository and your key (once per project)
composer config repositories.commercegears composer https://repo.commercegears.com composer config --auth http-basic.repo.commercegears.com PUBLIC_KEY PRIVATE_KEY
02Install the module
composer require commercegears/module-social-login
03Enable it
bin/magento setup:upgrade bin/magento setup:di:compile bin/magento setup:static-content:deploy bin/magento cache:flush
The last three are only needed in production mode.
Prefer a zip? Every version you are entitled to can be downloaded from My modules. More about Composer access
User guide
The user guide has its own page: how to install Social Login, what each option does and how to use it in your store. Written for version 2.0.3; a copy ships with the module.
Changelog
FAQ
Something else on your mind? The developers who wrote the module answer before and after you buy.
Ask a question →Already installed it? Open a support ticket
Google, Facebook and X (Twitter). Each one can be switched on separately, per website or store view.
Yes, with the add-on Social Login Pro. It adds these five providers to the same configuration section, buttons, Connected Accounts page and admin tools; everything described here applies to them too.
Those apps open links in their own built-in browser, where Google does not allow sign-in. Social Login recognises these browsers and shows a note above the buttons asking the shopper to open the page in their browser, with a "Copy link" button. This works on Luma, the checkout and Hyvä.
Yes. Hyvä templates are included (Hyvä 1.3+, tested with 1.5). On the Hyvä checkout the Luma checkout fallback is used, so the checkout buttons are the Luma ones.
No. OAuth 2.0 and OpenID Connect are implemented on Magento's HTTP client and PHP's OpenSSL extension, so there are no extra libraries to keep up to date or to conflict with other extensions.
On the sign-in page, the create-account page, the authentication popup and the checkout sign-in, above the email field in checkout (guests), anywhere as a CMS widget, and anywhere in your layout as a block.
The provider is linked to that account. If the provider has verified the address and is responsible for it (for example Gmail addresses at Google), this happens automatically; otherwise, or if you choose so, the customer enters their account password once. After that the provider signs them in directly.
Yes: set Create New Accounts to No. Shoppers without an account are asked to register first. This is useful for B2B and trade-only shops.
Yes, with CommerceGears Customer Approval: social sign-ups get an approval status like any other registration, and pending or rejected customers are not signed in.
X never returns one unless your app has the email permission. The customer then enters an email address once; an account created from a typed-in address must be confirmed by email before it can be used.
Yes, under My Account > Connected Accounts. The module refuses to remove the last way to sign in (no password and no other provider). Admins can remove links under CommerceGears > Social Login > Linked Accounts.
Only the link between the customer and the provider account is stored, no access tokens. Links are deleted with the customer, and pending sign-in data is deleted after 15 minutes.
Every sign-in uses a single-use state bound to the browser, PKCE where the provider supports it, and full ID token validation (signature, issuer, audience, expiry, nonce). Email addresses are only trusted when the provider has verified them, and accounts from unverified addresses must be confirmed by email first. Return URLs are restricted to your own store.
Yes. All settings, including the credentials, can be set per website and store view. Register one callback URL per store view URL at the provider.
Yes, developers can implement ProviderInterface (or extend AbstractOidcProvider) and register it in di.xml; icons, settings and self-test checks have extension points too. See the README.
They are kept and shown with their provider code in the admin and under Connected Accounts, where they can be removed. They are not counted as a way to sign in, so customers are never left without one.
Magento Open Source and Adobe Commerce 2.4.6 to 2.4.9, PHP 8.2 to 8.5 (Magento 2.4.6: PHP 8.2).
Support
Social Login Pro
Social Login Pro adds five more providers to the same buttons, settings and account rules.
See Social Login Pro →| Feature | Free | Pro |
|---|---|---|
| Google, Facebook and X | ||
| Apple (Sign in with Apple) | ||
| Microsoft personal and work accounts | ||
| LinkedIn, Amazon and GitHub | ||
| All placements, popup, widget and layout block | ||
| Account linking rules and Connected Accounts | ||
| Hyvä and Luma |
Add your own fields to Magento customer accounts and addresses, such as a company type, VAT number or address type, with rules per store and customer group, conditional fields and values on every order.
$199
Add your own fields to the Magento checkout without code, such as a delivery date, PO number, order comment or a dropdown, and find the answers on the order, in the order grid, in emails and on the invoice PDF.
$119
Free customer account approval for Magento 2 (Luma and Hyvä) for B2B, wholesale and trade-only shops: new registrations wait for admin approval, with auto-approve rules, admin and customer emails, and REST/GraphQL login blocking.
Free
Free Magento 2 module for Arasta live chat: the chat widget on every page without touching the theme, signed-in customers recognised and orders linked to the chats that led to them.Requires an Arasta subscription. The chat itself runs on Arasta, a paid SaaS service: you need an active plan at arasta.io. This module connects your store to it and is free.
Free
From the blog
The button appears on Hyvä. Does it open, submit and recover from an error? Test the workflow before trusting the compatibility badge.
The package download is the easy part. Keep credentials private, deploy the tested lock file and prove the feature works before customers use it.
Licence price is only the entry fee. Compare the workflow you get, the gaps you must fill and who maintains it after the next Magento upgrade.
Eight sign-in buttons are not a conversion strategy. A reliable route back into the right account can be; here's how to judge it on your store.
Start with one provider and one complete account journey. Exact callback URLs, app ownership and secret expiry matter more than the number of buttons.
