Magento 2 Login History for Customer Account and Admin
SKU: CUSTOMERLOGINHISTORY1
- customers see their recent sign-ins right in the account
- support sees the history in the admin on the customer record
- IP address storable in shortened form, device and browser detected
- retention period in days and an email for a new device
Einmaliger Kauf · inkl. 12 Monate Updates · zzgl. MwSt.
Magento 2 login history: make sign-ins visible in the customer account
The Magento 2 login history from Mironsoft shows customers in their account when and with what they last signed in, and gives your support the same history in the admin. Stored are time, device, browser and, if you wish, a shortened IP address. When someone signs in from a new device, an email can inform the customer. You set the retention period yourself.
History in the account
A page in the customer account lists recent sign-ins with time, device and rough location of the IP.
View in the admin
On the customer record staff see the same history without searching log files.
Shortened IP
The IP address can be stored shortened, so less personal data is kept.
New-device alert
An email to the customer reports sign-ins from a device not seen before.
Retention period
A cron job removes entries after the number of days you set.
Failed attempts optional
Failed sign-ins can be recorded as well and marked in the history.
Why a Magento 2 login history strengthens trust in the account
Anyone with a customer account in a shop stores addresses, orders and often payment preferences. Customers wonder whether someone else had access. That is why merchants search for a Magento 2 login history, for recent sign-ins in the Magento 2 customer account or for an alert about a sign-in from a new device. Magento stores the time of the last sign-in, but shows neither customers nor support a list.
Without a history, questions like I think someone was in my account land in support, and the answer requires a look at server logs. With the Magento 2 login history customers answer that themselves, and your team saves follow-up questions.
Magento 2 login history in the customer account: recent sign-ins
The customer account gets an additional menu item, Sign-ins. There customers see the latest entries with date, time, detected device, browser and a rough location of the sign-in. You set how many entries are shown. The page is built with Alpine.js and Hyvä components, loads without an extra library and follows the theme.
- Date, device, browser and shortened IP per entry
- Current session clearly marked
- Number of displayed entries configurable
Login history in the admin: support without log searching
In the admin the customer record shows its own tab with the history. Staff see whether a customer has signed in at all, when last and from which device. That helps with questions about password resets and account locks. A global grid filters all sign-ins by period, customer and result, and access is regulated by its own ACL resource.
- Tab on the customer record with the history
- Global grid with filters by time and result
- Own ACL resource for access
Email on sign-in from a new device
The module recognises devices by browser and operating system, without fingerprinting and without additional scripts. When a customer signs in from a new device, an email can inform them and advise changing the password if it was not them. You maintain the email template per store view and switch the alert on globally or per customer group.
- Device detection from browser and system only
- Email template per store view, link to change the password
- Alert switchable globally or per customer group
Retention period and privacy for the login history
IP addresses and device details are personal data. That is why you set whether the IP is stored in full, shortened or not at all, and how many days entries stay. A cron job then deletes them. When a customer is deleted, the module also removes their history. For access requests staff can export a customer history. Legal review by the shop owner remains untouched.
- IP full, shortened or off
- Deletion after days and on customer deletion
- Export of the history per customer for access requests
Where the Magento 2 login history helps in the shop
Four typical situations for customers and support.
Suspected foreign access
A customer spots an unknown sign-in in the Magento 2 login history and changes the password at once, without bothering support.
Support requests
Staff check in the Magento 2 login history on the customer record whether and when a customer signed in before answering the request.
Shared accounts
In B2B shops purchasing managers notice when several people share one account and can introduce individual accounts.
Data protection access
For access requests you export a customer history with one click instead of searching log files.
Magento 2 login history: without and with the module compared
What changes compared with standard Magento.
| Topic | Without module | With Mironsoft Customer Login History |
|---|---|---|
| Customer view | No list of sign-ins | Own page in the account |
| Support view | Only time of the last sign-in | Tab on the customer record and grid |
| New device | No message | Email to the customer |
| IP address | Not stored in a structured way | Full, shortened or off, configurable |
| Retention | No rule | Deletion after days and on customer deletion |
How we set up the Magento 2 login history for you
The process after your order.
Agreement
You decide how much of the IP is stored, how long entries stay and whether customers are warned.
Installation
We install the Magento 2 login history and add the menu item to the customer account of your Hyvä theme.
Email template
We design the new-device alert to match your shop, per store view.
Test
We test sign-in, failed attempt, new device, the account display and the cleanup.
Handover
Your support team gets an introduction to the tab, grid and export.
Delimitation from the Mironsoft Admin Login Log
The Mironsoft Admin Login Log monitors sign-ins of backend users, warns about a new IP and blocks addresses. The Magento 2 login history is aimed at your customers and their support instead. It shows customers their own sign-ins and is deliberately built for transparency, not defence.
Both modules can be combined. The customer side runs with Alpine.js in the Hyvä theme without an extra library and without jQuery.
No download, personal setup instead
Customer Login History is not listed here as a ready-made download file for self-installation. The purchase is a service commission: we get in touch after the purchase, install the module in your shop and agree on IP storage, retention and email template together with you.
Frequently asked questions
Everything about the history, privacy, alerts and how the purchase works.
How can I show the login history of a customer in Magento 2?
How do customers see their recent sign-ins in the account?
How can I warn customers about a sign-in from a new device?
Is the full IP address stored?
How long is the Magento 2 login history kept?
Is the login history GDPR compliant?
Are failed sign-ins recorded too?
Does the Magento 2 login history work with Hyvä?
How does this differ from the Admin Login Log?
Can I download and install the module myself?
Magento 2 Login History – Mironsoft Customer Login History